kctl-dokploy 0.5.0__tar.gz

kctl_dokploy-0.5.0/.gitignore

@@ -0,0 +1,33 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+*.egg
+dist/
+build/
+.eggs/
+
+# Virtual environments
+.venv/
+venv/
+
+# IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# Testing
+.pytest_cache/
+.coverage
+htmlcov/
+.mypy_cache/
+.ruff_cache/
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Environment
+.env
+.env.local

kctl_dokploy-0.5.0/CHANGELOG.md

@@ -0,0 +1,61 @@
+# Changelog
+
+All notable changes to kctl-dokploy.
+
+## [0.4.3] — 2026-04-19
+
+### Added
+- `backups pull` / `run-wait` / `download` log lines now carry an `[HH:MM:SS]`
+  wall-clock prefix. Operators can see elapsed time between phases (trigger →
+  S3 poll → download → decompress → drop-recreate → pg_restore) at a glance.
+  Implemented via a local `_TimestampedLog` wrapper that delegates to the
+  shared `OutputManager` — no cross-CLI behavior change.
+
+## [0.4.2] — 2026-04-19
+
+### Fixed
+- `backups pull` (and `backups run-wait`) now discover backups under the
+  NEW hierarchical S3 layout used by current Dokploy versions. Previous
+  Dokploy releases wrote objects under a flat
+  `<backup.prefix>-<timestamp>.<ext>` layout; recent Dokploy versions now
+  write them under `<compose.appName>_<serviceName>/<backup.prefix>/<timestamp>.<ext>`
+  (falling back to `<compose.appName>/<backup.prefix>/<timestamp>.<ext>`
+  when no `serviceName` is set on the backup config). The pull helper was
+  only scanning `<backup.prefix>` and therefore picked stale files (or
+  timed out waiting for a fresh trigger) on upgraded instances. The
+  helper now scans all candidate prefixes and returns the globally-newest
+  object. Non-compose backup types (postgres/mysql/mariadb/mongo) retain
+  the single-prefix behavior. Matches are filtered by DB name as
+  defense-in-depth.
+
+## [0.4.1] — 2026-04-19
+
+### Added
+- `backups pull <backup_id> --target-db ...` — one-command end-to-end flow:
+  trigger (optional) → wait → download → decompress → drop+recreate target
+  DB → pg_restore. Supports both Dokploy-managed target composes
+  (`--target-compose`) and raw postgres hosts (`--target-host` for local
+  dev). Auto-detects custom vs plain SQL format via PGDMP magic bytes.
+- `backups run-wait <backup_id>` — trigger a manual backup and poll S3
+  until the new object appears. Prints the resulting S3 key.
+- `backups download <s3_key> --destination <id>` — standalone S3 download
+  using a Dokploy destination's stored credentials.
+
+### Fixed
+- `backups list-files` now talks to S3 directly via boto3, bypassing
+  Dokploy's buggy `/backup.listBackupFiles` endpoint. No longer errors
+  with "Input validation failed" when called without `--search`; lists
+  everything under the destination by default. Added `--prefix` for
+  S3-side filtering and `--limit` (default 200). Removed the `--server`
+  flag which was not actually needed for direct S3 access.
+- `dokploy-admin` SKILL.extra.md runbook now matches the actual CLI
+  surface — previously documented 5 commands (`dump-compose`, `download`,
+  `run-wait`, `refresh`, `restore-local`) that had been removed in the
+  Dokploy-native redesign. `download` / `run-wait` / `pull` (formerly
+  `refresh`) are now re-introduced as thin boto3 helpers.
+
+### Notes
+- SSH-based commands (`dump-compose`, `restore-local`, `refresh`) remain
+  deleted — the Dokploy-native SSE restore (`backups restore`) is the
+  right tool for Dokploy-managed targets. `backups pull` fills the gap
+  for dev loops targeting a raw postgres on the developer's workstation.

kctl_dokploy-0.5.0/PKG-INFO

@@ -0,0 +1,18 @@
+Metadata-Version: 2.4
+Name: kctl-dokploy
+Version: 0.5.0
+Summary: Kodemeio Dokploy CLI — manage Dokploy deployment platform
+Requires-Python: >=3.12
+Requires-Dist: boto3>=1.35.0
+Requires-Dist: httpx>=0.28.0
+Requires-Dist: kctl-lib>=0.4.0
+Requires-Dist: pydantic>=2.10.0
+Requires-Dist: pyyaml>=6.0.2
+Requires-Dist: rich>=13.9.0
+Requires-Dist: typer>=0.15.0
+Provides-Extra: dev
+Requires-Dist: mypy>=1.14.0; extra == 'dev'
+Requires-Dist: pytest-httpx>=0.35.0; extra == 'dev'
+Requires-Dist: pytest>=8.3.0; extra == 'dev'
+Requires-Dist: ruff>=0.9.0; extra == 'dev'
+Requires-Dist: types-pyyaml>=6.0.0; extra == 'dev'

kctl_dokploy-0.5.0/README.md

@@ -0,0 +1,475 @@
+# kctl-dokploy
+
+Kodemeio Dokploy CLI -- manage your Dokploy deployment platform and run declarative 13-phase deployment pipelines.
+
+## Installation
+
+```bash
+uv tool install ./packages/kctl-dokploy
+```
+
+To upgrade after code changes:
+
+```bash
+uv tool install --force --reinstall ./packages/kctl-dokploy
+```
+
+## Quick Start
+
+```bash
+# Configure connection (interactive)
+kctl-dokploy config init
+
+# Verify connectivity
+kctl-dokploy config test
+
+# Dashboard overview
+kctl-dokploy dashboard show
+
+# List all projects
+kctl-dokploy projects list
+
+# List all compose services
+kctl-dokploy compose list
+```
+
+### Deploy Workflow
+
+The primary workflow uses declarative YAML manifests stored in `deploys/instances/`.
+
+```bash
+# Full deploy (all phases in one command)
+kctl-dokploy deploy apply -f deploys/instances/production/mac-react-sfa.yaml
+
+# Staged deploy (for troubleshooting)
+kctl-dokploy deploy setup -f deploys/instances/production/mac-react-sfa.yaml   # Stage 1
+kctl-dokploy deploy run   -f deploys/instances/production/mac-react-sfa.yaml   # Stage 2
+kctl-dokploy deploy post  -f deploys/instances/production/mac-react-sfa.yaml   # Stage 3
+
+# Batch deploy all manifests in a directory
+kctl-dokploy deploy apply-all -d deploys/instances/production/
+
+# Validate a manifest without deploying
+kctl-dokploy deploy validate -f deploys/instances/production/mac-react-sfa.yaml
+
+# Check current state vs manifest (dry-run)
+kctl-dokploy deploy status -f deploys/instances/production/mac-react-sfa.yaml
+
+# Dry-run any stage
+kctl-dokploy deploy apply -f deploys/instances/production/mac-react-sfa.yaml --dry-run
+```
+
+### Preflight Checks
+
+```bash
+# Run preflight gates before deploying
+kctl-dokploy deploy preflight -f deploys/instances/production/mac-react-sfa.yaml
+
+# Run preflight for all manifests in a directory
+kctl-dokploy deploy preflight-all -d deploys/instances/production/
+
+# Filter by server
+kctl-dokploy deploy preflight-all -d deploys/instances/production/ --server mac-prod-01
+
+# Run specific gates only
+kctl-dokploy deploy preflight -f <manifest> --gates dns,database,env_sync
+```
+
+### Troubleshooting
+
+```bash
+# Diagnose a failed deployment by manifest
+kctl-dokploy deploy troubleshoot -f deploys/instances/production/mac-react-sfa.yaml
+
+# Diagnose by compose service ID
+kctl-dokploy deploy troubleshoot --compose OEK_dJRQZZMo9HKbQrQ0z
+
+# View deployment logs
+kctl-dokploy compose deployments logs --compose <id>
+```
+
+### Live Container Log Streaming
+
+`kctl-dokploy compose service-logs` fetches runtime container stdout/stderr
+(the actual Odoo/postgres/etc. output — not Dokploy build logs). By default
+it returns a snapshot; pass `-f` / `--follow` to stream until Ctrl-C.
+
+```bash
+# Snapshot — last 200 lines for a specific service
+kctl-dokploy compose service-logs <compose-id> --service odoo-web --tail 200
+
+# Live tail — streams via SSH to the compose's server
+kctl-dokploy compose service-logs <compose-id> --service odoo-web -f
+```
+
+Remote streaming uses `ssh ... docker logs -f <container>` with a 10s
+connect timeout and `StrictHostKeyChecking=accept-new`. Local composes
+skip SSH and invoke `docker logs -f` directly. `kctl-odoo logs tail` wraps
+this command for Odoo-specific filters (module, request, level).
+
+### Server Migration
+
+```bash
+kctl-dokploy deploy migrate validate -f deploys/migrations/mac-to-dedicated.yaml
+kctl-dokploy deploy migrate plan     -f deploys/migrations/mac-to-dedicated.yaml
+kctl-dokploy deploy migrate apply    -f deploys/migrations/mac-to-dedicated.yaml
+kctl-dokploy deploy migrate apply    -f deploys/migrations/mac-to-dedicated.yaml --resume
+kctl-dokploy deploy migrate rollback -f deploys/migrations/mac-to-dedicated.yaml
+kctl-dokploy deploy migrate cleanup  -f deploys/migrations/mac-to-dedicated.yaml
+```
+
+### Compose Postgres Backup → S3 → Local Restore
+
+`backups restore` streams Dokploy's native SSE restore endpoint. Dokploy's server
+does `pg_restore` via `docker exec` — no SSH or temp files from the client side.
+
+**One-time setup** (register the S3 bucket on the target Dokploy):
+
+```bash
+kctl-dokploy --profile local backups add-destination \
+    --name hz-tpp-postgres-backup --bucket hz-tpp-postgres-backup \
+    --access-key "$HZ_ACCESS" --secret-key "$HZ_SECRET" \
+    --region fsn1 --endpoint https://fsn1.your-objectstorage.com
+```
+
+> Set destination `provider: "Other"` (not `"s3"`) for Hetzner Object Storage.
+> rclone rejects `"s3"` as a provider value for this endpoint type.
+
+**One-shot restore** (latest S3 key for a database):
+
+```bash
+kctl-dokploy -p local backups restore \
+    --compose <local-compose-id> \
+    --destination <local-dest-id> \
+    --database-name tpp_odoo_erp \
+    --service-name postgres \
+    --database-user odoo \
+    --latest tpp_odoo_erp
+```
+
+Streams log lines prefixed `[Dokploy]` to stdout. Exit 0 on success,
+1 on Dokploy error, 2 on transport/auth failure.
+
+**Prerequisites:**
+- Target DB must already exist with `OWNER=odoo` — Dokploy's restore does not create it.
+  Use `SERVICE_DATABASES` in the `kodemeio-postgres` compose env to pre-create on start.
+- `odoo` role must be SUPERUSER on the target postgres instance.
+- `--service-name` and `--database-user` are required; omitting either causes an
+  immediate exit 1 (empty `pg_restore -U ''` or wrong container).
+
+See `runbooks/postgres-restore.md` for the full reference including historical-key
+restore, metadata flag table, and common compose IDs.
+
+## Command Groups
+
+### Top-level Groups
+
+| Group            | Description                                                         |
+|------------------|---------------------------------------------------------------------|
+| `config`         | CLI configuration (profiles, init, add, use, show, validate)        |
+| `projects`       | Dokploy project CRUD and environment management                     |
+| `applications`   | Application service management (non-compose apps)                   |
+| `compose`        | Docker Compose service management (Dokploy's primary service type)  |
+| `servers`        | Server management, monitoring, and cluster operations               |
+| `databases`      | Managed database service management (Dokploy-managed DBs)           |
+| `registry`       | Container registry configuration and access                         |
+| `users`          | User CRUD, roles, and invite management                             |
+| `git`            | Git provider integration (GitHub, GitLab, Bitbucket)                |
+| `notifications`  | Notification channel management (Slack, email, webhook)             |
+| `certificates`   | SSL/TLS certificate management                                      |
+| `settings`       | Dokploy platform settings (SMTP, S3, general)                       |
+| `docker`         | Docker image and container utilities                                 |
+| `dashboard`      | Platform overview and health summary                                 |
+| `diagnose`       | Diagnostics, maintenance, and platform health checks                |
+| `deploy`         | Declarative deployment pipeline (13-phase, manifest-driven)         |
+| `report`         | Platform usage and deployment reports                               |
+| `template`       | Deployment template management                                      |
+| `audit`          | Audit log queries and export                                        |
+| `setup`          | Platform initial setup and onboarding                               |
+
+### Compose Sub-Groups
+
+The `compose` group mirrors Dokploy's UI tabs for managing individual services:
+
+| Sub-group         | Description                                                    |
+|-------------------|----------------------------------------------------------------|
+| `compose backups`        | Backup CRUD + native restore workflow (`restore`, `add-destination`, `destinations`, `list-files`) |
+| `compose domains`        | Traefik domain routing and SSL configuration            |
+| `compose env`            | Environment variable management (push, pull, diff)      |
+| `compose deployments`    | Deployment history, logs, and redeploy triggers         |
+| `compose schedules`      | Cron job / scheduled task management                    |
+| `compose patches`        | Service patch application                               |
+| `compose volume-backups` | Volume backup configuration                             |
+| `compose mounts`         | Volume mount management                                 |
+| `compose ports`          | Port mapping management                                 |
+| `compose security`       | Service-level security settings                         |
+| `compose redirects`      | HTTP redirect rules                                     |
+| `compose bulk`           | Bulk operations across multiple compose services        |
+
+### Server Sub-Groups
+
+| Sub-group           | Description                                          |
+|---------------------|------------------------------------------------------|
+| `servers monitoring` | Server resource monitoring (CPU, memory, disk)      |
+| `servers cluster`    | Swarm/cluster node management                       |
+
+### Project Sub-Groups
+
+| Sub-group               | Description                                     |
+|-------------------------|-------------------------------------------------|
+| `projects environments` | Dokploy environment management per project      |
+
+### Deploy Sub-Commands
+
+| Sub-command              | Description                                                  |
+|--------------------------|--------------------------------------------------------------|
+| `deploy apply`           | All-in-one: run all 13 phases in sequence                   |
+| `deploy apply-all`       | Batch apply all manifests in a directory                     |
+| `deploy setup`           | Stage 1: DNS + DB + compose + env + domain (idempotent)     |
+| `deploy run`             | Stage 2: trigger redeploy + wait for healthy                 |
+| `deploy post`            | Stage 3: backup config + schedules + post-deploy hooks       |
+| `deploy preflight`       | Run pre-deploy gate checks on a single manifest              |
+| `deploy preflight-all`   | Run pre-deploy gate checks on all manifests in a directory   |
+| `deploy validate`        | Validate manifest YAML without deploying                     |
+| `deploy verify`          | Pre-deploy validation + post-deploy smoke tests              |
+| `deploy status`          | Dry-run all phases to preview current state                  |
+| `deploy list`            | List all discovered manifests and their domains              |
+| `deploy troubleshoot`    | Diagnose failed deployment (logs, health, error type)        |
+| `deploy migrate`         | Server-to-server migration pipeline                          |
+
+## Deploy Pipeline
+
+`kctl-dokploy deploy apply` runs a 13-phase pipeline orchestrating multiple kctl-* CLIs:
+
+| # | Phase       | CLI Used       | Description                                               |
+|---|-------------|----------------|-----------------------------------------------------------|
+| 0 | preflight   | kctl-dokploy   | 10 gates: server, firewall, DNS, image pull, DB, compose, env sync (OIDC), source, network, SSL |
+| 1 | dns         | kctl-cf        | Create/verify Cloudflare DNS record                       |
+| 2 | database    | kctl-pg        | Create PostgreSQL database + application role             |
+| 3 | registry    | kctl-dokploy   | Ensure container registry access configured               |
+| 4 | compose     | kctl-dokploy   | Create or update Dokploy compose service                  |
+| 5 | environment | kctl-dokploy   | Push env vars from manifest + env file                    |
+| 6 | domain      | kctl-dokploy   | Configure Traefik domain routing + SSL                    |
+| 7 | deploy      | kctl-dokploy   | Trigger redeploy                                          |
+| 8 | verify      | kctl-dokploy   | Wait for healthcheck to pass                              |
+| 9 | backup      | kctl-dokploy   | Configure backup destination + schedule                   |
+| 10 | schedules  | kctl-dokploy   | Set up cron jobs (vacuum, session cleanup, etc.)          |
+| 11 | volume-backups | kctl-dokploy | Configure volume backup destinations                    |
+| 12 | post-deploy | kctl-odoo      | Install Odoo bundles/profiles (for Odoo service types)    |
+
+### Preflight Gates
+
+The preflight phase runs 10 gates before any infrastructure changes:
+
+| Gate          | Checks                                                      |
+|---------------|-------------------------------------------------------------|
+| `server`      | Dokploy API reachable, server exists in inventory           |
+| `firewall`    | Required ports accessible                                   |
+| `dns`         | DNS record exists and resolves correctly                    |
+| `image_pull`  | Container image pullable from registry                      |
+| `database`    | PostgreSQL credentials valid, DB server reachable           |
+| `compose`     | Compose service in valid state (not mid-deploy)             |
+| `env_sync`    | OIDC and required env vars present in env file              |
+| `source`      | Git source branch/ref accessible                            |
+| `network`     | `dokploy-network` exists on target server                   |
+| `ssl`         | SSL certificate valid and not near expiry                   |
+
+### Manifest Format
+
+Manifests follow the `{tenant}-{stack}-{app}.yaml` naming convention:
+
+```yaml
+# deploys/instances/production/mac-react-sfa.yaml
+extends: bases/react-pwa.yaml
+
+instance:
+  name: mac-react-sfa
+
+type: react-pwa
+project: mac
+server: mac-prod-01
+
+domain:
+  host: sfa.mandiriagro.com
+
+healthcheck:
+  path: /
+  expected_status: 200
+
+env_file: deploys/env/production/mac-react-sfa.env
+```
+
+## Global Options
+
+```
+--json                Output as JSON (machine-readable)
+--quiet, -q           Suppress informational messages
+--format, -f          Output format: pretty, json, csv, yaml
+--no-header           Omit headers in CSV output
+--debug               Enable debug logging
+--profile, -p         Use a named config profile
+--url                 Dokploy API URL override
+--api-key             API key override
+--version, -V         Show version and exit
+```
+
+## Command Aliases
+
+Hidden short aliases are available for common operations:
+
+| Alias | Expands to                |
+|-------|---------------------------|
+| `cl`  | `compose list`            |
+| `cs`  | `compose start <id>`      |
+| `cr`  | `compose redeploy <id>`   |
+| `sl`  | `servers list`            |
+| `pl`  | `projects list`           |
+| `ds`  | `dashboard show`          |
+| `dg`  | `diagnose run`            |
+| `dl`  | `deployments list`        |
+| `bl`  | `backups list`            |
+
+Example:
+
+```bash
+kctl-dokploy cl                   # same as: kctl-dokploy compose list
+kctl-dokploy cr OEK_dJRQZZMo9HKbQ  # same as: kctl-dokploy compose redeploy <id>
+```
+
+## Configuration
+
+### Profiles
+
+kctl-dokploy supports named profiles for managing multiple Dokploy instances:
+
+```bash
+# Create a profile (interactive)
+kctl-dokploy config init
+
+# Add a profile manually
+kctl-dokploy config add production \
+  --url https://dokploy.kodeme.io \
+  --api-key $DOKPLOY_API_KEY
+
+# Add a staging profile
+kctl-dokploy config add staging \
+  --url https://dokploy-stg.kodeme.io \
+  --api-key $DOKPLOY_STAGING_KEY
+
+# Switch default profile
+kctl-dokploy config use production
+
+# Use per-command
+kctl-dokploy --profile staging compose list
+
+# List all profiles
+kctl-dokploy config profiles
+
+# Show current profile (secrets masked)
+kctl-dokploy config show
+```
+
+### Config File
+
+Configuration is stored in `~/.config/kodemeio/config.yaml` under the `dokploy` service key, shared with all other kctl-* CLIs.
+
+```yaml
+# ~/.config/kodemeio/config.yaml (example shape)
+profiles:
+  default: production
+  production:
+    dokploy:
+      url: https://dokploy.kodeme.io
+      api_key: ${DOKPLOY_API_KEY}   # env var expansion supported
+```
+
+## Shell Completions
+
+```bash
+# Generate and install for your shell
+kctl-dokploy --install-completion bash
+kctl-dokploy --install-completion zsh
+kctl-dokploy --install-completion fish
+
+# Or use the skill subcommand
+kctl-dokploy skill completions install
+```
+
+## Plugin Development
+
+kctl-dokploy supports extending the CLI via Python entry points. Create a package that registers a Typer app under the `kctl_dokploy.plugins` entry point group:
+
+```toml
+# In your plugin's pyproject.toml
+[project.entry-points."kctl_dokploy.plugins"]
+my_plugin = "my_plugin.cli:app"
+```
+
+The plugin's `app` (a `typer.Typer` instance) will be registered as a command group automatically on startup.
+
+## Development
+
+### Running Tests
+
+```bash
+cd packages/kctl-dokploy
+uv run pytest tests/ -v
+```
+
+### Linting and Formatting
+
+```bash
+cd packages/kctl-dokploy
+uv run ruff check src/
+uv run ruff format src/
+```
+
+### Type Checking
+
+```bash
+cd packages/kctl-dokploy
+uv run mypy src/kctl_dokploy/
+```
+
+### Project Structure
+
+```
+packages/kctl-dokploy/
+  src/kctl_dokploy/
+    cli.py                  Main app + command group registration
+    __init__.py             Version (0.3.5)
+    core/
+      callbacks.py          Global option handling (AppContext)
+      api_client.py         HTTP client wrapping kctl-lib APIClient
+      deployer.py           13-phase Deployer class
+      manifest.py           DeployManifest Pydantic model + YAML loader
+      preflight.py          Preflight gate runner
+      troubleshoot.py       Deployment diagnosis engine
+      deploy_validators.py  Pre/post deploy validators
+    commands/
+      aliases.py            Short command aliases
+      deploy.py             Declarative deployment pipeline
+      compose.py            Compose service management
+      servers.py            Server management
+      projects.py           Project management
+      diagnose.py           Diagnostic commands
+      ...                   (30+ command modules)
+  tests/                    pytest test suite
+  pyproject.toml            Package metadata and tool config
+  README.md                 This file
+```
+
+### Workspace Commands
+
+From the monorepo root:
+
+```bash
+# Install all workspace packages
+uv sync --all-extras --all-packages
+
+# Run kctl-dokploy tests only
+uv run pytest packages/kctl-dokploy/tests/ -v
+
+# Lint all packages
+uv run ruff check packages/*/src/
+```

kctl_dokploy-0.5.0/e2e/.gitignore

@@ -0,0 +1,3 @@
+node_modules/
+playwright-report/
+test-results/

kctl_dokploy-0.5.0/e2e/README.md

@@ -0,0 +1,30 @@
+# kctl-dokploy E2E Tests
+
+Playwright-based E2E tests for kctl-dokploy against live staging services.
+
+## Setup
+
+```bash
+pnpm install
+pnpm run install-browsers
+```
+
+## Run
+
+```bash
+# Against staging
+export DOKPLOY_URL=https://dokploy.kodeme.io
+export DOKPLOY_TOKEN=<your-token>
+pnpm test
+
+# Smoke tests only
+pnpm test:smoke
+
+# Visible browser
+pnpm test:headed
+```
+
+## Env Vars
+
+- `DOKPLOY_URL` — Base URL (default: https://dokploy.kodeme.io)
+- `DOKPLOY_TOKEN` — API token

kctl_dokploy-0.5.0/e2e/fixtures/auth.ts

@@ -0,0 +1,20 @@
+import { test as base } from "@playwright/test";
+
+export interface AuthFixtures {
+  apiToken: string;
+  baseUrl: string;
+}
+
+export const test = base.extend<AuthFixtures>({
+  apiToken: async ({}, use) => {
+    const token = process.env.DOKPLOY_TOKEN;
+    if (!token) throw new Error("DOKPLOY_TOKEN env var required");
+    await use(token);
+  },
+  baseUrl: async ({}, use) => {
+    const url = process.env.DOKPLOY_URL || "https://dokploy.kodeme.io";
+    await use(url);
+  },
+});
+
+export { expect } from "@playwright/test";

kctl_dokploy-0.5.0/e2e/package.json

@@ -0,0 +1,15 @@
+{
+  "name": "kctl-dokploy-e2e",
+  "version": "0.1.0",
+  "private": true,
+  "scripts": {
+    "test": "playwright test",
+    "test:smoke": "playwright test --project=smoke",
+    "test:headed": "playwright test --headed",
+    "install-browsers": "playwright install chromium"
+  },
+  "devDependencies": {
+    "@playwright/test": "^1.48.0",
+    "typescript": "^5.5.0"
+  }
+}

kctl_dokploy-0.5.0/e2e/playwright.config.ts

@@ -0,0 +1,15 @@
+import { defineConfig } from "@playwright/test";
+
+export default defineConfig({
+  testDir: "./tests",
+  timeout: 60_000,
+  retries: 1,
+  reporter: "list",
+  use: {
+    baseURL: process.env.DOKPLOY_URL || "https://dokploy.kodeme.io",
+  },
+  projects: [
+    { name: "smoke", testMatch: /smoke\/.*\.spec\.ts/ },
+    { name: "scenarios", testMatch: /scenarios\/.*\.spec\.ts/ },
+  ],
+});

kctl_dokploy-0.5.0/e2e/tests/smoke/connectivity.spec.ts

@@ -0,0 +1,12 @@
+import { test, expect } from "../../fixtures/auth";
+
+test.describe("Connectivity", () => {
+  test.skip(!process.env.DOKPLOY_TOKEN, "DOKPLOY_TOKEN not set");
+
+  test("API endpoint is reachable", async ({ request, apiToken, baseUrl }) => {
+    const response = await request.get(`${baseUrl}/api/health`, {
+      headers: { Authorization: `Bearer ${apiToken}` },
+    });
+    expect([200, 204]).toContain(response.status());
+  });
+});