|Number of watchers on Github||615|
|Number of open issues||1|
|Average time to close an issue||2 months|
|Average time to merge a PR||6 days|
|Open pull requests||6+|
|Closed pull requests||20+|
|Last commit||over 2 years ago|
|Repo Created||about 7 years ago|
|Repo Last Updated||over 2 years ago|
|Organization / Author||thoughtbot|
|Do you use parity? Leave a review!|
|View parity activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
Shell commands for development, staging, and production parity for Heroku apps.
On OS X, this installs everything you need:
brew tap thoughtbot/formulae brew install parity
wget -qO - https://apt.thoughtbot.com/thoughtbot.gpg.key | sudo apt-key add - echo "deb http://apt.thoughtbot.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/thoughtbot.list sudo apt-get update sudo apt-get install parity
On other systems you can:
/binis in your
Parity requires these command-line programs:
git heroku pg_restore
On OS X, these programs are installed
as Homebrew package dependencies of
parity Homebrew package.
Backup a database:
production backup staging backup
Restore a production or staging database backup into development:
development restore production development restore staging
restore-from reads better to you, it's the same thing:
development restore-from production development restore-from staging
Push your local development database backup up to staging:
staging restore development
Deploy from master to production and migrate and restart the dynos if necessary:
Deploy the current branch to staging or a feature branch and migrate and restart the dynos if necessary:
Note that deploys to non-production environments use
git push --force.
Open a console:
production console staging console
Migrate a database and restart the dynos:
production migrate staging migrate
Tail a log:
production tail staging tail
Use redis-cli with your
production redis-cli staging redis-cli
The scripts also pass through, so you can do anything with them that you can do
heroku ______ --remote staging or
heroku ______ --remote production:
watch production ps staging open
stagingremote pointing to the staging Heroku app.
productionremote pointing to the production Heroku app.
heroku git:remote -r staging -a your-staging-app heroku git:remote -r production -a your-production-app
config/database.ymlfile that can be parsed as YAML for
If you have Heroku environments beyond staging and production (such as a feature
environment for each developer), you can add a binstub to the
bin folder of
your application. Custom environments share behavior with staging: they can be
backed up and can restore from production.
Using feature environments requires including Parity as a gem in your application's Gemfile.
Here's an example binstub for a 'feature-geoff' environment, hosted at myapp-feature-geoff.herokuapp.com.
#!/usr/bin/env ruby require "parity" if ARGV.empty? puts Parity::Usage.new else Parity::Environment.new("feature-geoff", ARGV).run end
Please fill out our issues template if you are having problems.
CONTRIBUTING.md for details.
Please see the releases page for the version history, along with a description of the changes in each release.
See guidelines in
RELEASING.md for details
Parity is 2013-2018 thoughtbot, inc. It is free software, and may be redistributed under the terms specified in the LICENSE file.
Parity is maintained and funded by thoughtbot, inc. The names and logos for thoughtbot are trademarks of thoughtbot, inc.
Ignore missing local development database when restoring from remotes.