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
Copy file name to clipboardExpand all lines: docs/development/airstack-cli/docker_usage.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,18 +195,20 @@ To change the Isaac Sim scene:
195
195
ISAAC_SIM_SCENE=path/to/your_scene.usd airstack up
196
196
```
197
197
198
+
To disable autolaunching the stack and simply spawn idle docker containers (useful for debugging):
199
+
```bash
200
+
AUTOLAUNCH=false airstack up
201
+
```
202
+
198
203
A list of all available environment variables is in the default `.env` file in the project root directory, which allows specifying all the variables in one place.
199
204
When no `--env-file` argument is passed to `docker compose`, it automatically uses this default `.env` file.
200
205
201
-
The top-level env file is reproduced below:
206
+
The default `.env` file is reproduced below:
202
207
```bash
203
208
--8<-- ".env"
204
209
```
205
210
206
211
To override the default `.env` file, you can pass the `--env-file` argument with the syntax `airstack --env-file [env_file] up` (or `docker compose --env-file [env_file] up -d`).
207
212
208
-
Multiple `--env-file` arguments can be passed to compose overriding sets of variables.env` file.
209
-
When overriding, the default `.env` file must be loaded first. The overrides are applied on top of it.
210
-
211
-
212
-
213
+
Multiple `--env-file` arguments can be passed to compose overriding sets of `variables.env` files.
214
+
All subsequent `--env-file` arguments override the previous ones, allowing you to layer configurations.
0 commit comments