Self-host Chibisafe with Levelrail
A file vault for uploading and sharing files from the cloud.
- Authorchibisafe
- LicenceMIT
- Memory512 MiB
- Archarm64
- Services2
How to self-host Chibisafe
-
Pull the images
2 images are pulled on your server.
Show images
chibisafe/chibisafe:v6.5.5chibisafe/chibisafe-server:v6.5.5
-
Create the app
2 services start in a single Compose app, with 3 named volume mounts for your data, on port 8001.
-
Fill in the secrets
1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Chibisafe requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8001
- 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.
- Host ports. It publishes port 8001 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Chibisafe. 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 Chibisafe docs page.
Deploy Chibisafe your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Chibisafe from the CLI
levelrail-cli templates deploy chibisafe --name my-chibisafe Deploy Chibisafe with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/chibisafe/deploy Chibisafe configuration
Chibisafe services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| chibisafe | chibisafe/chibisafe:v6.5.5 | 8001 | none |
| chibisafe-server | chibisafe/chibisafe-server:v6.5.5 | none | chibisafe_database -> /app/databasechibisafe_uploads -> /app/uploadschibisafe_logs -> /app/logs |
Chibisafe environment variables
| Variable | Service | Value |
|---|---|---|
| BASE_API_URL | chibisafe | Preset by the template |
Ports and volumes
- Ports
- 8001
- Volumes
- 3 named mounts: chibisafe_database -> /app/database, chibisafe_uploads -> /app/uploads, chibisafe_logs -> /app/logs
Chibisafe FAQ
How much memory does Chibisafe need?
The catalog lists about 512 MiB of memory for Chibisafe across its 2 services.
Does Chibisafe run on arm64?
For Chibisafe, an arm64 image is published; amd64 is image published.
What licence is Chibisafe under?
Chibisafe is licensed under MIT, which is permissive, with few conditions on reuse.
Does Chibisafe need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Chibisafe use?
Chibisafe listens on port 8001 inside the stack.
Where does Chibisafe keep its data?
In named volumes: chibisafe_database mounted at /app/database, chibisafe_uploads mounted at /app/uploads and chibisafe_logs mounted at /app/logs.
Can I deploy Chibisafe 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 chibisafe for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image chibisafe/chibisafe:v6.5.5, chibisafe/chibisafe-server:v6.5.5 is what you deploy there.