Commit 88e1a926 authored by Dominique Barton's avatar Dominique Barton 🦄
Browse files

FEATURE: Mention prod server

parent 3bb381b0
Pipeline #15218 passed with stages
in 39 seconds
Development server
==================
We've a dedicated shared development server called ``dev1.pvt.confirm.ch`` or simply ``dev.confirm.ch``.
Docker Docker
------ ======
The development server runs `Docker <http://docker.com/>`_, which can be used for testing, building and deployments. We've dedicated `Docker <http://docker.com/>`_ development & production servers:
- ``dev1.[pvt|pub].confirm.ch`` or simply ``dev.confirm.ch`` for all **development** environment
- ``prod1.pub.confirm.ch`` or simply ``prod.confirm.ch`` for all **live** environments
We're also running our own :ref:`Docker Registry` which can be used to push Docker images. We're also running our own :ref:`Docker Registry` which can be used to push Docker images.
GitLab Runners Proxy
-------------- -----
To route requests, have a look at the :ref:`Proxy` chapter.
Development GitLab Runners
--------------------------
There are 2 registered and shared GitLab runners running on the development server. There are 2 registered and shared GitLab runners running on the development server.
The runners can be used to test & build applications.
Use the following :ref:`GitLab CI` tags to access the runners: Use the following :ref:`GitLab CI` tags to access the runners:
- ``dev docker``: To run a job in a Docker container on the development server (i.e. *Docker executor*) - ``dev docker``: To run a job in a Docker container on the development server (i.e. *Docker executor*)
...@@ -23,8 +28,3 @@ Use the following :ref:`GitLab CI` tags to access the runners: ...@@ -23,8 +28,3 @@ Use the following :ref:`GitLab CI` tags to access the runners:
Use the ``dev shell`` tags only for deploying Docker containers (i.e. ``docker-compose``). Use the ``dev shell`` tags only for deploying Docker containers (i.e. ``docker-compose``).
For everything else, use the ``dev docker`` tags and thus the Docker executor. For everything else, use the ``dev docker`` tags and thus the Docker executor.
Proxy
-----
To route requests, have a look at the :ref:`Proxy` chapter.
...@@ -3,11 +3,14 @@ Proxy ...@@ -3,11 +3,14 @@ Proxy
There's a `Traefik Proxy <https://traefik.io/traefik/>`_ running on all Docker servers, dispatching all incoming HTTP/HTTPS requests to the desired Docker containers. There's a `Traefik Proxy <https://traefik.io/traefik/>`_ running on all Docker servers, dispatching all incoming HTTP/HTTPS requests to the desired Docker containers.
The proxy also provides a `Proxy Dashboard <https://proxy-dev.confirm.ch>`_, which can be used to display a few informations about the deployed routes & services (Docker containers). The proxies also provides a dashboard, which can be used to display a few informations about the deployed routes & services (Docker containers):
- `Dev Proxy Dashboard <https://proxy-dev.confirm.ch>`_
- `Prod Proxy Dashboard <https://proxy-prod.confirm.ch>`_
.. hint:: .. hint::
The proxies are deployed in the `Proxy GitLab project <https://git.confirm.ch/confirm/proxy>`_ and the dashboard is only available from within private networks. The proxies are deployed in the `Proxy GitLab project <https://git.confirm.ch/confirm/proxy>`_ and the dashboards are only available from within private networks.
.. _routing requests: .. _routing requests:
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment