Portainer Templates logo

Portainer Templates

Password Pusher Password Pusher

Stack

SecurityFile Sharing

Share passwords, text, files and links as a link that expires after a set number of views or days, so they don't sit in someone's chat history or inbox forever. Source: https://github.com/pglombardo/PasswordPusher

Image details

Pulls: 2.3M
Architecture: amd64
Image size: 198 MB
Latest: 2.16
User: pglombardo
Created: Sep 12, 2023
Updated: 10 hours ago
Status: active

Source details

Repo: pglombardo/PasswordPusher
Stars: 3k
Forks: 474
Language: Ruby
License: Apache-2.0
Latest: v2.16.2 · 10 hours ago
Updated: 1 hour ago
Website: docs.pwpush.com/

Configuration

Type
Compose
Platform
linux
Image
pglombardo/pwpush:2
Ports
${PWPUSH_PORT:-5150}:5100
Volumes
/opt/PasswordPusher/storage : pwpush-storage
Env vars
PWPUSH_MASTER_KEY=${PWPUSH_MASTER_KEY:?Set a master key}SECRET_KEY_BASE=${PWPUSH_SECRET_KEY_BASE:-}PWP__ALLOW_ANONYMOUS=${PWPUSH_ANONYMOUS:-true}PWP__DISABLE_SIGNUPS=${PWPUSH_DISABLE_SIGNUPS:-false}PWP__FILES__STORAGE=localPWPUSH_SECRET_KEY_BASE=''PWPUSH_PORT=5150
Restart
unless-stopped
Source
Repo

Template by NotAFlightRisk·Source

Report issue

Notes

Set the master key before you deploy (openssl rand -hex 32 makes one), since the stack won't start without it. Then open http://<your-host>:5150 (or whichever port you picked), which goes straight to a first-run page for the admin account. It wants a boot code from the container's logs: search them for Boot Code. After that, anyone who can reach it can push without an account, and sign up for one too. To stop either, add PWPUSH_ANONYMOUS = false or PWPUSH_DISABLE_SIGNUPS = true to the stack's environment variables and redeploy. Pushes, files and accounts live in the pwpush-storage volume. Text is encrypted with the master key there, but uploaded files are kept as they are. Docs: docs.pwpush.com

Standalone Install

Select an install method, to see config/commands for deploying Password Pusher

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Password Pusher, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  password-pusher:
    image: pglombardo/pwpush:2
    restart: unless-stopped
    ports:
      - "${PWPUSH_PORT:-5150}:5100"
    environment:
      PWPUSH_MASTER_KEY: ${PWPUSH_MASTER_KEY:?Set a master key}
      SECRET_KEY_BASE: ${PWPUSH_SECRET_KEY_BASE:-}
      PWP__ALLOW_ANONYMOUS: ${PWPUSH_ANONYMOUS:-true}
      PWP__DISABLE_SIGNUPS: ${PWPUSH_DISABLE_SIGNUPS:-false}
      PWP__FILES__STORAGE: local
    volumes:
      - pwpush-storage:/opt/PasswordPusher/storage

volumes:
  pwpush-storage:

Or deploy it directly from the source:

git clone https://github.com/NotAFlightRisk/portainer-templates-extras
cd portainer-templates-extras
docker compose -f apps/password-pusher/compose.yml up -d

More install options in our documentation, or see pglombardo/PasswordPusher for app-specific guidance.


Password Pusher Front Page

Create unique, one-time URLs for sharing (and receiving) sensitive information.

Auto self-deletion upon expiration, lifecycle audit logs and a JSON API to automate it all

⚡️ Quick Start

→ Go to pwpush.com and try it out.
or
→ Setup a DNS record to point to your server (e.g. pwpush.example.com) and run:
docker run -d -p "80:80" -p "443:443" --env TLS_DOMAIN=pwpush.example.com pglombardo/pwpush

and browse to https://pwpush.example.com.
or alternatively
→ Use one of our production ready Docker Compose files with persistent databases.

Documentation

See the full Password Pusher documentation here.

🛡 License

License
This project is licensed under the terms of the Apache License 2.0 license. See LICENSE for more details.

📃 Citation

@misc{PasswordPusher,
  author = {Peter Giacomo Lombardo},
  title = {An application to securely communicate passwords over the web. Passwords automatically expire after a certain number of views and/or time has passed.},
  year = {2025},
  publisher = {GitHub},
  journal = {GitHub repository},
  howpublished = {\url{https://github.com/pglombardo/PasswordPusher}}
}

See Also

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Image won't pull

Test the pull directly on the host: docker pull pglombardo/pwpush:2

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Required settings are blank

PWPUSH_SECRET_KEY_BASE has no default value, and password-pusher may crash or misbehave if left empty.

  • Fill it in on the deploy screen before hitting deploy.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Password Pusher is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything Password Pusher needs bundled into one download. This template pulls pglombardo/pwpush:2, which Docker fetches once (about 198 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Password Pusher's comes from Docker Hub, published by pglombardo.

Version tags

The bit after the colon in the image name is the version tag. This one pins 2, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, so it runs on regular x86 PCs and servers, though not ARM boards like a Raspberry Pi.

Volumes

A volume is where Password Pusher keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /opt/PasswordPusher/storage kept in the pwpush-storage volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Password Pusher takes 7 of them, and 2 need a value before it'll start properly:

  • PWPUSH_MASTER_KEY, needs a value. Encrypts the text of every push. Exactly 64 hex characters, so generate it with: openssl rand -hex 32. Keep it the same when you redeploy, or older pushes can't be opened.
  • SECRET_KEY_BASE, pulled from your own environment
  • PWP__ALLOW_ANONYMOUS, defaults to true
  • PWP__DISABLE_SIGNUPS, defaults to false
  • PWP__FILES__STORAGE, defaults to local
  • PWPUSH_SECRET_KEY_BASE, needs a value. Keeps people logged in through a restart. Generate one with: openssl rand -hex 64. Leave it blank and every restart logs everyone out.
  • PWPUSH_PORT, defaults to 5150. Host port for the web UI

Restart policy

The restart policy here is unless-stopped, so Docker restarts Password Pusher after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Password Pusher sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container password-pusher. That's what you'll spot in the containers list and use in commands like docker logs password-pusher.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

Password Pusher is open source, released under the Apache-2.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Password Pusher up. Add the template list to Portainer once, then deploying Password Pusher is a click rather than a wall of config.