DB Restoration From Staging to Production with Parity
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Using parity with my Heroku apps, I'd like to restore my production database from staging. This should be possible based on the documentation using the --force
argument, yet passing this argument results in an error: Error: Unexpected argument: --force
.
Here's the exact command I am using: production restore staging --force
.
So far, I've tried:
- Reinstalling Parity via the install instructions
- Adjusting where the
--force
argument is placed - Opening a new terminal window and executing the commands again
- Updating heroku_cli via brew
Any help would be appreciated!
ruby-on-rails heroku thoughtbot
add a comment |
Using parity with my Heroku apps, I'd like to restore my production database from staging. This should be possible based on the documentation using the --force
argument, yet passing this argument results in an error: Error: Unexpected argument: --force
.
Here's the exact command I am using: production restore staging --force
.
So far, I've tried:
- Reinstalling Parity via the install instructions
- Adjusting where the
--force
argument is placed - Opening a new terminal window and executing the commands again
- Updating heroku_cli via brew
Any help would be appreciated!
ruby-on-rails heroku thoughtbot
add a comment |
Using parity with my Heroku apps, I'd like to restore my production database from staging. This should be possible based on the documentation using the --force
argument, yet passing this argument results in an error: Error: Unexpected argument: --force
.
Here's the exact command I am using: production restore staging --force
.
So far, I've tried:
- Reinstalling Parity via the install instructions
- Adjusting where the
--force
argument is placed - Opening a new terminal window and executing the commands again
- Updating heroku_cli via brew
Any help would be appreciated!
ruby-on-rails heroku thoughtbot
Using parity with my Heroku apps, I'd like to restore my production database from staging. This should be possible based on the documentation using the --force
argument, yet passing this argument results in an error: Error: Unexpected argument: --force
.
Here's the exact command I am using: production restore staging --force
.
So far, I've tried:
- Reinstalling Parity via the install instructions
- Adjusting where the
--force
argument is placed - Opening a new terminal window and executing the commands again
- Updating heroku_cli via brew
Any help would be appreciated!
ruby-on-rails heroku thoughtbot
ruby-on-rails heroku thoughtbot
asked Jan 4 at 18:52
Luke KellerLuke Keller
1,85521423
1,85521423
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54044520%2fdb-restoration-from-staging-to-production-with-parity%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54044520%2fdb-restoration-from-staging-to-production-with-parity%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown