Self-host Pingvin Share on a VPS

A self-hosted, ad-free alternative to WeTransfer for sending files with expiring links.

levelrail-cli templates deploy pingvin-share --name my-pingvin-share

Specification

Status
Listed
Category
Storage
Services
pingvin-share
Ports
3000
Volumes
1
Memory
about 256 MiB
arm64
image published
amd64
image published
Settings to fill in
none

This template is deprecated. Upstream repository is archived.

About Pingvin Share

A self-hosted, ad-free alternative to WeTransfer for sending files with expiring links. Runs as a single container from the pingvin-share image, listening on port 3000 and keeps its data in named volumes.

What it deploys

Pingvin Share runs as one service in a single Compose app, listening on port 3000, with 1 named volume mount.

ServiceImageTagPortsVolumes
pingvin-share stonith404/pingvin-share v1.13.0 3000 pingvin_data -> /opt/app/backend/data

Before you install

  • CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
  • Listed. It is in the catalog. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 3000 directly on the host, so open them in the VPS firewall only if you want that.

Settings and environment

You do not have to fill in anything. 1 secret is generated at deploy and stored encrypted. Values are never shown here.

ServiceVariableValue
pingvin-shareCORS_ALLOW_ORIGINPreset by the template
pingvin-shareJWT_SECRETGenerated at deploy

Install Pingvin Share on a VPS

  1. Install Levelrail on a fresh VPS

    Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.

    curl -fsSL https://levelrail.com/install.sh | sudo sh
  2. Sign in

    Open the setup link, choose a password, then log the CLI in. The CLI install command is curl -fsSL https://levelrail.com/install-cli.sh | sh if the machine does not have it. See Getting started.

    levelrail-cli login --device
  3. Read the template

    Shows the entry, including its full compose.yaml.

    levelrail-cli templates get pingvin-share
  4. Deploy it

    This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.

    levelrail-cli templates deploy pingvin-share --name my-pingvin-share

Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Pingvin Share.

More in Storage

All Storage templates