revisium 2.0.1 → 2.2.0

package/docs/authentication.md

@@ -8,8 +8,8 @@ JWT token from Revisium UI. Best for interactive use.
 
 ### Get Your Token
 
-- **Cloud:** <https://cloud.revisium.io/get-mcp-token>
-- **Self-hosted:** `https://your-host/get-mcp-token`
+- **Cloud:** <https://cloud.revisium.io/get-token>
+- **Self-hosted:** `https://your-host/get-token`
 
 ### Usage
 
@@ -57,7 +57,7 @@ If no credentials are provided, you'll be prompted:
 
 ```text
 Choose authentication method:
-  > Token (copy from https://cloud.revisium.io/get-mcp-token)
+  > Token (copy from https://cloud.revisium.io/get-token)
     API Key (for automated access)
     Username & Password
 

package/docs/configuration.md

@@ -2,16 +2,50 @@
 
 ## Environment Variables
 
-All commands support configuration via environment variables:
+All commands support configuration via environment variables.
+
+### Single-Endpoint Commands (schema, migrate, rows)
 
 | Variable | Description | Example |
 |----------|-------------|---------|
-| `REVISIUM_URL` | Revisium URL with host/org/project/branch | `revisium://cloud.revisium.io/org/proj/main` |
-| `REVISIUM_TOKEN` | JWT authentication token | - |
-| `REVISIUM_USERNAME` | Username (for password auth) | - |
-| `REVISIUM_PASSWORD` | Password (for password auth) | - |
+| `REVISIUM_URL` | Revisium URL (see [URL Format](./url-format.md)) | `revisium://cloud.revisium.io/org/proj/main` |
+| `REVISIUM_TOKEN` | JWT authentication token | `eyJhbGciOiJIUzI1NiIs...` |
+| `REVISIUM_API_KEY` | API key (for automated access) | `ak_xxxxxxxxxxxxx` |
+| `REVISIUM_USERNAME` | Username (for password auth) | `admin` |
+| `REVISIUM_PASSWORD` | Password (for password auth) | `secret` |
+
+### Sync Commands (source/target)
+
+| Variable | Description |
+|----------|-------------|
+| `REVISIUM_SOURCE_URL` | Source project URL |
+| `REVISIUM_SOURCE_TOKEN` | Source JWT token |
+| `REVISIUM_SOURCE_API_KEY` | Source API key |
+| `REVISIUM_SOURCE_USERNAME` | Source username |
+| `REVISIUM_SOURCE_PASSWORD` | Source password |
+| `REVISIUM_TARGET_URL` | Target project URL |
+| `REVISIUM_TARGET_TOKEN` | Target JWT token |
+| `REVISIUM_TARGET_API_KEY` | Target API key |
+| `REVISIUM_TARGET_USERNAME` | Target username |
+| `REVISIUM_TARGET_PASSWORD` | Target password |
+
+### Authentication Priority
+
+When using `--url`, authentication is resolved in this order:
+
+1. **URL query parameter** - `?token=...` or `?apikey=...`
+2. **URL credentials** - `user:pass@host`
+3. **Environment variable** - `REVISIUM_TOKEN` > `REVISIUM_API_KEY` > `REVISIUM_USERNAME/PASSWORD`
+4. **Interactive prompt** - if running in terminal
+
+**Important:** You can use `--url` to specify host/org/project/branch and provide credentials via environment:
 
-See [URL Format](./url-format.md) for complete URL syntax.
+```bash
+# URL specifies target, credentials from environment
+export REVISIUM_TOKEN=$MY_TOKEN
+revisium migrate apply --file ./migrations.json \
+  --url revisium://cloud.revisium.io/myorg/myproject/master
+```
 
 ## .env File
 
@@ -47,8 +81,18 @@ revisium migrate apply --file ./migrations.json
 Override environment variables with CLI options:
 
 ```bash
+# Full URL with token in query parameter
+revisium schema save --folder ./schemas \
+  --url revisium://cloud.revisium.io/my-org/my-project/develop?token=$TOKEN
+
+# URL without credentials (uses REVISIUM_TOKEN from environment)
+export REVISIUM_TOKEN=$MY_TOKEN
+revisium schema save --folder ./schemas \
+  --url revisium://cloud.revisium.io/my-org/my-project/develop
+
+# URL with credentials in URL
 revisium schema save --folder ./schemas \
-  --url revisium://api.example.com/my-org/my-project/develop
+  --url revisium://admin:secret@localhost:8080/my-org/my-project/develop
 ```
 
 ## Priority
@@ -67,9 +111,14 @@ Configuration is resolved in this order (highest to lowest):
 # Development (uses .env defaults)
 revisium rows upload --folder ./data
 
-# Production (override with CLI)
-revisium rows upload --folder ./data \
+# Production with token in URL
+revisium rows upload --folder ./data --commit \
   --url revisium://prod.example.com/prod-org/main-app/master?token=$PROD_TOKEN
+
+# Production with token in environment (recommended for CI/CD)
+export REVISIUM_TOKEN=$PROD_TOKEN
+revisium rows upload --folder ./data --commit \
+  --url revisium://prod.example.com/prod-org/main-app/master
 ```
 
 ### Multiple Environments

package/docs/docker-deployment.md

@@ -9,7 +9,7 @@ The CLI is available as a Docker image for CI/CD pipelines and containerized env
 docker pull revisium/revisium-cli
 
 # Or specific version
-docker pull revisium/revisium-cli:1.1.1
+docker pull revisium/revisium-cli:2.0.0
 ```
 
 ## Environment Variables
@@ -17,13 +17,14 @@ docker pull revisium/revisium-cli:1.1.1
 | Variable | Description | Required |
 |----------|-------------|----------|
 | `REVISIUM_URL` | Revisium URL (see [URL Format](./url-format.md)) | Yes |
-| `REVISIUM_TOKEN` | JWT authentication token | Yes* |
-| `REVISIUM_USERNAME` | Username (alternative to token) | Yes* |
-| `REVISIUM_PASSWORD` | Password (alternative to token) | Yes* |
-| `MIGRATIONS_FILE` | Path to migrations file | No |
-| `DATA_DIR` | Path to data directory | No |
+| `REVISIUM_TOKEN` | JWT authentication token (recommended) | Yes* |
+| `REVISIUM_API_KEY` | API key (for automated access) | Yes* |
+| `REVISIUM_USERNAME` | Username (for password auth) | Yes* |
+| `REVISIUM_PASSWORD` | Password (for password auth) | Yes* |
 
-*Either `REVISIUM_TOKEN` or `REVISIUM_USERNAME`/`REVISIUM_PASSWORD` is required.
+*One authentication method is required: `REVISIUM_TOKEN`, `REVISIUM_API_KEY`, or `REVISIUM_USERNAME`/`REVISIUM_PASSWORD`.
+
+**Note:** The `--url` parameter can specify host/org/project/branch while credentials come from environment variables. This is the recommended approach for CI/CD.
 
 ## CI/CD Workflow (Prisma-like)
 
@@ -97,7 +98,7 @@ Use migrations in Kubernetes with init container for schema deployment:
 ### Build Custom Image with Migrations
 
 ```dockerfile
-FROM revisium/revisium-cli:1.1.1
+FROM revisium/revisium-cli:2.0.0
 
 # Copy migrations
 COPY revisium/migrations.json /app/migrations.json
@@ -150,7 +151,7 @@ For initial data seeding, include data files in your Docker image:
 ### Dockerfile with Data
 
 ```dockerfile
-FROM revisium/revisium-cli:1.1.1
+FROM revisium/revisium-cli:2.0.0
 
 # Copy migrations
 COPY revisium/migrations.json /app/migrations.json
@@ -195,7 +196,34 @@ spec:
 
 ## GitHub Actions Examples
 
-### Basic Migration Apply
+### Basic Migration Apply (Token - Recommended)
+
+```yaml
+name: Deploy
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Apply Revisium Migrations
+        run: npx revisium migrate apply --file ./revisium/migrations.json --commit
+        env:
+          REVISIUM_URL: revisium://cloud.revisium.io/${{ vars.ORG }}/${{ vars.PROJECT }}/main
+          REVISIUM_TOKEN: ${{ secrets.REVISIUM_TOKEN }}
+```
+
+### Basic Migration Apply (Username/Password)
 
 ```yaml
 name: Deploy
@@ -296,7 +324,15 @@ jobs:
 Run CLI commands directly with Docker:
 
 ```bash
-# Apply migrations
+# Apply migrations (with token - recommended)
+docker run --rm \
+  -e REVISIUM_URL=revisium://cloud.revisium.io/myorg/myproject/main \
+  -e REVISIUM_TOKEN=$REVISIUM_TOKEN \
+  -v ./revisium/migrations.json:/app/migrations.json \
+  revisium/revisium-cli \
+  revisium migrate apply --file /app/migrations.json --commit
+
+# Apply migrations (with username/password)
 docker run --rm \
   -e REVISIUM_URL=revisium://cloud.revisium.io/myorg/myproject/main \
   -e REVISIUM_USERNAME=admin \
@@ -308,8 +344,7 @@ docker run --rm \
 # Upload data
 docker run --rm \
   -e REVISIUM_URL=revisium://cloud.revisium.io/myorg/myproject/main \
-  -e REVISIUM_USERNAME=admin \
-  -e REVISIUM_PASSWORD=secret \
+  -e REVISIUM_TOKEN=$REVISIUM_TOKEN \
   -v ./data:/app/data \
   revisium/revisium-cli \
   revisium rows upload --folder /app/data --commit

package/docs/migrate-commands.md

@@ -15,15 +15,23 @@ revisium migrate save --file <path>
 | Option | Description | Required |
 |--------|-------------|----------|
 | `-f, --file <path>` | Output file path | Yes |
+| `--url <url>` | Revisium URL (see [URL Format](./url-format.md)) | No* |
+
+*If `--url` is not provided, uses `REVISIUM_URL` environment variable or prompts interactively.
 
 ### Examples
 
 ```bash
-# Save migrations
+# Save migrations (using REVISIUM_URL from environment)
 revisium migrate save --file ./migrations.json
 
-# Save from specific branch
-revisium migrate save --file ./migrations.json --branch develop
+# Save with explicit URL and token
+revisium migrate save --file ./migrations.json \
+  --url revisium://cloud.revisium.io/myorg/myproject/master?token=$TOKEN
+
+# Save from head revision
+revisium migrate save --file ./migrations.json \
+  --url revisium://cloud.revisium.io/myorg/myproject/master:head?token=$TOKEN
 ```
 
 ## migrate apply
@@ -40,18 +48,28 @@ revisium migrate apply --file <path> [--commit]
 |--------|-------------|----------|
 | `-f, --file <path>` | Migrations file path | Yes |
 | `-c, --commit` | Create revision after applying | No |
+| `--url <url>` | Revisium URL (see [URL Format](./url-format.md)) | No* |
+
+*If `--url` is not provided, uses `REVISIUM_URL` environment variable or prompts interactively.
 
 ### Examples
 
 ```bash
-# Apply migrations
+# Apply migrations (using REVISIUM_URL from environment)
 revisium migrate apply --file ./migrations.json
 
 # Apply and create revision
 revisium migrate apply --file ./migrations.json --commit
 
-# Apply to different environment
-revisium migrate apply --file ./migrations.json --url https://staging.example.com
+# Apply to specific environment with token
+revisium migrate apply --file ./migrations.json --commit \
+  --url revisium://staging.example.com/myorg/myproject/master?token=$TOKEN
+
+# Apply with credentials via environment variables
+export REVISIUM_USERNAME=admin
+export REVISIUM_PASSWORD=secret
+revisium migrate apply --file ./migrations.json --commit \
+  --url revisium://cloud.revisium.io/myorg/myproject/master
 ```
 
 ## Migration Format
@@ -126,20 +144,27 @@ Deletes a table:
 
 ```bash
 # Export from source
-revisium migrate save --file ./migrations.json --url https://source.example.com
+revisium migrate save --file ./migrations.json \
+  --url revisium://source.example.com/myorg/myproject/master:head?token=$SOURCE_TOKEN
 
 # Apply to target
-revisium migrate apply --file ./migrations.json --url https://target.example.com --commit
+revisium migrate apply --file ./migrations.json --commit \
+  --url revisium://target.example.com/myorg/myproject/master?token=$TARGET_TOKEN
 ```
 
 ### Version Control
 
 ```bash
 # Save migrations to git
-revisium migrate save --file ./migrations.json
+revisium migrate save --file ./migrations.json \
+  --url revisium://cloud.revisium.io/myorg/myproject/master?token=$TOKEN
 git add migrations.json
 git commit -m "Add user phone field migration"
 
-# Apply in CI/CD
+# Apply in CI/CD (credentials via environment)
+export REVISIUM_URL=revisium://cloud.revisium.io/myorg/myproject/master
+export REVISIUM_TOKEN=$DEPLOY_TOKEN
 revisium migrate apply --file ./migrations.json --commit
 ```
+
+See [URL Format](./url-format.md) for complete URL syntax and [Authentication](./authentication.md) for auth options.

package/docs/rows-commands.md

@@ -16,18 +16,26 @@ revisium rows save --folder <path> [--tables <list>]
 |--------|-------------|----------|
 | `-f, --folder <path>` | Output folder for row files | Yes |
 | `-t, --tables <list>` | Comma-separated table IDs | No (all tables) |
+| `--url <url>` | Revisium URL (see [URL Format](./url-format.md)) | No* |
+
+*If `--url` is not provided, uses `REVISIUM_URL` environment variable or prompts interactively.
 
 ### Examples
 
 ```bash
-# Export all tables
+# Export all tables (using REVISIUM_URL from environment)
 revisium rows save --folder ./data
 
 # Export specific tables
 revisium rows save --folder ./data --tables users,posts
 
-# Export from specific branch
-revisium rows save --folder ./data --branch develop
+# Export with explicit URL and token
+revisium rows save --folder ./data \
+  --url revisium://cloud.revisium.io/myorg/myproject/master?token=$TOKEN
+
+# Export from head revision
+revisium rows save --folder ./data \
+  --url revisium://cloud.revisium.io/myorg/myproject/master:head?token=$TOKEN
 ```
 
 ### Output Format
@@ -69,11 +77,12 @@ revisium rows upload --folder <path> [options]
 | `-t, --tables <list>` | Comma-separated table IDs | All tables |
 | `--batch-size <n>` | Rows per batch | 100 |
 | `-c, --commit` | Create revision after upload | false |
+| `--url <url>` | Revisium URL (see [URL Format](./url-format.md)) | Environment |
 
 ### Examples
 
 ```bash
-# Basic upload
+# Basic upload (using REVISIUM_URL from environment)
 revisium rows upload --folder ./data
 
 # Upload specific tables
@@ -84,6 +93,16 @@ revisium rows upload --folder ./data --batch-size 500
 
 # Upload and create revision
 revisium rows upload --folder ./data --commit
+
+# Upload with explicit URL and token
+revisium rows upload --folder ./data --commit \
+  --url revisium://cloud.revisium.io/myorg/myproject/master?token=$TOKEN
+
+# Upload with credentials via environment variables
+export REVISIUM_USERNAME=admin
+export REVISIUM_PASSWORD=secret
+revisium rows upload --folder ./data --commit \
+  --url revisium://cloud.revisium.io/myorg/myproject/master
 ```
 
 ## Features
@@ -145,16 +164,20 @@ revisium rows upload --folder ./data --tables users --commit
 
 ```bash
 # Export from source
-revisium rows save --folder ./data --url https://source.example.com
+revisium rows save --folder ./data \
+  --url revisium://source.example.com/myorg/myproject/master:head?token=$SOURCE_TOKEN
 
 # Import to target
-revisium rows upload --folder ./data --url https://target.example.com --commit
+revisium rows upload --folder ./data --commit \
+  --url revisium://target.example.com/myorg/myproject/master?token=$TARGET_TOKEN
 ```
 
 ### Incremental Updates
 
 ```bash
 # Edit local JSON files
-# Then upload changes
+# Then upload changes (using REVISIUM_URL from environment)
 revisium rows upload --folder ./data --commit
 ```
+
+See [URL Format](./url-format.md) for complete URL syntax and [Authentication](./authentication.md) for auth options.

package/docs/schema-commands.md

@@ -15,15 +15,27 @@ revisium schema save --folder <path>
 | Option | Description | Required |
 |--------|-------------|----------|
 | `-f, --folder <path>` | Output folder for schema files | Yes |
+| `--url <url>` | Revisium URL (see [URL Format](./url-format.md)) | No* |
+
+*If `--url` is not provided, uses `REVISIUM_URL` environment variable or prompts interactively.
 
 ### Examples
 
 ```bash
-# Export all schemas
+# Export all schemas (using REVISIUM_URL from environment)
 revisium schema save --folder ./schemas
 
-# Export from specific branch
-revisium schema save --folder ./schemas --branch develop
+# Export with explicit URL and token
+revisium schema save --folder ./schemas \
+  --url revisium://cloud.revisium.io/myorg/myproject/master?token=$TOKEN
+
+# Export from head revision
+revisium schema save --folder ./schemas \
+  --url revisium://cloud.revisium.io/myorg/myproject/master:head?token=$TOKEN
+
+# Local development
+revisium schema save --folder ./schemas \
+  --url revisium://localhost:8080/admin/demo/master?token=$TOKEN
 ```
 
 ### Output Format
@@ -111,11 +123,15 @@ Typical workflow for schema management:
 
 ```bash
 # 1. Export schemas from source environment
-revisium schema save --folder ./schemas --url https://source.example.com
+revisium schema save --folder ./schemas \
+  --url revisium://source.example.com/myorg/myproject/master:head?token=$SOURCE_TOKEN
 
 # 2. Convert to migrations
 revisium schema create-migrations --schemas-folder ./schemas --file ./migrations.json
 
 # 3. Apply to target environment
-revisium migrate apply --file ./migrations.json --url https://target.example.com --commit
+revisium migrate apply --file ./migrations.json --commit \
+  --url revisium://target.example.com/myorg/myproject/master?token=$TARGET_TOKEN
 ```
+
+See [URL Format](./url-format.md) for complete URL syntax and authentication options.

package/docs/sync-commands.md

@@ -114,7 +114,14 @@ revisium sync all --source <url> --target <url> [options]
 
 ### Options
 
-Combines all options from `sync schema` and `sync data`.
+| Option | Description | Default |
+|--------|-------------|---------|
+| `-s, --source <url>` | Source project URL | Required |
+| `-t, --target <url>` | Target project URL | Required |
+| `--tables <list>` | Comma-separated tables | All tables |
+| `--batch-size <n>` | Rows per batch | 100 |
+| `-c, --commit` | Create revision after sync | false |
+| `-d, --dry-run` | Preview without applying | false |
 
 ### Examples
 
@@ -133,24 +140,49 @@ revisium sync all \
   --commit
 ```
 
-## Environment Variables
+## Authentication
+
+Sync commands support separate authentication for source and target.
+
+### Environment Variables
 
-For non-interactive usage:
+| Variable | Description |
+|----------|-------------|
+| `REVISIUM_SOURCE_URL` | Source project URL |
+| `REVISIUM_SOURCE_TOKEN` | Source JWT token |
+| `REVISIUM_SOURCE_API_KEY` | Source API key |
+| `REVISIUM_SOURCE_USERNAME` | Source username |
+| `REVISIUM_SOURCE_PASSWORD` | Source password |
+| `REVISIUM_TARGET_URL` | Target project URL |
+| `REVISIUM_TARGET_TOKEN` | Target JWT token |
+| `REVISIUM_TARGET_API_KEY` | Target API key |
+| `REVISIUM_TARGET_USERNAME` | Target username |
+| `REVISIUM_TARGET_PASSWORD` | Target password |
+
+### Non-Interactive Usage
 
 ```bash
-# Source
-REVISIUM_SOURCE_URL=revisium://cloud.revisium.io/org/proj/master:head
-REVISIUM_SOURCE_TOKEN=<YOUR_SOURCE_TOKEN>
+# Using tokens
+export REVISIUM_SOURCE_TOKEN=<YOUR_SOURCE_TOKEN>
+export REVISIUM_TARGET_TOKEN=<YOUR_TARGET_TOKEN>
 
-# Target
-REVISIUM_TARGET_URL=revisium://localhost:8080/org/proj
-REVISIUM_TARGET_TOKEN=<YOUR_TARGET_TOKEN>
+revisium sync all \
+  --source revisium://cloud.revisium.io/org/proj/master:head \
+  --target revisium://localhost:8080/org/proj/master \
+  --commit
 ```
 
-Then run without URL arguments:
-
 ```bash
-revisium sync all --commit
+# Using username/password
+export REVISIUM_SOURCE_USERNAME=admin
+export REVISIUM_SOURCE_PASSWORD=source_secret
+export REVISIUM_TARGET_USERNAME=admin
+export REVISIUM_TARGET_PASSWORD=target_secret
+
+revisium sync all \
+  --source revisium://source.example.com/org/proj/master:head \
+  --target revisium://target.example.com/org/proj/master \
+  --commit
 ```
 
 ## Examples

package/docs/url-format.md

@@ -63,8 +63,8 @@ revisium migrate apply --file ./migrations.json \
 ```
 
 Get your token:
-- **Cloud:** https://cloud.revisium.io/get-mcp-token
-- **Self-hosted:** https://your-host/get-mcp-token
+- **Cloud:** https://cloud.revisium.io/get-token
+- **Self-hosted:** https://your-host/get-token
 
 ### API Key Authentication
 

package/e2e/setup/global-setup.ts

@@ -1,6 +1,6 @@
 import * as fs from 'fs';
 import * as path from 'path';
-import { startDocker, waitForHealthy } from '../utils/docker-helper';
+import { waitForHealthy } from '../utils/docker-helper';
 import { api } from '../utils/api-client';
 import { E2E_CONFIG } from '../utils/constants';
 
@@ -11,19 +11,13 @@ export default async function globalSetup(): Promise<void> {
   console.log('E2E Global Setup');
   console.log('========================================\n');
 
-  // 1. Start Docker containers
-  startDocker();
+  console.log('Waiting for Revisium to be ready...');
+  await waitForHealthy(`${E2E_CONFIG.API_URL}/health/readiness`);
 
-  // 2. Wait for Revisium to be healthy
-  console.log('\nWaiting for Revisium to be ready...');
-  await waitForHealthy(`${E2E_CONFIG.API_URL}/health`);
-
-  // 3. Login and get token
   console.log('\nLogging in as admin...');
   const token = await api.login();
   console.log('Login successful');
 
-  // 4. Save environment for test workers
   const envData = {
     E2E_API_URL: E2E_CONFIG.API_URL,
     E2E_ADMIN_TOKEN: token,

package/e2e/setup/global-teardown.ts

@@ -1,7 +1,6 @@
 import * as fs from 'fs';
 import * as path from 'path';
 import { execSync } from 'child_process';
-import { stopDocker } from '../utils/docker-helper';
 
 const ENV_FILE = path.join(process.cwd(), '.e2e-env.json');
 
@@ -10,10 +9,6 @@ export default function globalTeardown(): void {
   console.log('E2E Global Teardown');
   console.log('========================================\n');
 
-  // 1. Stop Docker containers
-  stopDocker();
-
-  // 2. Merge coverage if E2E coverage exists
   const nycOutputDir = path.join(process.cwd(), '.nyc_output');
   if (fs.existsSync(nycOutputDir)) {
     const files = fs
@@ -32,7 +27,6 @@ export default function globalTeardown(): void {
     }
   }
 
-  // 3. Cleanup env file
   if (fs.existsSync(ENV_FILE)) {
     fs.rmSync(ENV_FILE);
     console.log(`\nCleaned up ${ENV_FILE}`);

package/e2e/utils/constants.ts

@@ -2,8 +2,6 @@ export const E2E_CONFIG = {
   API_URL: 'http://localhost:8082',
   ADMIN_USERNAME: 'admin',
   ADMIN_PASSWORD: 'admin',
-  DOCKER_COMPOSE_FILE: 'e2e/docker-compose.e2e.yml',
-  DOCKER_PROJECT_NAME: 'revisium-cli-e2e',
   HEALTH_CHECK_TIMEOUT: 60000,
   HEALTH_CHECK_INTERVAL: 1000,
 };

package/e2e/utils/docker-helper.ts

@@ -1,28 +1,5 @@
-import { execSync } from 'child_process';
 import { E2E_CONFIG } from './constants';
 
-export function startDocker(): void {
-  console.log('Starting Docker containers...');
-
-  execSync(
-    `docker compose -f ${E2E_CONFIG.DOCKER_COMPOSE_FILE} -p ${E2E_CONFIG.DOCKER_PROJECT_NAME} up -d --wait`,
-    { stdio: 'inherit' },
-  );
-
-  console.log('Docker containers started');
-}
-
-export function stopDocker(): void {
-  console.log('Stopping Docker containers...');
-
-  execSync(
-    `docker compose -f ${E2E_CONFIG.DOCKER_COMPOSE_FILE} -p ${E2E_CONFIG.DOCKER_PROJECT_NAME} down -v`,
-    { stdio: 'inherit' },
-  );
-
-  console.log('Docker containers stopped');
-}
-
 export async function waitForHealthy(
   url: string,
   timeout: number = E2E_CONFIG.HEALTH_CHECK_TIMEOUT,