2023-04-07 22:03:28 +02:00
|
|
|
running the following commands should always give podman-rocks-123
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
podman-compose -f project/container-compose.yaml --env-file env-files/project-1.env up
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
podman-compose -f $(pwd)/project/container-compose.yaml --env-file $(pwd)/env-files/project-1.env up
|
|
|
|
|
```
|
2024-05-03 15:31:23 +02:00
|
|
|
|
|
|
|
|
```
|
|
|
|
|
podman-compose -f $(pwd)/project/container-compose.env-file-flat.yaml up
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
podman-compose -f $(pwd)/project/container-compose.env-file-obj.yaml up
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
podman-compose -f $(pwd)/project/container-compose.env-file-obj-optional.yaml up
|
|
|
|
|
```
|
2023-09-13 15:32:56 +02:00
|
|
|
|
|
|
|
|
based on environment variable precedent this command should give podman-rocks-321
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
ZZVAR1=podman-rocks-321 podman-compose -f $(pwd)/project/container-compose.yaml --env-file $(pwd)/env-files/project-1.env up
|
|
|
|
|
```
|
2024-06-05 10:55:40 +02:00
|
|
|
|
|
|
|
|
_The below test should print three environment variables_
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
podman-compose -f $(pwd)/project/container-compose.load-.env-in-project.yaml run --rm app
|
|
|
|
|
|
|
|
|
|
ZZVAR1=This value is overwritten by env-file-tests/.env
|
|
|
|
|
ZZVAR2=This value is loaded from .env in project/ directory
|
|
|
|
|
ZZVAR3=This value is loaded from env-file-tests/.env
|
|
|
|
|
```
|
