Comments (19)
@geoffharcourt Thanks Geoff! Let me know when you do and how can I help with providing info you need to look into this.
from parity.
Hi @cantonyselim this feature is not available until v0.9.3 of Parity. I haven't been able to push it out yet because there's an issue with Homebrew packaging due to new gem dependencies.
from parity.
No worries, is there a work around right now so that I can use parity to restore a database to my staging from production?
from parity.
@cantonyselim you should be able to use the existing restore
command (restore-from
will just be an alias for restore
).
from parity.
@cantonyselim can you install 0.9.3 and give it a try?
from parity.
@geoffharcourt I just tried after installing 0.9.3 and it still gives the same error.
from parity.
I'm able to run development restore-from staging
on my machine at the moment with 0.9.3. Do you have other versions of parity installed, or is your app using a different Ruby version? What do you get when you type which development
?
from parity.
The app is using ruby 2.2.1:
$ which development
/Users/viktorfonic/.rvm/gems/ruby-2.2.1/bin/development
$ brew list parity
/usr/local/Cellar/parity/0.9.3/bin/development
/usr/local/Cellar/parity/0.9.3/bin/production
/usr/local/Cellar/parity/0.9.3/bin/staging
/usr/local/Cellar/parity/0.9.3/lib/app/ (9 files)
/usr/local/Cellar/parity/0.9.3/lib/ruby/ (1009 files)
/usr/local/Cellar/parity/0.9.3/lib/vendor/ (200 files)
I always do brew upgrade --all && brew cleanup
$ heroku --version
heroku-toolbelt/3.42.50 (x86_64-darwin10.8.0) ruby/1.9.3
heroku-cli/4.29.4-8a30ba5 (amd64-darwin) go1.6.1
=== Installed Plugins
[email protected]
[email protected]
heroku-config
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
From the other app dir that's using ruby 2.3.0:
$ which development
/usr/local/bin/development
$ staging restore-from production
/Users/viktorfonic/.heroku/client/lib/heroku/jsplugin.rb:109: warning: Insecure world writable dir /usr/local/Cellar/parity in PATH, mode 040777
/Users/viktorfonic/.heroku/client/lib/heroku/jsplugin.rb:109: warning: Insecure world writable dir /usr/local/Cellar/parity in PATH, mode 040777
! Internal server error.
! Runheroku status
to check for known platform issues.
from parity.
@vfonic for the app at the top, it looks like the Parity gem's executable (in .rvm/gems/
) is in front of the Homebrew-installed executable in your path. In that app's folder, run gem uninstall parity
and be sure the executable is uninstalled. When you type which development
or which staging
, you should see the Homebrew location, not the RVM one.
I can't tell if the second app's error has anything to do with interaction with the plugins you have installed.
from parity.
We set the parity
folder in Cellar
to be writable in the Homebrew formula so that if Bundler runs it doesn't trigger a permissions error, but I don't have that same error message about permissions on my machine (using the same versions of heroku-toolbelt
and heroku-cli
).
from parity.
I've uninstalled the old gem together with executables. The error is now the same in every project:
$ which development
/usr/local/bin/development
$ staging restore-from production
! Internal server error.
! Runheroku status
to check for known platform issues.
from parity.
I'm not sure if this is a parity problem. The report that began this issue was with the restore-from
subcommand not being recognized by parity, but what you're getting now looks like the returned response from Heroku when the CLI gets a 500 error from the server.
Can you tail staging with staging tail
? Can you take a backup with staging backup
?
from parity.
Yes, all those commands work.
Speaking of heroku CLI plugins, I don't remember installing any of those. I've just checked now and it seems that those came installed by default together with heroku-toolbelt brew formula. I think it's just the newer versions of heroku CLI display more information than previous ones. Try running heroku --version
and see if you get the same output with addons.
Seems like the gem I had (0.9.2) worked for using staging restore production
. I've just tried now to re-run staging restore production
(on 0.9.3) and it failed with the error above. Indeed it is a different issue. I'll try and see if I can figure out what could be the issue.
from parity.
Do you have git remotes defined for the app? We're using git remotes now rather than the app name. What's the output of git remote -v
for your app?
from parity.
Yes, I have the remotes set. I'm pretty sure v0.9.2 relied on having those set as well.
from parity.
@vfonic later this week I'm going to try to push out a development release so we can get some more information about what's not working here.
from parity.
@geoffharcourt sorry for the late response so I tried restore
and had the same error. I did which staging
and which production
and it also came up as the path in my bin
/usr/local/bin/production
/usr/local/bin/staging
This is with the current install not v0.9.3
from parity.
@cantonyselim can you update to v0.9.3? I'm hoping that the changes applied there will resolve your issue.
from parity.
@cantonyselim and @vfonic can you install v0.10.0 and test? I've removed external dependencies, so I expect your issues should be resolved. I've been able to execute this successfully from both Rubygems and Homebrew with v0.10.0.
from parity.
Related Issues (20)
- Feature request: specify the database to pull from HOT 7
- calling parity for customized environments without putting `bin/` before the environment HOT 1
- Feature need: handle new Heroku pipeline review app convention HOT 2
- Development restore not working after Catalina upgrade HOT 27
- Install from ubuntu not working HOT 1
- What to use when 'development' means development in Heroku pipeline HOT 2
- Feature request: deploying to `main` branch on production HOT 3
- Did you mean autosuggest somehow broken HOT 1
- Support for ERB database.yml ? HOT 3
- Feature request: add flag to use the downloaded database HOT 3
- Run tasks using parity HOT 2
- Feature request: Add `development backup`
- How to install parity without upgrading postgresql package? HOT 2
- Error on development restore call HOT 1
- Allow pushing from different branches than "main" or "master" HOT 1
- Use `--json` output? (More stable/future-proof integration)
- Restoring development from heroku broken since heroku_ext change HOT 3
- foreign key constraint violations and relation does not exist errors when restoring from production
- I love this project ❤️
- Restore to non-localhost database HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from parity.