Self-host PicoShare with Levelrail
Minimalist file sharing service for sending large files by link with an optional expiry. A generated shared secret protects the upload page.
- Authormtlynch
- LicenceAGPL-3.0-only
- Memory64 MiB
- Services1
How to self-host PicoShare
-
Pull the images
One image is pulled on your server.
Show images
mtlynch/picoshare:v1.5.4
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 4001.
-
Fill in the secrets
1 secret is generated and stored encrypted, 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.
After the first start
- Sign in with the generated shared secret shown in the deployment variables, then upload a file to get a link.
PicoShare requirements
- Memory
- About 64 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 4001
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-only, network copyleft (agpl) 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 PicoShare. 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 PicoShare docs page.
Deploy PicoShare your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy PicoShare from the CLI
levelrail-cli templates install picoshare --name my-picoshare Deploy PicoShare with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/picoshare/install \
-d '{
"name": "my-picoshare"
}' PicoShare configuration
PicoShare services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| picoshare | mtlynch/picoshare:v1.5.4 | 4001 | data -> /data |
PicoShare environment variables
| Variable | Service | Value |
|---|---|---|
| PORT | picoshare | Preset by the template |
| PS_SHARED_SECRET | picoshare | Generated at deploy |
Ports and volumes
- Ports
- 4001
- Volumes
- 1 named mount: data -> /data
PicoShare FAQ
How much memory does PicoShare need?
The catalog lists about 64 MiB of memory for PicoShare.
Does PicoShare run on arm64?
For PicoShare, arm64 support is not confirmed; amd64 is unknown.
What licence is PicoShare under?
PicoShare is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does PicoShare need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does PicoShare use?
PicoShare listens on port 4001 inside the stack.
Where does PicoShare keep its data?
In a named volume: data mounted at /data.
Can I deploy PicoShare on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for PicoShare, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image mtlynch/picoshare:v1.5.4 is what you deploy there.