---
description: Install, upgrade and back up the Node dashboard.
---

# Install with Docker Compose

The supplied stack runs the Node app, its built-in scheduler and a one-shot migrator. The package selects matching Linux agent releases. The Docker host needs Docker Compose, Node.js 22.12+ and npm for setup.

## Install

Run on the Docker host:

```sh
npx devpush@latest init my-devpush --target docker
cd my-devpush
```

The wizard installs a pinned npm dependency, generates `.env`, `Dockerfile` and `compose.yml`, configures sign-in and offers to start the dashboard. The first build can take several minutes. For setup over SSH, follow the [GitHub callback forwarding steps](/docs/configuration/#authentication). Keep `.env` on the Docker host; it contains installation secrets. Review `DEVPUSH_ADMIN_EMAIL` and [sign-in](/docs/configuration/#authentication).

Provide an HTTPS [reverse proxy](/docs/configuration/#reverse-proxies) pointing to host port 7429 (`DEVPUSH_HTTP_PORT`). Compose does not provide dashboard TLS. Compose binds the listener to `127.0.0.1:7429`. For a proxy on another host, deliberately change the bind address in `compose.yml` and firewall direct access. Do not enroll this host as an app server if its existing proxy occupies ports 80/443.

If you declined startup during setup, start the dashboard:

```sh
npm run deploy
```

Check that it is healthy:

```sh
curl --fail http://localhost:7429/api/health
```

Use the configured port if different. Diagnose startup with:

```sh
docker compose logs --tail=100 app migrate
```

Sign in, configure the [allowlist](/docs/accounts-and-teams/#installation-administration), arrange backups and [connect a server](/docs/getting-started/).

## Upgrade

Back up both databases and uploads, review migrations, install the reviewed package version with `npm install --save-exact devpush@VERSION` and run `npm run deploy`. Update framework peers when the package requires it. Keep `BETTER_AUTH_SECRET` and `DEVPUSH_SECRET_ENCRYPTION_KEY` unchanged.

All services run as UID/GID 1000. Existing volumes/bind mounts must grant that user access; do not make them world-writable. Run one app instance with SQLite on a local filesystem, never a network share.

The migrator applies the shipped main/log migration histories before startup. Never edit applied migrations or run schema push in production.

To roll back a schema-changing release, stop the app, restore pre-upgrade databases and rebuild using the previous package version and lockfile.

## Backups and recovery

`data` holds both SQLite stores under `/app/storage`. Set `COMPOSE_PROFILES=backups` in `.env` for daily online snapshots, retained seven days by default (`BACKUP_RETENTION_DAYS`). Snapshots live in `/backups`, mounted from `backups`. Copy them off-host and test restoration.

Never copy only a live `.sqlite` file: committed data may be in WAL files. Online snapshots are consistent individually; stop the app for a coordinated snapshot of both stores and uploads. Back up `uploads`, configuration and secrets separately.

To restore, first stop all database writers:

```sh
docker compose stop app db-backup
```

Replace both database files, remove stale WAL/SHM files while all connections are closed, restore uploads and start the image matching those backups.

Remote libSQL uses provider backups; the local backup profile refuses remote configurations. Changing storage settings does not transfer data.

## Background work

Production Node runs a minute-based scheduler inside the app. Workers uses native cron; both call the same functions. Notification retries and enabled backup schedules run each minute; maintenance runs hourly, with failed runs retried.

Email delivery logs identify notifications without message content. Retries stop after ten attempts or 24 hours from the first attempt; there is no delivery-management screen.

`/api/health` checks the main database only. Inspect [agent diagnostics](/docs/agent-maintenance/) and real app routes separately. Use [deletion recovery](/docs/deletion-recovery/) for blocked cleanup; never delete rows to bypass it.

## Uninstall

Back up the databases, uploads and secrets first. Stop and remove the dashboard containers using the same configuration:

```sh
docker compose down
```

This preserves named volumes. Only remove those volumes after verifying the backups and deciding to discard the installation’s data. Application containers on agent servers keep running; [remove agents](/docs/agent-maintenance/#remove-an-agent) separately when needed.