20%
09.01.2013
/haproxy/www.example.com.pem
22 mode http
23 option httpclose
24 option forwardfor
25 reqadd X-Forwarded-Proto:\ https
26 default_backend web_server
27
28 backend web_server
29 mode http
30 balance roundrobin
31
20%
09.01.2013
-stack-AWSEBSecurityGroup-ZNUGTMANJ7WO
2013-05-08 20:21:40 INFO Created Auto Scaling launch configuration named: awseb-e-hxaxpp3bsa-stack-AWSEBAutoScalingLaunchConfiguration-12RI7463WQWE3
2013-05-08 20:23:25 INFO Waiting for EC2
20%
05.02.2019
in the container?
20 - name: "mysql client exists"
21 path: '/usr/bin/mysql'
22 shouldExist: true
23
24 # Does the MySQL configuration file exist at the right place?
25 - name: "my.cnf exists and has appropriate
20%
11.02.2016
19
20 mysql> CREATE TABLE `data_random` (
21 `id` CHAR(32) NOT NULL,
22 `data` VARCHAR(64) DEFAULT NULL,
23 `ts` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
24
20%
18.07.2013
=> Service['apache']
17 }
18
19 file { '/var/www/index.html':
20 ensure => present,
21 source => 'puppet:///modules/myproject/web/index.html',
22 owner => 'root',
23 group => 'root',
24
20%
20.05.2014
names was introduced in version 2.2.x
.
The FAQ module consists of several components. The FAQ Explorer lets the admin navigate through the knowledgebase. If you want to create an article, you can call ... 20
19%
02.08.2022
be turned on and off according to what you want to check about the state of the node.
Almost 20 years ago, when I worked for a Linux high-performance computing (HPC) company that no longer exists, we had
19%
11.09.2018
- containerPort: 80
19
20 ---
21
22 apiVersion: v1
23 kind: Service
24 metadata:
25 name: nginx-svc
26 labels:
27 run: nginx-svc
28 spec:
29 type: NodePort
30 ports:
31 - port: 80
32 protocol
19%
13.06.2016
for $i"
19
20 #If certs do not exist yet
21 FILE="$LECROOT/$i/cert.pem"
22 if [ ! -f "$FILE" ]
23 then
24 echo "$FILE does not exists, so lets get certificates"
25 cd /root/letsencrypt
26
19%
04.12.2024
now sports a small FPC ribbon connector exposing a single-lane PCIe 2.0 bus. NVM Express (NVMe) [2] drives connect to the PCIe bus via an M.2 [3] adapter – in this case, to the new M.2 HAT+ released
