You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, in physical deployment, the docker compose file uses environment for all variables, see link and a sample screenshot:
Reasoning for new functionality
For the easy of deployment across different testing environment, this env variable management needs to be consistent and deployment documentation needs to be updated.
The text was updated successfully, but these errors were encountered:
dan-du-car
changed the title
Docker environment needs to be consistent across deployments in both simulation and physical equipments (vehicle, intersection)
Docker environment variable needs to be consistent across deployments in both simulation and physical equipments (vehicle, intersection)
May 23, 2024
dan-du-car
changed the title
Docker environment variable needs to be consistent across deployments in both simulation and physical equipments (vehicle, intersection)
Docker environment variable needs to be consistent across deployments in both simulation and physical equipments (vehicle and intersection)
May 23, 2024
Summary
Environment variables managements are different between simulation (XIL) and physical deployment. In the simulation environment, docker compose file uses a combination of env_file and environment (https://github.com/usdot-fhwa-stol/carma-config/blob/develop/xil_cloud_telematics/docker-compose.yml), see below:
However, in physical deployment, the docker compose file uses environment for all variables, see link and a sample screenshot:
Reasoning for new functionality
For the easy of deployment across different testing environment, this env variable management needs to be consistent and deployment documentation needs to be updated.
The text was updated successfully, but these errors were encountered: