# systemctl start docker # docker info ★配置docker服务使用systemd去管理（以及信任本地镜像仓库） # vi /etc/docker/daemon.json { "data-root": "/docker_data", "registry-mirrors": [ "h�ps://cof-lee.com:5443" ], "insecure-registries": bin/dockerd -H fd:// 这行下面再添加一行： ExecStartPost=/usr/sbin/iptables -P FORWARD ACCEPT # systemctl daemon-reload # systemctl restart docker ★默认还加了DOCKER-USER这个forward链，默认全部return，导致不通，也得 放开，具体得看下iptables规则），以下操作目的为 -s 0.0.0.0/0 -j ACCEPT EOF ★最好的做法是让docker不生成默认的docker0网桥，不修改iptables规则 # cat > /etc/docker/daemon.json <

0 码力 | 126 页 | 4.33 MB | 1 年前

3

#修改这行：Environment=PGDATA=/var/lib/pgsql/13/data/ 改为新的路径，如 下： Environment=PGDATA=/data_pg/data/ # systemctl daemon-reload # systemctl restart postgresql-13 ★PG-10版本 # systemctl stop postgresql #修改这行：Environment=PGDATA=/var/lib/pgsql/data/ 改为新的路径，如下： Environment=PGDATA=/data_pg/data/ # systemctl daemon-reload # systemctl restart postgresql ★第3章、设置监听ip及端口号 pg默认监听127.0.0.1的ip及5432/tcp端口

of Constraints “Eliyahu M. Goldratt, who created the Theory of Constraints, showed us how any improvements made anywhere besides the bottleneck are an illusion . Astonishing, but true useless, because it will always remain starved, waiting for work from the bottleneck. And any improvements made before the bottleneck merely results in more inventory piling up at the bottleneck.” Resource

ideas don’t work and reinforcing those that do3. local learnings are rapidly turned into global improvements, so that new techniques and practices can be used by the entire organization iii. ENABLING THE IMPROVEMENT OF DAILY WORK 1. Mike Rother observed in Toyota Kata that in the absence of improvements, processes don’t stay the same—due to chaos and entropy, processes actually degrade over time

resilient systems with higher degrees of assurance 3. Ch. 20 – Convert Local Discoveries into Global Improvements a. USE CHAT ROOMS AND CHAT BOTS TO AUTOMATE AND CAPTURE ORGANIZATIONAL KNOWLEDGE i. ChatOps Goal is focused improvement on daily work, not experimentation and innovation iii. Demo back improvements at the completion of the blitz iv. Empower those closest to the work to continually identify

/root/redis-6.2.13/redis.conf PrivateTmp=true [Install] WantedBy=mul�-user.target EOF # systemctl daemon-reload # systemctl enable redis # systemctl start redis # systemctl status redis ★redis使用ssl

and management tested continuously. Steve Barr steve.barr@csgi.com @srbarr1 Overall Quality improvements, “it” goes in better, and with less issues.  Maintenance window changed from once a week to

approval ii. Peer review help improve overall quality, provide cross-training, learning, and skill improvements. iii. Keep batch sizes of reviews small iv. 4 simple Peer Review Guidelines 1. Everyone must

less able to refactor due to potential rework and merge problems 1. Cross-cutting dependency improvements often provide high-payoffs d. ADOPT TRUNK-BASED DEVELOPMENT PRACTICES i. CI and Trunk-based