Just Dashboard Deployments
Deploy an application to your server, follow each release, and operate it from one project workspace.
Just Dashboard 0.8.4 deploys to the one Linux server that runs the dashboard. A project starts from a Git repository, a Docker image, a Compose stack already on the server, or a reviewed template, and the same page can start a database server. Each project has its own Overview, Deployments, Logs, Runtime, Console, and Settings pages.
Start with a project
Open Deployments → New project and choose a source. The dashboard inspects it, fills in what it can establish, and opens the first step that still needs an answer: Project, Runtime, Variables, or Review. Review checks the plan against this server and lists what the release keeps, the secrets it generates, its readiness checks, and whether replacement interrupts traffic, before you press Deploy. A run checks again against the source revision it actually builds.
Follow the guides for creating a project, choosing a template, and connecting persistent data.
What a project contains
| Page | What you use it for |
|---|---|
| Overview | See the live address, a site preview when the website permits embedding, live readings, recent deployments, and open pull requests for a GitHub project. A template explains its first sign-in here. |
| Deployments | Follow builds and releases, inspect each run, compare releases, retry a failed run, pin a release, or roll back. |
| Logs | Read the requests served by the managed proxy, traffic insights, container output, recent build transcripts, container events, and traffic alerts. |
| Runtime | Inspect the live containers and their resource use, and start, stop, restart, or pause one. See the project's domains, storage, linked databases, and backup state. |
| Console | Open a shell in the live release container. |
| Settings | Change the source, build, runtime, variables, domains, storage, databases and backups, automation, or project lifecycle. |
The project list puts failed and unhealthy projects first, then deployments in progress and projects with changes pending. Filter it by Deploying, Failed, Changes pending, or Pull requests. Each card shows its source, last commit, recent runs, and the last hour of traffic. An unavailable health reading is shown as unavailable; it is not treated as proof that the application is healthy.
Release behavior
Each release keeps an immutable record of what was built and deployed. An eligible, stateless HTTP service behind a managed route can start a candidate and pass a readiness check before traffic moves to it. Compose, fixed-port, game, and exclusive-storage workloads use a stop-first replacement and can have downtime. The Review screen and Settings → Runtime show the strategy for the current plan. Learn how releases and rollback work.
Useful starting points
- Create from Git, an image, a Compose stack, or a template
- Set build, runtime, variables, and release tasks
- Set up domains, HTTPS, and ports
- Configure automatic deploys, notifications, and previews
- Read deployment requests, insights, output, and events
- Diagnose a blocked or failed deployment
- Keep storage and databases through releases
These pages describe Just Dashboard 0.8.4. Deployment behavior can change between patches; check the version shown in your dashboard before following a procedure on another release.