Deploy Password Pusher 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 create the admin account with the boot code from the pwpush service’s log, on the Logs tab. Only signed-in accounts make links; whoever gets one opens it without an account. To let anyone make links or sign up, add ALLOW_ANONYMOUS=true or DISABLE_SIGNUPS=false to the project’s .env and deploy again.

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:
  pwpush:
    image: pglombardo/pwpush:2
    restart: unless-stopped
    environment:
      # Pushes are encrypted with the master key; sessions are signed with the other.
      PWPUSH_MASTER_KEY: ${MASTER_KEY}
      SECRET_KEY_BASE: ${SECRET_KEY_BASE}
      PWP__HOST_DOMAIN: ${HOST}
      PWP__HOST_PROTOCOL: https
      PWP__FILES__STORAGE: local
      # The admin is made on the first-run page, with the boot code from the log; nobody else
      # signs up or pushes until the notes' lines are added. A link opens without an account.
      PWP__DISABLE_SIGNUPS: ${DISABLE_SIGNUPS:-true}
      PWP__ALLOW_ANONYMOUS: ${ALLOW_ANONYMOUS:-false}
    volumes:
      # The SQLite database and the files pushed.
      - storage:/opt/PasswordPusher/storage

volumes:
  storage:

compose.yamlSee it on GitHub