Tuto pour le déploiement des sites avec Docker - Historique des versions

Daniela.cojocaru le 5 août 2026 à 12:44

2026-08-05T12:44:01Z

← Version précédente		Version du 5 août 2026 à 12:44
Ligne 1 :		Ligne 1 :
			<languages/>
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->

Daniela.cojocaru : Cette version a été marquée à traduire

2026-08-05T12:36:24Z

Cette version a été marquée à traduire

← Version précédente		Version du 5 août 2026 à 12:36
Ligne 1 :		Ligne 1 :
	<translate>		<translate>
			<!--T:1-->
	A la fin de ce tuto, vous pourrez déployer votre site (ou service) sur les serveurs du BR ! Ceci permet de profiter d'une infrastructure gratuite, performante et robuste !		A la fin de ce tuto, vous pourrez déployer votre site (ou service) sur les serveurs du BR ! Ceci permet de profiter d'une infrastructure gratuite, performante et robuste !

			<!--T:2-->
	Note : ce tutoriel peut être délicat, n'hésitez pas à contacter un BRman pour obtenir de l'aide.		Note : ce tutoriel peut être délicat, n'hésitez pas à contacter un BRman pour obtenir de l'aide.
	</translate>		</translate>

	<translate>		<translate>
	= Comment déployer des conteneurs Docker sur l'infrastructure du BR =		= Comment déployer des conteneurs Docker sur l'infrastructure du BR = <!--T:3-->
	</translate>		</translate>

	<translate>		<translate>
	== Overview ==		== Overview == <!--T:4-->

			<!--T:5-->
	This tutorial will walk you through :		This tutorial will walk you through :
	* How to convert your website to a Docker service		* How to convert your website to a Docker service
Ligne 19 :		Ligne 22 :

	<translate>		<translate>
	== Requirements ==		== Requirements == <!--T:6-->

			<!--T:7-->
	* Basics of git (videos [https://git-scm.com/video/what-is-version-control here] or the beginning of [https://git-scm.com/book/en/v2 this awesome online book]) ;		* Basics of git (videos [https://git-scm.com/video/what-is-version-control here] or the beginning of [https://git-scm.com/book/en/v2 this awesome online book]) ;
	* Basics of containers (see a really good explanation [https://www.docker.com/resources/what-container here]) and of docker-compose (see the getting-started [https://docs.docker.com/compose/gettingstarted/ here]) ;		* Basics of containers (see a really good explanation [https://www.docker.com/resources/what-container here]) and of docker-compose (see the getting-started [https://docs.docker.com/compose/gettingstarted/ here]) ;
Ligne 28 :		Ligne 32 :

	<translate>		<translate>
	== Existing architecture ==		== Existing architecture == <!--T:8-->

			<!--T:9-->
	A physical server called <code>endalcher</code> deploys and runs your container. It uses the following services to connect your service to the Internet:		A physical server called <code>endalcher</code> deploys and runs your container. It uses the following services to connect your service to the Internet:

			<!--T:10-->
	* [https://docs.docker.com/compose/ docker-compose] to deploy the correct environment for your containers ;		* [https://docs.docker.com/compose/ docker-compose] to deploy the correct environment for your containers ;
	* [https://docs.traefik.io/v1.7/ traefik] as a reverse proxy to serve your site behind your endpoint, it is configured [https://gitlab.binets.fr/br/docker-default-services here] ;		* [https://docs.traefik.io/v1.7/ traefik] as a reverse proxy to serve your site behind your endpoint, it is configured [https://gitlab.binets.fr/br/docker-default-services here] ;
Ligne 38 :		Ligne 44 :

	<translate>		<translate>
	== How to convert your website to a Docker service ==		== How to convert your website to a Docker service == <!--T:11-->

			<!--T:12-->
	The exact procedure will be dependant on your project. An example can be found here : [https://gitlab.binets.fr/br/qdj/-/blob/master/deployment/Dockerfile?ref_type=heads qdj-Dockerfile]		The exact procedure will be dependant on your project. An example can be found here : [https://gitlab.binets.fr/br/qdj/-/blob/master/deployment/Dockerfile?ref_type=heads qdj-Dockerfile]

			<!--T:13-->
	A ''Docker container'' is an isolated machine on which you can run your website. In this step, we will help you convert you app to be Docker-ready. This basically means installing everything your app needs inside a linux computer. You'll need to install ''Docker'' on your computer first [https://docs.docker.com/desktop/install/windows-install/ windows-installer].		A ''Docker container'' is an isolated machine on which you can run your website. In this step, we will help you convert you app to be Docker-ready. This basically means installing everything your app needs inside a linux computer. You'll need to install ''Docker'' on your computer first [https://docs.docker.com/desktop/install/windows-install/ windows-installer].

			<!--T:14-->
	We assume your project is hosted on the [https://gitlab.binets.fr BR's gitlab instance]. Create a <code>deployment</code> directory at the root of your repository and create a file <code>Dockerfile</code> (with no extension) and a file <code>docker-compose.yaml</code> in it.		We assume your project is hosted on the [https://gitlab.binets.fr BR's gitlab instance]. Create a <code>deployment</code> directory at the root of your repository and create a file <code>Dockerfile</code> (with no extension) and a file <code>docker-compose.yaml</code> in it.
	</translate>		</translate>
Ligne 68 :		Ligne 77 :

	<translate>		<translate>
			<!--T:15-->
	Then open a terminal in this directory and type <code>docker compose up --build</code>. If everything went well, you see a nice message from Docker telling you everything is working !		Then open a terminal in this directory and type <code>docker compose up --build</code>. If everything went well, you see a nice message from Docker telling you everything is working !

			<!--T:16-->
	Now, you need to make ''your'' app work in the docker container. For this, you need:		Now, you need to make ''your'' app work in the docker container. For this, you need:

			<!--T:17-->
	* To update the Dockerfile to install everything you need. The following works for a basic (Django) python app :		* To update the Dockerfile to install everything you need. The following works for a basic (Django) python app :
	</translate>		</translate>

Daniela.cojocaru le 5 août 2026 à 12:36

2026-08-05T12:36:12Z

← Version précédente		Version du 5 août 2026 à 12:36
Ligne 1 :		Ligne 1 :
			<translate>
	A la fin de ce tuto, vous pourrez déployer votre site (ou service) sur les serveurs du BR ! Ceci permet de profiter d'une infrastructure gratuite, performante et robuste !		A la fin de ce tuto, vous pourrez déployer votre site (ou service) sur les serveurs du BR ! Ceci permet de profiter d'une infrastructure gratuite, performante et robuste !

	Note : ce tutoriel peut être délicat, n'hésitez pas à contacter un BRman pour obtenir de l'aide.		Note : ce tutoriel peut être délicat, n'hésitez pas à contacter un BRman pour obtenir de l'aide.
			</translate>

			<translate>
	= Comment déployer des conteneurs Docker sur l'infrastructure du BR =		= Comment déployer des conteneurs Docker sur l'infrastructure du BR =
			</translate>

			<translate>
	== Overview ==		== Overview ==

Ligne 11 :		Ligne 16 :
	* How to build it automatically on Gitlab-CI		* How to build it automatically on Gitlab-CI
	* How to deploy it automatically on our servers		* How to deploy it automatically on our servers
			</translate>

			<translate>
	== Requirements ==		== Requirements ==

Ligne 18 :		Ligne 25 :
	* Basics of web (see an [https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web/How_the_Web_works introduction] on MDN) ;		* Basics of web (see an [https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web/How_the_Web_works introduction] on MDN) ;
	* Basics of gitlab-ci (reading the [https://docs.gitlab.com/ee/ci/ getting-started] is recommended) ;		* Basics of gitlab-ci (reading the [https://docs.gitlab.com/ee/ci/ getting-started] is recommended) ;
			</translate>

			<translate>
	== Existing architecture ==		== Existing architecture ==

Ligne 26 :		Ligne 35 :
	* [https://docs.traefik.io/v1.7/ traefik] as a reverse proxy to serve your site behind your endpoint, it is configured [https://gitlab.binets.fr/br/docker-default-services here] ;		* [https://docs.traefik.io/v1.7/ traefik] as a reverse proxy to serve your site behind your endpoint, it is configured [https://gitlab.binets.fr/br/docker-default-services here] ;
	* nginx to serve your site to the outside world (as all the binets sites).		* nginx to serve your site to the outside world (as all the binets sites).
			</translate>

			<translate>
	== How to convert your website to a Docker service ==		== How to convert your website to a Docker service ==

Ligne 34 :		Ligne 45 :

	We assume your project is hosted on the [https://gitlab.binets.fr BR's gitlab instance]. Create a <code>deployment</code> directory at the root of your repository and create a file <code>Dockerfile</code> (with no extension) and a file <code>docker-compose.yaml</code> in it.		We assume your project is hosted on the [https://gitlab.binets.fr BR's gitlab instance]. Create a <code>deployment</code> directory at the root of your repository and create a file <code>Dockerfile</code> (with no extension) and a file <code>docker-compose.yaml</code> in it.
			</translate>

	* Dockerfile		* Dockerfile
Ligne 55 :		Ligne 67 :
	</source>		</source>

			<translate>
	Then open a terminal in this directory and type <code>docker compose up --build</code>. If everything went well, you see a nice message from Docker telling you everything is working !		Then open a terminal in this directory and type <code>docker compose up --build</code>. If everything went well, you see a nice message from Docker telling you everything is working !

Ligne 60 :		Ligne 73 :

	* To update the Dockerfile to install everything you need. The following works for a basic (Django) python app :		* To update the Dockerfile to install everything you need. The following works for a basic (Django) python app :
			</translate>
	<source>		<source>
	FROM python:3		FROM python:3

Cedric.holocher : typo

2024-01-05T00:29:36Z

typo

← Version précédente		Version du 5 janvier 2024 à 00:29
Ligne 125 :		Ligne 125 :
	== Automatic deployment ==		== Automatic deployment ==

	We will now add a second CI job to your repository to deploy your image. It will trigger ''another'' CI pipeline of [https://gitlab.binets.fr/br/docker-services br/docker-services]. This pipeline has the rights to deploy on <code>endalcher</code>, and do so using a <code>docker-compose.yaml</code> file. To trigger it, add the following to your <code>.gitlab-ci.yml</code>		We will now add a second CI job to your repository to deploy your image. It will trigger ''another'' CI pipeline of [https://gitlab.binets.fr/br/docker-services br/docker-services]. This pipeline has the rights to deploy on <code>endalcher</code>, and does so using a <code>docker-compose.yaml</code> file. To trigger it, add the following to your <code>.gitlab-ci.yml</code>

	<source lang=yaml>		<source lang=yaml>

Cedric.holocher : rephrase

2024-01-05T00:27:58Z

rephrase

← Version précédente		Version du 5 janvier 2024 à 00:27
Ligne 144 :		Ligne 144 :

	=== Extra parameters and secrets ===		=== Extra parameters and secrets ===

			''Be aware that any secret passed this way is still visible to the BR and everyone that has maintainer access to you repository ! If you need help setting up, don't hesitate to ask for help from the BR !''

	You can also pass any parameter needed in the compose file by adding arguments to the cURL call like so : <code>--form variables[MY_SUPER_VARIABLE]="elle vaut 42!"</code>		You can also pass any parameter needed in the compose file by adding arguments to the cURL call like so : <code>--form variables[MY_SUPER_VARIABLE]="elle vaut 42!"</code>

	If you want to pass secret environnements variables, store ~~then~~ in ~~gitlab under~~ <code>Settings/CI-CD/Variables</code> and make sure they are "protected" and "masked". Pass them like so <code>--form variables[MY_PASSWORD]=$PASSWORD_STORED_IN_GITLAB</code>.		If you want to pass secret environnements variables, store them in <code>Gitlab -> Settings -> CI-CD -> Variables</code> and make sure they are "protected" and "masked". Pass them like so <code>--form variables[MY_PASSWORD]=$PASSWORD_STORED_IN_GITLAB</code>.

	~~Be aware that any secret passed this way is visible to the BR and everyone that has maintainer access to you repository ! If you need help setting up, don't hesitate to ask for help from the BR !~~

	=== Secret files ===		=== Secret files ===

Cedric.holocher : typo

2024-01-05T00:25:59Z

typo

← Version précédente		Version du 5 janvier 2024 à 00:25
Ligne 189 :		Ligne 189 :
	Keeping your repository private can be beneficial for security or privacy. But it require an extra step for the BR to access the docker image. We wille pass a [https://docs.gitlab.com/ee/user/project/deploy_tokens/#gitlab-deploy-token CI deploy token] as cURL parameter.		Keeping your repository private can be beneficial for security or privacy. But it require an extra step for the BR to access the docker image. We wille pass a [https://docs.gitlab.com/ee/user/project/deploy_tokens/#gitlab-deploy-token CI deploy token] as cURL parameter.

	* Go to your <code>Settings -> Repository -> Deploy token</code> and create a token name exactly <code>gitlab-deploy-~~toke~~</code>		* Go to your <code>Settings -> Repository -> Deploy token</code> and create a token name exactly <code>gitlab-deploy-token</code>

	* Add the following parameters to the cURL call in your CI deploy job : <code> --form variables[OPTIONAL_PRIVATE_CI_REGISTRY]=$CI_REGISTRY --form variables[OPTIONAL_PRIVATE_CI_REGISTRY_USER]=$CI_DEPLOY_USER --form variables[OPTIONAL_PRIVATE_CI_REGISTRY_PASSWORD]=$CI_DEPLOY_PASSWORD </code>		* Add the following parameters to the cURL call in your CI deploy job : <code> --form variables[OPTIONAL_PRIVATE_CI_REGISTRY]=$CI_REGISTRY --form variables[OPTIONAL_PRIVATE_CI_REGISTRY_USER]=$CI_DEPLOY_USER --form variables[OPTIONAL_PRIVATE_CI_REGISTRY_PASSWORD]=$CI_DEPLOY_PASSWORD </code>

Cedric.holocher : private repo variables

2024-01-05T00:25:24Z

private repo variables

← Version précédente		Version du 5 janvier 2024 à 00:25
Ligne 184 :		Ligne 184 :
	- echo "=> pushed $IMAGE_TAG"		- echo "=> pushed $IMAGE_TAG"
	</source>		</source>

			=== Private repository ===

			Keeping your repository private can be beneficial for security or privacy. But it require an extra step for the BR to access the docker image. We wille pass a [https://docs.gitlab.com/ee/user/project/deploy_tokens/#gitlab-deploy-token CI deploy token] as cURL parameter.

			* Go to your <code>Settings -> Repository -> Deploy token</code> and create a token name exactly <code>gitlab-deploy-toke</code>

			* Add the following parameters to the cURL call in your CI deploy job : <code> --form variables[OPTIONAL_PRIVATE_CI_REGISTRY]=$CI_REGISTRY --form variables[OPTIONAL_PRIVATE_CI_REGISTRY_USER]=$CI_DEPLOY_USER --form variables[OPTIONAL_PRIVATE_CI_REGISTRY_PASSWORD]=$CI_DEPLOY_PASSWORD </code>

	== Example ==		== Example ==

Cedric.holocher : /* Secret files */

2024-01-05T00:17:38Z

Secret files

← Version précédente		Version du 5 janvier 2024 à 00:17
Ligne 152 :		Ligne 152 :

	=== Secret files ===		=== Secret files ===

			''Be aware that any secret passed this way too is visible to the BR and everyone that has ''ANY'' access to you repository (because they can get the docker image) ! So only do this for a private registry or make sure your setting <code>Settings -> General -> Visibility, project features, permissions</code> only allows for registry access for members''

	Another way to store secrets in your Gitlab repo is <code>Gitlab -> Settings -> CI-CD -> Secure-files</code>. You can upload any (small) secret file here and it will not be exposed ! You can downlod it at buildtime like so :		Another way to store secrets in your Gitlab repo is <code>Gitlab -> Settings -> CI-CD -> Secure-files</code>. You can upload any (small) secret file here and it will not be exposed ! You can downlod it at buildtime like so :
Ligne 182 :		Ligne 184 :
	- echo "=> pushed $IMAGE_TAG"		- echo "=> pushed $IMAGE_TAG"
	</source>		</source>

	~~Be aware that any secret passed this way too is visible to the BR and everyone that has maintainer access to you repository ! If you need help setting up, don't hesitate to ask for help from the BR !~~

	== Example ==		== Example ==

Cedric.holocher : /* Secret files */

2024-01-05T00:10:09Z

Secret files

← Version précédente		Version du 5 janvier 2024 à 00:10
Ligne 153 :		Ligne 153 :
	=== Secret files ===		=== Secret files ===

	Another way to store secrets is <code>Settings/CI-CD/Secure-files</code>. You can upload any (small) secret file here and it will not be exposed ! You can downlod it at buildtime like so :		Another way to store secrets in your Gitlab repo is <code>Gitlab -> Settings -> CI-CD -> Secure-files</code>. You can upload any (small) secret file here and it will not be exposed ! You can downlod it at buildtime like so :

	<source lang=yaml>		<source lang=yaml>
Ligne 184 :		Ligne 184 :

	Be aware that any secret passed this way too is visible to the BR and everyone that has maintainer access to you repository ! If you need help setting up, don't hesitate to ask for help from the BR !		Be aware that any secret passed this way too is visible to the BR and everyone that has maintainer access to you repository ! If you need help setting up, don't hesitate to ask for help from the BR !


	== Example ==		== Example ==

Cedric.holocher : manual download of image

2024-01-05T00:08:50Z

manual download of image

← Version précédente		Version du 5 janvier 2024 à 00:08
Ligne 109 :		Ligne 109 :

	As you commit this file to Gitlab, you should see a new job appear (or look under Build/jobs). Your image should build correctly (if not, it means something is not available to gitlab that is when you build on your computer. Read the job logs and try to fix it !)		As you commit this file to Gitlab, you should see a new job appear (or look under Build/jobs). Your image should build correctly (if not, it means something is not available to gitlab that is when you build on your computer. Read the job logs and try to fix it !)

			=== Checking the image ===

			This step is optional, but it is the easiest way to debug your image ! You can run it locally like so :

			<source lang=bash>
			docker login registry.binets.fr
			docker run --rm registry.binets.fr/<nom.prenom>/<my-gitlab-repo>:<image>
			</source>

			Where <code>image</code> is the number of the image (available in <code>Gitlab -> Deploy -> Container registry</code>) and <code><nom.prenom>/<my-gitlab-repo></code> is the same as in your project Gitlab URL.

			Typically, your app won't start because you forgot a secret file (see below how to manage that !).

	== Automatic deployment ==		== Automatic deployment ==

Tuto pour le déploiement des sites avec Docker - Historique des versions

Daniela.cojocaru le 5 août 2026 à 12:44

Daniela.cojocaru : Cette version a été marquée à traduire

Daniela.cojocaru le 5 août 2026 à 12:36

Cedric.holocher : typo

Cedric.holocher : rephrase

Cedric.holocher : typo

Cedric.holocher : private repo variables

Cedric.holocher : /* Secret files */

Cedric.holocher : /* Secret files */

Cedric.holocher : manual download of image

Daniela.cojocaru : Cette version a été marquée à traduire

Cedric.holocher : typo

Cedric.holocher : rephrase

Cedric.holocher : typo

Cedric.holocher : private repo variables

Cedric.holocher : /* Secret files */

Cedric.holocher : /* Secret files */

Cedric.holocher : manual download of image