DokkitInstall
Install
One server, then a small program on each machine you want watched. Four steps, in order. The step you are on is always marked.
Step 1 of 4
The server
It will run on .
Its address is , already pointing at that machine.
What the installer does 3 things
- Installs Docker and its compose plugin if they are missing, and writes its settings to
/opt/dokkit/.env. - Starts three containers: Postgres 17, the Dokkit server, and Caddy, which gets and renews the certificate for by itself.
- Waits until the server answers over https, then prints the address and a setup code for the first visit.
Its database is , at .
Run it from an administrator PowerShell.
What the installer does 3 things
- Fetches the release and refuses it unless its checksums carry a valid signature from the release key.
- The first time, sets up Postgres 17 as a Windows service of its own that listens on this machine only.
- Installs Dokkit as a Windows service and starts it. Without a certificate it serves plain http to this machine only; give it one with
-Certand-CertKey, or get one later in Settings.
What the server needs 1 core, 1 GB, 20 GB at least
Estimates for about ten machines and sixty services. They have not been measured yet.
Step 2 of 4
The first visit
- Open in a browser.
- Type the setup code the server printed when it started. It is there so nobody else on the network can claim the server first.
- Make the owner account. That is you.
Dokkit cannot page you about itself when it is down. In Settings, give it an outside heartbeat: an https address it calls every minute, at any service that alerts when the calls stop.
Step 3 of 4
Each machine
The machine runs .
- In Dokkit, open Add a machine and give it a name. It gives you one line, made for that machine.
- Paste it into an administrator PowerShell on the machine:
It fetches the program from your server, checks its signature, joins the machine, installs the service and the updater, and checks it reports.
- Get the program:
curl -fsSL https://dokkit.dev/get.sh | sh - Join it to your server, with a token from Add a machine:
- Keep it running with nobody signed in:
sudo dokkit service install
The program opens no port. It reaches your server over a connection it makes itself.
Step 4 of 4
Each app
- In the app's own folder, describe it. This asks what the app is and writes
dokkit.toml:dokkit init - Prove it on your own machine. It runs every check once and prints what would be sent, with no server needed:
dokkit check - On the machine where it runs, tell the program where it lives:
dokkit folder add .