We have some developers services:
We use a very simple configuration for our needs.
CI/CD util for delivery code to environment. We use this forked repository
Before starting, do this:
mkdir jenkins
chmod 777 ./jenkins
Vault is saver of credentials and shared data of our services. We save here shared:
- urls, ports
- credentials
- configs of services
Now, we have next structure of namespaces:
- service-1
- environment-1
- environment-2
- environment-3
- local isolated environment
- service-2
- environment-1
- environment-2
- environment-3
- local isolated environment
PyPi registry is saver of private python package. This is wsgi server without reverse proxy. We protected them with htpasswd way.
This is private docker registry. We save have our docker images of services. We protected them with htpasswd way. More about htpasswd in Credentials section
Before push, you need login:
docker login <url>
Set tag for image:
docker tag <image-id> <url>/<tag>
After that, docker asks you login and password. Now, you can push concrete image by tag:
docker push <url>/<tag>
Now, you can see your image into registry by endpoint (with authentication):
<url>/v2/_catalog
Downloading image from registry by tag:
docker pull <url>/<tag>
More info about docker registry API, you can find here.
You can see more info:
This is monitoring service. Now, anyone can go here, therefore we don't use credentials. If you want to add new service, you go to ./prometheus/config.yml. Than, in section scrape_configs, you need add any targets:
- targets: ['<your-host>:9090']
After that, rebot container.
You can run our infrastructure by next way for production:
RESTART=always docker-compose up
Or for locally:
RESTART=no docker-compose up
It is not a very useful to starting docker compose in local machine with mode restart: always. Containers always
restart. Then killing them is not a very simple case. This is can be outrageously.
If you want to add new user, you can generate bcrypt-11. You need to generate
new hash and pass them into .htpasswd as new line.
After update your credentials, you need reboot the service.
You need to use htpasswd.
- First make sure you have the passlib module installed (note that passlib>=1.6 is required), which is needed for parsing the Apache htpasswd file specified by the -P, --passwords option (see next steps):
- Create the Apache htpasswd file with at least one user/password pair (you'll be prompted for a password).
- Add password to $HOME/.credentionals/htpasswd to a new line and restart docker-registry server