Normalize AppStore package formatting and localized metadata. Adds repository text-format defaults, normalizes package YAML and environment sample whitespace, and updates localized display strings.
Password Pusher
Introduction
Password Pusher is an open source web application for sharing passwords. The 2.17.3 and release App Store packages use PostgreSQL and persist local uploads in a Docker volume.
Features
- Create password pushes with expiration and view limits.
- Share password content through secure links.
- Persist local file uploads across container updates.
Important: Existing MySQL/MariaDB installations
Password Pusher has deprecated MySQL/MariaDB support. Its ActiveStorage migration can fail on MySQL/MariaDB when foreign-key column types do not match.
Do not upgrade an existing MySQL/MariaDB installation directly or only change its selected database service. Stop the application and back up the complete database, /opt/PasswordPusher/storage from the app container, and any custom PWPUSH_MASTER_KEY. Follow the official MySQL/MariaDB-to-PostgreSQL migration guide to migrate the data one way with pgloader. In the 1Panel upgrade form, select the migrated PostgreSQL service and enter the target database name, user, and password.
If the old instance has file pushes, the updated package creates a persistent volume named passwordpusher-storage but does not automatically copy files from the old container. Back up the old container's /opt/PasswordPusher/storage and restore its contents into the new volume before starting the new version. Ensure existing files are readable and writable by container UID/GID 1000:1000; startup only sets the owner of an empty new volume and never recursively changes ownership of existing files. If you set a custom PWPUSH_MASTER_KEY, enter the same key in the upgrade form; changing it makes old pushes unreadable. Verify old pushes can be decrypted, attachments can be read, and new pushes can be created. Keep the old database backup, container, and storage directory until verification is complete.
Changing the database does not copy data. Without migration, the new PostgreSQL database will appear empty. Leave the encryption key blank if the old instance used the built-in default key.
Usage
In 1Panel, select an available PostgreSQL service and provide the database name, user, and password. After installation, open the Web UI using the configured application port.
Configuration
| Variable | Purpose | Default |
|---|---|---|
PANEL_DB_TYPE |
Database service | postgresql |
PANEL_DB_HOST |
PostgreSQL service selected in 1Panel | Selected by 1Panel |
PANEL_DB_PORT |
PostgreSQL port | 5432 |
PANEL_DB_NAME |
Database name | passwordpusher |
PANEL_DB_USER |
Database user | passwordpusher |
PANEL_DB_USER_PASSWORD |
Database user password | Generated by 1Panel |
PWPUSH_MASTER_KEY |
Custom push encryption key | Blank (application default) |
PANEL_APP_PORT_HTTP |
Web UI port | 40180 |
Application data and local file uploads persist in the passwordpusher-storage Docker volume mounted at /opt/PasswordPusher/storage.
References
- Website: https://pwpush.com
- Documentation: https://docs.pwpush.com
- MySQL/MariaDB migration guide: https://docs.pwpush.com/docs/mysql-to-postgresql-migration/
- Source: https://github.com/pglombardo/PasswordPusher