Install
Get it running on your own server.
docu.nexus runs as one Docker stack: Postgres, Redis, and the app. The installer writes the configuration, generates your secrets, downloads and verifies the image, and starts everything.
It asks where people will reach the instance, then does the rest. When it finishes, open the URL it prints and create the first administrator account. There is no default login.
curl -fsSL https://docu.nexus/install.sh | sh
- Downloading docunexus-v0.5.0-amd64.tar.gz
- Verifying checksum
- Loading into Docker
-
docunexus-postgresHealthy -
docunexus-redisHealthy -
docunexus-appStarted
docu.nexus is running.
Before you start
What you need
Host
Linux with Docker
Any Linux host running Docker with the Compose plugin.
Tool
curl
Used to fetch the installer and the image. Almost certainly already there.
Size
2 GB disk, 4 GB RAM
Comfortable for a small team. The stack is Postgres, Redis and the app.
No git, no repository, no source tree, and no build. No Docker registry account either: the image is a signed-for-integrity file over HTTPS, checked against its published SHA256 before it is loaded.
What the installer handles
Offline installs, and upgrades that keep your data
Air-gapped installs
The image and its checksum are plain files over HTTPS. Fetch them on a connected machine, carry them across, and load by hand. No registry account, at either end.
Upgrades are the same command
Run it again from the same directory. It keeps your configuration and your data, pulls the newer image, and restarts.
Two things left to you
Before you put it in front of people
The installer gets you running. It deliberately leaves TLS at a reverse proxy, and a backup schedule, to you. Both are in the manual, along with every configuration value the app reads.