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
The CLI applies configurations via `dstack apply`, which provisions infrastructure, schedules workloads, and manages lifecycle. Runs can be "attached" mode (by default) - interactive, blocks terminal with port forwarding and SSH access, or detached (via `-d`) – background, non-interactive.
38
38
39
-
**Important:** Use `--help` with any CLI command if uncertain about usage or available options.
40
-
39
+
**CRITICAL: Never propose dstack commands or command syntaxes that don't exist.**
40
+
- Only use commands and syntaxes explicitly documented in this skill file or verified via `--help`
41
+
- If uncertain about a command or its syntax, check the documentation or use `--help` rather than guessing
42
+
- Do not invent or assume command names, flags, or argument patterns
43
+
41
44
**Best practices:**
42
45
- Prefer giving run configurations a `name` property for easier management and identification
43
46
- Prefer modifying configuration files over passing parameters to `dstack apply` (unless it's an exception)
@@ -253,6 +256,25 @@ volumes:
253
256
- In attached mode (default), the terminal blocks and shows output - use timeout or Ctrl+C to interrupt if you need to continue with other commands
254
257
- In detached mode (`-d`), runs in background without blocking the terminal
255
258
259
+
**Workflow for applying configurations:**
260
+
261
+
**Important: When displaying CLI output, keep it close to the original format. Prefer showing tables as-is rather than reformatting or summarizing.**
262
+
263
+
**For run configurations (dev-environment, task, service):**
264
+
1. Show the plan by running `echo "n" | dstack apply -f <dstack config file>`
265
+
2. Ask user for confirmation
266
+
3. Once confirmed, run `dstack apply -f <dstack config file> -y -d` (detached mode with auto-confirm)
267
+
4. Show run status with `dstack ps`
268
+
269
+
**For other configurations (fleet, volume, gateway):**
270
+
1. Show the plan by running `dstack apply -f <dstack config file>` (these don't support the "n" trick or `-d` flag)
271
+
2. Ask user for confirmation
272
+
3. Once confirmed, run `dstack apply -f <dstack config file> -y`
273
+
4. Show status with the appropriate command:
274
+
- Fleets: `dstack fleet`
275
+
- Volumes: `dstack volume`
276
+
- Gateways: `dstack gateway`
277
+
256
278
```bash
257
279
# Apply and attach (interactive, blocks terminal with port forwarding)
The CLI applies configurations via `dstack apply`, which provisions infrastructure, schedules workloads, and manages lifecycle. Runs can be "attached" mode (by default) - interactive, blocks terminal with port forwarding and SSH access, or detached (via `-d`) – background, non-interactive.
38
38
39
-
**Important:** Use `--help` with any CLI command if uncertain about usage or available options.
40
-
39
+
**CRITICAL: Never propose dstack commands or command syntaxes that don't exist.**
40
+
- Only use commands and syntaxes explicitly documented in this skill file or verified via `--help`
41
+
- If uncertain about a command or its syntax, check the documentation or use `--help` rather than guessing
42
+
- Do not invent or assume command names, flags, or argument patterns
43
+
41
44
**Best practices:**
42
45
- Prefer giving run configurations a `name` property for easier management and identification
43
46
- Prefer modifying configuration files over passing parameters to `dstack apply` (unless it's an exception)
@@ -253,6 +256,25 @@ volumes:
253
256
- In attached mode (default), the terminal blocks and shows output - use timeout or Ctrl+C to interrupt if you need to continue with other commands
254
257
- In detached mode (`-d`), runs in background without blocking the terminal
255
258
259
+
**Workflow for applying configurations:**
260
+
261
+
**Important: When displaying CLI output, keep it close to the original format. Prefer showing tables as-is rather than reformatting or summarizing.**
262
+
263
+
**For run configurations (dev-environment, task, service):**
264
+
1. Show the plan by running `echo "n" | dstack apply -f <dstack config file>`
265
+
2. Ask user for confirmation
266
+
3. Once confirmed, run `dstack apply -f <dstack config file> -y -d` (detached mode with auto-confirm)
267
+
4. Show run status with `dstack ps`
268
+
269
+
**For other configurations (fleet, volume, gateway):**
270
+
1. Show the plan by running `dstack apply -f <dstack config file>` (these don't support the "n" trick or `-d` flag)
271
+
2. Ask user for confirmation
272
+
3. Once confirmed, run `dstack apply -f <dstack config file> -y`
273
+
4. Show status with the appropriate command:
274
+
- Fleets: `dstack fleet`
275
+
- Volumes: `dstack volume`
276
+
- Gateways: `dstack gateway`
277
+
256
278
```bash
257
279
# Apply and attach (interactive, blocks terminal with port forwarding)
The CLI applies configurations via `dstack apply`, which provisions infrastructure, schedules workloads, and manages lifecycle. Runs can be "attached" mode (by default) - interactive, blocks terminal with port forwarding and SSH access, or detached (via `-d`) – background, non-interactive.
38
38
39
-
**Important:** Use `--help` with any CLI command if uncertain about usage or available options.
40
-
39
+
**CRITICAL: Never propose dstack commands or command syntaxes that don't exist.**
40
+
- Only use commands and syntaxes explicitly documented in this skill file or verified via `--help`
41
+
- If uncertain about a command or its syntax, check the documentation or use `--help` rather than guessing
42
+
- Do not invent or assume command names, flags, or argument patterns
43
+
41
44
**Best practices:**
42
45
- Prefer giving run configurations a `name` property for easier management and identification
43
46
- Prefer modifying configuration files over passing parameters to `dstack apply` (unless it's an exception)
@@ -253,6 +256,25 @@ volumes:
253
256
- In attached mode (default), the terminal blocks and shows output - use timeout or Ctrl+C to interrupt if you need to continue with other commands
254
257
- In detached mode (`-d`), runs in background without blocking the terminal
255
258
259
+
**Workflow for applying configurations:**
260
+
261
+
**Important: When displaying CLI output, keep it close to the original format. Prefer showing tables as-is rather than reformatting or summarizing.**
262
+
263
+
**For run configurations (dev-environment, task, service):**
264
+
1. Show the plan by running `echo "n" | dstack apply -f <dstack config file>`
265
+
2. Ask user for confirmation
266
+
3. Once confirmed, run `dstack apply -f <dstack config file> -y -d` (detached mode with auto-confirm)
267
+
4. Show run status with `dstack ps`
268
+
269
+
**For other configurations (fleet, volume, gateway):**
270
+
1. Show the plan by running `dstack apply -f <dstack config file>` (these don't support the "n" trick or `-d` flag)
271
+
2. Ask user for confirmation
272
+
3. Once confirmed, run `dstack apply -f <dstack config file> -y`
273
+
4. Show status with the appropriate command:
274
+
- Fleets: `dstack fleet`
275
+
- Volumes: `dstack volume`
276
+
- Gateways: `dstack gateway`
277
+
256
278
```bash
257
279
# Apply and attach (interactive, blocks terminal with port forwarding)
0 commit comments