Password Pusher is an opensource application to communicate passwords over the web. Links to passwords expire after a certain number of views and/or time has passed.
Hosted at pwpush.com but you can also easily run your own private instance with just a few steps.
Follow Password Pusher on Twitter for the latest news, updates and changes.
You can access Password Pusher at pwpush.com or alternatively use one of the tools below.
To run your own instance, see Run Your Own Instance in the next section.
-
pgarm/pwposh: a PowerShell module available in the PowerShell Gallery
-
kprocyszyn/.Get-PasswordLink.ps1: a PowerShell based CLI
-
lnfnunes/pwpush-cli: a Node.js based CLI
-
abkierstein/pwpush: a Python based CLI
-
Alfred Workflow for Mac users
Note: Password Pusher can be largely configured by environment variables so after you pick your deployment method below, make sure to read the configuration page.
Docker images of Password Pusher are available on Docker hub.
โ ephemeral
docker run -d -p "5100:5100" pglombardo/pwpush-ephemeral:latest
โ using an External Postgres Database
docker run -d -p "5100:5100" pglombardo/pwpush-postgres:latest
Included in this repository is docker/pwpush-postgres/docker-compose.yaml
which can be used by simply running:
docker-compose up -d
docker-compose down
We currently don't supply a prebuilt Kubernetes YAML file yet but you can deploy the above Docker images using this documentation.
See this blog post on how to deploy Password Pusher to Azure by Craig McLaren.
See our OpenShift documentation.
One click deploy to Heroku Cloud without having to set up servers.
This option will deploy a production Password Pusher instance backed by a postgres database to Heroku. As is monthly cost: $0.
Make sure you have git and Ruby installed and then:
git clone git@github.com:pglombardo/PasswordPusher.git
cd PasswordPusher
gem install bundler
bundle install --without development production test --deployment
bundle exec rake assets:precompile
RAILS_ENV=private bundle exec rake db:setup
foreman start internalweb
Then view the site @ http://localhost:5100/.
Note: You can change the listening port by modifying the Procfile
Thanks to:
-
@sfarosu for contributing the Docker, Kubernetes & OpenShift container support.
-
@iandunn for better password form security.
-
Kasper 'kapรถw' Grubbe for the JSON POST fix.
-
JarvisAndPi for the favicon design