(2017) Configuration Management Best Practices

This commit is contained in:
Morgan 2017-12-12 13:37:18 +01:00 committed by GitHub
parent 326ef75be4
commit a3d2b24cd3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -494,6 +494,7 @@ I spend a lot of time on internet, losing myself in lot of topics. I choose GitH
* [kelseyhightower/confd](https://github.com/kelseyhightower/confd) - confd is a lightweight configuration management tool to keep local config files up-to-date using either etcd, consul, dynamodb, redis, vault, zookeeper, aws ssm parameter store or env vars * [kelseyhightower/confd](https://github.com/kelseyhightower/confd) - confd is a lightweight configuration management tool to keep local config files up-to-date using either etcd, consul, dynamodb, redis, vault, zookeeper, aws ssm parameter store or env vars
* [Eric Myhre](https://gist.github.com/warpfork/0ad12d99d2b4de32412f7f294c23fde5) - You probably don't really want CI-triggered CD * [Eric Myhre](https://gist.github.com/warpfork/0ad12d99d2b4de32412f7f294c23fde5) - You probably don't really want CI-triggered CD
* [StackStorm Exchange](https://exchange.stackstorm.org/) - Automate all the things you already know and use with dozens of ready-made integration packs. Cloud providers, monitoring services, lightbulbs. Its extendable, flexible, and built with love for DevOps and ChatOps * [StackStorm Exchange](https://exchange.stackstorm.org/) - Automate all the things you already know and use with dozens of ready-made integration packs. Cloud providers, monitoring services, lightbulbs. Its extendable, flexible, and built with love for DevOps and ChatOps
* [Dag Sonstebo](https://www.slideshare.net/DagSonstebo/techug-glasgow-talk-22feb17-configuration-management-best-practices) - (2017) Configuration Management Best Practices
## Ansible ## Ansible
* [Ansible](https://www.ansible.com/blog) - Ansible Blog * [Ansible](https://www.ansible.com/blog) - Ansible Blog
@ -2369,6 +2370,7 @@ I spend a lot of time on internet, losing myself in lot of topics. I choose GitH
* [Project Atomic](http://docs.projectatomic.io/container-best-practices/) - Container Best Practices * [Project Atomic](http://docs.projectatomic.io/container-best-practices/) - Container Best Practices
* [Conventional Commits](https://conventionalcommits.org/) - The Conventional Commits specification proposes introducing a standardized lightweight convention on top of commit messages. This convention dovetails with SemVer, asking software developers to describe in commit messages, features, fixes, and breaking changes that they make. * [Conventional Commits](https://conventionalcommits.org/) - The Conventional Commits specification proposes introducing a standardized lightweight convention on top of commit messages. This convention dovetails with SemVer, asking software developers to describe in commit messages, features, fixes, and breaking changes that they make.
* [marionebl/commitlint](https://github.com/marionebl/commitlint) - Lint commit messages * [marionebl/commitlint](https://github.com/marionebl/commitlint) - Lint commit messages
* [Dag Sonstebo](https://www.slideshare.net/DagSonstebo/techug-glasgow-talk-22feb17-configuration-management-best-practices) - (2017) Configuration Management Best Practices
## Database ## Database
* [jOOQ Blog](https://blog.jooq.org/) - best practices and lessons learned about writing Java and SQL code * [jOOQ Blog](https://blog.jooq.org/) - best practices and lessons learned about writing Java and SQL code