.env: separate unique deployment data from service versions

[coesensbert]

the .env currently has specific deployment data and the service versions. This files is in .gitignore so it's not possible to just git pull newer versions without manual adjustments.

Test separate environment files to have the versions in one that is not in .gitignore

[coesensbert]

this!

The .env file in the project root, and the env_file: field in the Compose file are two different concepts.

The .env is for settings a default environment for Compose. Values set in this file can be used within the Compose file.

The env_file: field is for setting the default environment for a container. Values set in this can be used in the container, but not in the Compose file.

means versions go into .env and others in secrets.env and specified at each container that needs it

[coesensbert]

only way i found was to work with two env files in the startup cmd docker compose --env-file .secrets.env --env-file .env up -d

added changes to, already tested 02. Still have to do dev.grid.tf https://github.com/threefoldtech/grid_deployment/tree/development/docker-compose/devnet

[coesensbert]

env var precedence docs: https://docs.docker.com/compose/environment-variables/envvars-precedence/

[coesensbert]

Apply to all running devnet grid stacks:

• [x] *.dev.grid.tf
• [x] *.02.dev.grid.tf
• [x] *.bknd3.dev.ninja.tf
• [x] *.bknd4.dev.ninja.tf
• [x] *.compose.dev.ninja.tf

[coesensbert]

all done, docs will follow

in short:

• change the version of a service on the grid_deployment repo in the .env file first!! And push the change. This will be our source of truth.
• go to a grid stack and do: git pull -r
• then do: docker compose --env-file .secrets.env --env-file .env up -d
• done

[coesensbert]

all changes for devnet also pushed to test and mainnet