v0.6.2 · TLS-only · single host

One control plane for your
self-managed Linux host.

Connect trusted Git repositories, deploy Node/Bun or Docker Compose projects, bind domains, issue TLS, and manage owned Nginx files from one dashboard.

# Local evaluation
git clone https://github.com/raptercode/dashboard-portal-control
cd dashboard-portal-control && cp .env.example .env
docker compose up --build -d

Controlled deploys, domains, and operations—without a generic remote shell.

Portal is intentionally scoped to one owner and one self-managed Ubuntu host.

📦

Candidate-first deploys

Build and health-check a candidate before changing the active release; use rollback when needed.

🔒

Managed domains and TLS

Validate DNS, test owned Nginx files, and use Certbot for HTTPS after host preflight.

📊

Logs and host signals

Review release events, scoped runtime logs, tool readiness, and CPU/memory/disk history.

🔔

Bounded integrations

Use database TCP connectors, project-scoped monitoring tokens, and deployment notifications.

⚙️

Three runtimes

Choose Native Node.js, Native Bun, or trusted Docker Compose with explicit guardrails.

🛡️

Encrypted at rest

Protect Git tokens, environment values, webhook endpoints, and database passwords with one persistent key.

1
self-managed host
3
supported project runtimes
TLS
public entry point: HTTPS
No
generic shell endpoint

Set up a project in three deliberate steps.

1

Prepare Git

Save the Git author identity and, only when needed, an encrypted HTTPS token for a private repository.

Setup → Git identity
2

Sync and deploy

Choose the branch, application directory, runtime, scripts, health check, and environment; then create a candidate.

Projects → New Project → Deploy
3

Attach domain + TLS

Point DNS to the host, validate readiness, and let Portal manage only its own Nginx and certificate files.

Domains → DNS check → TLS

Ready to understand the safe path first?

Ubuntu 24.04 / 25.04 · one owner · one host