20%
20.06.2022
_DB_PASSWORD=SOME_DB_PASSWORD
15 command: ["start-dev"]
16
17 postgres:
18 container_name: postgres
19 image: postgres:14
20 environment:
21 - POSTGRES_PASSWORD=SOME_DB_PASSWORD
22
20%
02.06.2020
cddaa6-0886-44b3-9590-16717d5cd3c2",
20 "service_instance_guid": null,
21 "port": null,
22 "domain_url": "/v2/shared_domains/fb6bd89f-2ed9-49d4-9ad1-97951a573135",
23
20%
02.02.2021
i < 1000:
21 my_data.append(data_w_weekend(i / 1000))
22 i += 1
23
24 # add some noise
25 random_gain = 0.1 # factor for the noise
26 i = 0
27 while i < 1000:
28 my_data[i] += np
20%
18.03.2020
0.743225 0.743613 0.334626E-02
20 0.743993 0.744333 0.301099E-02
21 0.744667 0.744967 0.271109E-02
22 0.745261 0.745526 0.244257E-02
23
20%
22.06.2012
1-12:00:00
20
144400
1-16:06:40
21
160000
1-20:26:40
22
176400
2-01:00:00
23
193600
2-05:46:40
24
20%
06.10.2022
": [
16 {
17 "GroupName": "RND-Admins"
18 }
19 ]
20 },
21 {
22 "Path": "/",
23 "UserName": "guido",
24 "Arn": "arn:aws:iam::123456789:user/guido",
25
20%
13.12.2022
is my home network (192.168.x.x). The second NIC is connected to a private Ethernet network (10.0.0.1, subnet mask 255.255.252.0), which follows the network addressing discussed in the
20%
11.10.2016
, interesting, and worthwhile exercise. I argue that systems administration needs a command-line editor, because it can be used even if X windows isn't working or isn't installed on the servers. Knowing how
20%
09.10.2017
in turn stores as a separate time series. The software can already cope with millions of time series, yet version 2.0 [6] should cover more extreme Kubernetes environments with thousands of nodes
20%
16.08.2018
seconds set connect timeout (default is 10 sec)
-u seconds set command timeout (no default)
-f n use fanout of n nodes
-w host,host,... set target node list on command line
-x
