VAULTHandbook
deen

Installation

Two commands, a few minutes of building — then your store is up.

VAULT is built on your server, not pulled from someone else’s registry — nothing stands between you and your store. That is why the first start takes a few minutes; every start after that takes seconds.

The two commands

  1. 1

    Upload and unpack VAULT

    Get the ZIP you downloaded onto the server (e.g. scp or SFTP) and unpack it:

    Terminal
    unzip vault.zip -d /opt/vault && cd /opt/vault
  2. 2

    Run the installer

    Terminal
    bash install.sh

What install.sh does for you

  • Checks the machine: Docker present, enough memory, enough disk, ports free. With too little RAM (under ~1.9 GB incl. swap) it offers to create a 2 GB swap file — with your consent, made permanent.
  • Generates your secrets: APP_SECRET (encrypts licence keys and credentials in the database), a database password and the one-time install token. Everything lands in .env.
  • Builds and starts the store together with its own PostgreSQL database and Caddy (HTTPS). Migrations run automatically on boot.
  • Speaks clearly: a failed build, a failed start and a start that never reports healthy are three different messages with three different next steps.
What success looks like
  ✓ VAULT is running

    Open:          https://your-domain.com/install
    Install token: 8f3a91c4e7b2d5a6…

Now open the printed address in your browser — continue in Setup wizard.