Self-host One-Time Secret with Levelrail

Share a password or API key through a link that self-destructs after the first view, backed by Redis.

  • Authoronetimesecret
  • LicenceMIT
  • Memory256 MiB
  • Archarm64
  • Services2

How to self-host One-Time Secret

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • onetimesecret/onetimesecret:v0.26.14
    • redis:7-alpine
  2. Create the app

    2 services start in a single Compose app, with 1 named volume mount for your data, on port 3000.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 7 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

One-Time Secret requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 image published
Ports
3000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then One-Time Secret. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the One-Time Secret docs page.

Deploy One-Time Secret your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy One-Time Secret from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain app=app.example.com.

levelrail-cli templates install onetimesecret --name my-onetimesecret

Deploy One-Time Secret with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/onetimesecret/install \
  -d '{
    "name": "my-onetimesecret"
  }'

One-Time Secret configuration

One-Time Secret services

ServiceImagePortsVolumes
app onetimesecret/onetimesecret:v0.26.14 3000 none
redis redis:7-alpine none redis -> /data

One-Time Secret environment variables

VariableServiceValue
AUTH_AUTOVERIFY app Preset by the template
AUTH_SIGNUP app Preset by the template
COLONEL app Preset by the template
HOST app Preset by the template
RACK_ENV app Preset by the template
REDIS_URL app Preset by the template
SECRET app Generated at deploy
SSL app Preset by the template

Ports and volumes

Ports
3000
Volumes
1 named mount: redis -> /data

One-Time Secret FAQ

How much memory does One-Time Secret need?

The catalog lists about 256 MiB of memory for One-Time Secret across its 2 services.

Does One-Time Secret run on arm64?

For One-Time Secret, an arm64 image is published; amd64 is image published.

What licence is One-Time Secret under?

One-Time Secret is licensed under MIT, which is permissive, with few conditions on reuse.

Does One-Time Secret need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does One-Time Secret bundle?

The template includes Redis, running as its own service.

Which ports does One-Time Secret use?

One-Time Secret listens on port 3000 inside the stack.

Where does One-Time Secret keep its data?

In a named volume: redis mounted at /data.

Can I deploy One-Time Secret on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id onetimesecret for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image onetimesecret/onetimesecret:v0.26.14, redis:7-alpine is what you deploy there.

levelrail-cli templates install onetimesecret --name my-onetimesecret