Setting up the development environment: coffee grounds (Part 2)

Hello dear reader!
This time I want to share my result of setting up a personal environment for working with various PHP-based projects using Puppet. This article describes the results that were obtained in the process of studying and writing Puppet configuration.

This article was written to show one way to do this. I do not want to call for action, but only share what I encountered, what I did and how I use it.

The article will be very long with a bias towards the technical side. Please under the "cat".

Some time ago I wrote “Setting up the development environment: a circle of needlework (Part 1)” , in which I described my sufferings at every change of project. In preparing this article, some components of the environment were added and removed. At the end of the article there will be a link to the repository with a module that you can break into pieces to use and modify at your discretion.
')

Purpose: quickly set up the working environment for the current project

The goal is the same, but with a small addition: if you can automate, do it.

Puppet

This is a good tool that will help you in managing the configuration of various operating systems.

The choice fell on this tool, as this tool is used in the company, and I need to know what happens behind the scenes with DevOps / NetOps.

So in the process of describing the configuration, I got the following:

- PHP (5.6, 7.x; pools for each project; extensions; composer)
- NGINX (PHP-FPM upstream for each project; Easy vhost configuration)
- OpenSSL
- MySQL
- Bind9
- NodeJS + NPM
- memcached
- Redis
- Docker
- Additional software: mc, htop, wget, curl

Configuration

Since I store the actual configuration in a private repository, I suggest that you look at the training version , which I will describe in this article.

Attention: this repository is delivered as is. The further fate of the project is to become more flexible or die.

When developing a configuration crutch , I used the capabilities of Puppet Hiera and r10k (a tool for convenient configuration deployment).

The basis of the code that is responsible for installing packages, creating files and restarting services is in the 'production' branch. Using the capabilities of Puppet Hiera, I provided the ability to customize the configuration of the current node, which is determined by the FQDN of the working machine. Thus, one of the configuration examples can be found along the way:


which will be combined with


As a result of this configuration, the entire initial list of components will be installed, and the server will also have the following features:

1) Created configuration for NGINX + PHP-FPM for the following projects:
- www.warface.lo (php7.0)
- imageproxy.warface.lo (php5.6)
- www.cryengine.lo (php7.1)
- shop.cryengine.lo (php7.1)
- forum.cryengine.lo (php5.6)
2) Installed the following versions of PHP with the appropriate modules: 5.6, 7.0, 7.1, 7.2
3) The imagemagick package will be installed.
4) Updated OpenSSL to the latest available version.
5) MySQL root / root
6) Redis and Memcached services
7) Latest versions of Composer, NodeJS and NPM
8) Server bind9 + its configuration, which allows "rezolvit" domain * .lo requests to the current host.
9) Docker

Structure

The repository structure combines the following concepts:
master branch - control repository ( control-repo )
production branch - description of the 'production' configuration

Installation

The startup process comes down to a few simple steps:

1) Install git + puppet + r10k
2) Initialization of control-repo
2) Deploying configuration with r10k
3) Run puppet apply

Further modification

Below is a list of how you can improve your current configuration and make it more flexible:

- Add classes describing the process of project deployment (git clone, specific vhost, application settings, base deployment: user + schema + data)
- Add container launch classes for docker
- Certificate generation (NGINX + HTTPS)

The implementation is far from ideal and does not always follow the rules, but this is what I would like to highlight:

- Always think about dependencies, since Puppet does not guarantee the initialization of classes in the order they are connected;
- Describe using hiera parameters that change the behavior of the class;
- Do not forget about the default settings;
- Do not reinvent the wheel: perhaps someone has already done the functionality that you need.

useful links

- Puppet documentation
- R10K
- Puppet Modules
- Puppet Cookbook
- Setting up the development environment: the needlework circle (Part 1)

PS : If you find any things in the repository that can be improved, then write me about it and with an example or a link how to change it.