Deploy Vikunja on Pethost in one click

What happens

1. You sign in to Pethost or make an account, with a passkey, GitHub or Google.
2. No machine yet? You pick a plan, and we prepare one for you. The link waits in your browser until it is ready.
3. New project opens at the app, and you click Create project.
4. In a minute or two the app is live at its own address with HTTPS. Its secrets are made for it at random, and its data is in the nightly backup.
5. It is a project like any other: its compose.yaml, its .env, its logs and a terminal are in the panel, and your agent can change it, roll it back or restore it.

First steps

Open the address and register your account. Then add ENABLE_REGISTRATION=false to the project’s .env and deploy again, so that nobody else can sign up.

What it runs

The template is this compose.yaml and the variables it writes into the project’s .env. Pethost runs the file as it is written.

services:
  vikunja:
    image: vikunja/vikunja:2
    restart: unless-stopped
    # The image has nothing but Vikunja, so a volume comes up owned by root and Vikunja's
    # own user could not write to it.
    user: "0:0"
    environment:
      VIKUNJA_SERVICE_PUBLICURL: ${URL}/
      VIKUNJA_SERVICE_JWTSECRET: ${JWT_SECRET}
      VIKUNJA_DATABASE_TYPE: sqlite
      VIKUNJA_DATABASE_PATH: /db/vikunja.db
      # Open until the first account is made; the notes say how to close it.
      VIKUNJA_SERVICE_ENABLEREGISTRATION: ${ENABLE_REGISTRATION:-true}
    volumes:
      - files:/app/vikunja/files
      - db:/db

volumes:
  files:
  db:

compose.yamlSee it on GitHub