Skip to content
Snippets Groups Projects
Commit a998d153 authored by Etxaniz Errazkin, Iñaki's avatar Etxaniz Errazkin, Iñaki
Browse files

Update README.md

parent 0b9ecd5f
No related branches found
No related tags found
No related merge requests found
Pipeline #87396 failed
Stage: build
Stage: deploy
Stage: stop
Show whitespace changes
Inline Side-by-side
Showing
with 5 additions and 5 deletions
README.md
+ 5
− 5
View file @ a998d153
...@@ -16,7 +16,7 @@ In order to use this docker compose you need docker and docker-compose. ...@@ -16,7 +16,7 @@ In order to use this docker compose you need docker and docker-compose.
The docker-compose can be started in different ways depending your purpose. But in all the cases the first step is to download the repo. The docker-compose can be started in different ways depending your purpose. But in all the cases the first step is to download the repo.
```bash ```bash
git clone https://git.code.tecnalia.com/piacere/private/t53-iop-optimizer.git git clone https://git.code.tecnalia.com/piacere/public/the-platform/iop/optimizer.git
cd t53-iop-optimizer cd t53-iop-optimizer
```` ````
NOTE: For develop and debug scenarios the repo relays in git submodules and therefore if we need to build the component images (the typical case) we need to user the "--recurse-submodules" option to download the submodules. Or issuing a "git submodule update --init --recursive" statement latter on. NOTE: For develop and debug scenarios the repo relays in git submodules and therefore if we need to build the component images (the typical case) we need to user the "--recurse-submodules" option to download the submodules. Or issuing a "git submodule update --init --recursive" statement latter on.
...@@ -33,7 +33,7 @@ NOTE: Another posibility could be to edit the .env file directly, but beware of ...@@ -33,7 +33,7 @@ NOTE: Another posibility could be to edit the .env file directly, but beware of
### For production ### For production
By default the project is configured to support the production scenario where we relay in previously uploaded images to the artifactory. The file containing the default variables for this scenario is .env By default the project is configured to support the production scenario where we relay in previously uploaded images to the artifactory. The file containing the default variables for this scenario is .env
```bash ```bash
git clone https://git.code.tecnalia.com/piacere/private/t53-iop-optimizer.git git clone https://git.code.tecnalia.com/piacere/public/the-platform/iop/optimizer.git
cd t53-iop-optimizer cd t53-iop-optimizer
export SERVER_HOST=basedomain.org export SERVER_HOST=basedomain.org
export HTTPS_PORT=8443 export HTTPS_PORT=8443
...@@ -50,7 +50,7 @@ docker-compose down --volumes --remove-orphans ...@@ -50,7 +50,7 @@ docker-compose down --volumes --remove-orphans
### For secure production ### For secure production
By default the project is configured to support the production scenario where we relay in previously uploaded images to the artifactory. The file containing the default variables for this scenario is .env By default the project is configured to support the production scenario where we relay in previously uploaded images to the artifactory. The file containing the default variables for this scenario is .env
```bash ```bash
git clone https://git.code.tecnalia.com/piacere/private/t53-iop-optimizer.git git clone https://git.code.tecnalia.com/piacere/public/the-platform/iop/optimizer.git
cd t53-iop-optimizer cd t53-iop-optimizer
export SERVER_HOST=basedomain.org export SERVER_HOST=basedomain.org
export HTTPS_PORT=8443 export HTTPS_PORT=8443
...@@ -67,7 +67,7 @@ docker-compose --env-file .env.secure down --volumes --remove-orphans ...@@ -67,7 +67,7 @@ docker-compose --env-file .env.secure down --volumes --remove-orphans
Another tipical scenario is to run the docker-compose for building the images after some updates. The file containing the default variables for this scenario is .env.build. Another tipical scenario is to run the docker-compose for building the images after some updates. The file containing the default variables for this scenario is .env.build.
```bash ```bash
git clone --recurse-submodules https://git.code.tecnalia.com/piacere/private/t53-iop-optimizer.git git clone --recurse-submodules https://git.code.tecnalia.com/piacere/public/the-platform/iop/optimizer.git
cd t53-iop-optimizer cd t53-iop-optimizer
docker-compose --env-file .env.build build docker-compose --env-file .env.build build
docker login optima-piacere-docker-dev.artifact.tecnalia.com -u user@domain.net -p repositoryToken docker login optima-piacere-docker-dev.artifact.tecnalia.com -u user@domain.net -p repositoryToken
...@@ -79,7 +79,7 @@ NOTE: For this task as metioned before it is necessary to download the submodule ...@@ -79,7 +79,7 @@ NOTE: For this task as metioned before it is necessary to download the submodule
Another tipical scenario is to run the docker-compose to test the whole solution during development or debug activities inside a development computer. The file containing the default variables for this scenario is .env.int. Another tipical scenario is to run the docker-compose to test the whole solution during development or debug activities inside a development computer. The file containing the default variables for this scenario is .env.int.
```bash ```bash
git clone --recurse-submodules https://git.code.tecnalia.com/piacere/private/t53-iop-optimizer.git git clone --recurse-submodules https://git.code.tecnalia.com/piacere/public/the-platform/iop/optimizer.git
cd t53-iop-optimizer cd t53-iop-optimizer
export CERTIFICATE_SIGNING_KEY_PASSPHRASE=thesecretkeytodecryptthecaprivatekey export CERTIFICATE_SIGNING_KEY_PASSPHRASE=thesecretkeytodecryptthecaprivatekey
docker-compose --env-file .env.int build docker-compose --env-file .env.int build
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment