Mixing
heroku deploy fails with fog-aws (says formatador “removed”)
I have a web site uploading images to AWS using the fog-aws gem. Everything works fine when I run it locally, but it will not deploy to heroku. Standard heroku/ruby buildpack, latest versions of everything:
ruby 2.5.1, rails 5.2.2,
gem 'carrierwave', '1.3.1'
gem 'fog-aws', '3.3.0'
Tried:
1) Of course, deleting the Gemfile.lock file and bundle installing several times
2) Explicitly including formatador, using older versions (I don't think the error message is correct, since formatador 0.2.5 does exist and I can install it both locally and on heroku)
3) Using 'fog' instead of 'fog-aws' (gives me similar errors with 'unf', and includes a ton of unnecessary dependencies)
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.5.1
remote: -----> Installing dependencies using bundler 1.15.2
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.3). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Your bundle is locked to formatador (0.2.5), but that version could not be found
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of formatador (0.2.5) has removed it. You'll need to
remote: update your bundle to a different version of formatador (0.2.5) that hasn't been
remote: removed in order to install.
remote: Bundler Output: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.3). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Your bundle is locked to formatador (0.2.5), but that version could not be found
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of formatador (0.2.5) has removed it. You'll need to
remote: update your bundle to a different version of formatador (0.2.5) that hasn't been
remote: removed in order to install.
ruby-on-rails heroku fog-aws
asked Jan 1 at 20:13
user3407688user3407688
283
add a comment |
I have a web site uploading images to AWS using the fog-aws gem. Everything works fine when I run it locally, but it will not deploy to heroku. Standard heroku/ruby buildpack, latest versions of everything:
ruby 2.5.1, rails 5.2.2,
gem 'carrierwave', '1.3.1'
gem 'fog-aws', '3.3.0'
Tried:
1) Of course, deleting the Gemfile.lock file and bundle installing several times
2) Explicitly including formatador, using older versions (I don't think the error message is correct, since formatador 0.2.5 does exist and I can install it both locally and on heroku)
3) Using 'fog' instead of 'fog-aws' (gives me similar errors with 'unf', and includes a ton of unnecessary dependencies)
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.5.1
remote: -----> Installing dependencies using bundler 1.15.2
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.3). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Your bundle is locked to formatador (0.2.5), but that version could not be found
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of formatador (0.2.5) has removed it. You'll need to
remote: update your bundle to a different version of formatador (0.2.5) that hasn't been
remote: removed in order to install.
remote: Bundler Output: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.3). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Your bundle is locked to formatador (0.2.5), but that version could not be found
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of formatador (0.2.5) has removed it. You'll need to
remote: update your bundle to a different version of formatador (0.2.5) that hasn't been
remote: removed in order to install.
ruby-on-rails heroku fog-aws
asked Jan 1 at 20:13
user3407688user3407688
283
maybe post the gemfile too.
– Aaditya Maheshwari
Jan 1 at 20:17
add a comment |
I have a web site uploading images to AWS using the fog-aws gem. Everything works fine when I run it locally, but it will not deploy to heroku. Standard heroku/ruby buildpack, latest versions of everything:
ruby 2.5.1, rails 5.2.2,
gem 'carrierwave', '1.3.1'
gem 'fog-aws', '3.3.0'
Tried:
1) Of course, deleting the Gemfile.lock file and bundle installing several times
2) Explicitly including formatador, using older versions (I don't think the error message is correct, since formatador 0.2.5 does exist and I can install it both locally and on heroku)
3) Using 'fog' instead of 'fog-aws' (gives me similar errors with 'unf', and includes a ton of unnecessary dependencies)
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.5.1
remote: -----> Installing dependencies using bundler 1.15.2
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.3). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Your bundle is locked to formatador (0.2.5), but that version could not be found
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of formatador (0.2.5) has removed it. You'll need to
remote: update your bundle to a different version of formatador (0.2.5) that hasn't been
remote: removed in order to install.
remote: Bundler Output: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.3). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Your bundle is locked to formatador (0.2.5), but that version could not be found
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of formatador (0.2.5) has removed it. You'll need to
remote: update your bundle to a different version of formatador (0.2.5) that hasn't been
remote: removed in order to install.
ruby-on-rails heroku fog-aws
asked Jan 1 at 20:13
user3407688user3407688
283
I have a web site uploading images to AWS using the fog-aws gem. Everything works fine when I run it locally, but it will not deploy to heroku. Standard heroku/ruby buildpack, latest versions of everything:
ruby 2.5.1, rails 5.2.2,
gem 'carrierwave', '1.3.1'
gem 'fog-aws', '3.3.0'
Tried:
1) Of course, deleting the Gemfile.lock file and bundle installing several times
2) Explicitly including formatador, using older versions (I don't think the error message is correct, since formatador 0.2.5 does exist and I can install it both locally and on heroku)
3) Using 'fog' instead of 'fog-aws' (gives me similar errors with 'unf', and includes a ton of unnecessary dependencies)
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.5.1
remote: -----> Installing dependencies using bundler 1.15.2
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.3). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Your bundle is locked to formatador (0.2.5), but that version could not be found
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of formatador (0.2.5) has removed it. You'll need to
remote: update your bundle to a different version of formatador (0.2.5) that hasn't been
remote: removed in order to install.
remote: Bundler Output: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.3). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Your bundle is locked to formatador (0.2.5), but that version could not be found
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of formatador (0.2.5) has removed it. You'll need to
remote: update your bundle to a different version of formatador (0.2.5) that hasn't been
remote: removed in order to install.
ruby-on-rails heroku fog-aws
ruby-on-rails heroku fog-aws
asked Jan 1 at 20:13
user3407688user3407688
283
asked Jan 1 at 20:13
user3407688user3407688
283
asked Jan 1 at 20:13
user3407688user3407688
283
asked Jan 1 at 20:13
user3407688user3407688
283
asked Jan 1 at 20:13
user3407688user3407688
283
283
maybe post the gemfile too.
– Aaditya Maheshwari
Jan 1 at 20:17
add a comment |
maybe post the gemfile too.
– Aaditya Maheshwari
Jan 1 at 20:17
maybe post the gemfile too.
– Aaditya Maheshwari
Jan 1 at 20:17
maybe post the gemfile too.
– Aaditya Maheshwari
Jan 1 at 20:17
add a comment |
1 Answer
1
active
oldest
votes
Figured it out; just needed to RTFM!
I needed a "require 'fog/aws'" at the top of config/initializers/fog.rb. Worked locally without it, but caused the behavior above when deployed to heroku. I added that line, and it worked.
answered Jan 2 at 1:35
user3407688user3407688
283
add a comment |
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%2f53998608%2fheroku-deploy-fails-with-fog-aws-says-formatador-removed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Figured it out; just needed to RTFM!
I needed a "require 'fog/aws'" at the top of config/initializers/fog.rb. Worked locally without it, but caused the behavior above when deployed to heroku. I added that line, and it worked.
answered Jan 2 at 1:35
user3407688user3407688
283
add a comment |
Figured it out; just needed to RTFM!
I needed a "require 'fog/aws'" at the top of config/initializers/fog.rb. Worked locally without it, but caused the behavior above when deployed to heroku. I added that line, and it worked.
answered Jan 2 at 1:35
user3407688user3407688
283
add a comment |
Figured it out; just needed to RTFM!
I needed a "require 'fog/aws'" at the top of config/initializers/fog.rb. Worked locally without it, but caused the behavior above when deployed to heroku. I added that line, and it worked.
answered Jan 2 at 1:35
user3407688user3407688
283
Figured it out; just needed to RTFM!
I needed a "require 'fog/aws'" at the top of config/initializers/fog.rb. Worked locally without it, but caused the behavior above when deployed to heroku. I added that line, and it worked.
answered Jan 2 at 1:35
user3407688user3407688
283
answered Jan 2 at 1:35
user3407688user3407688
283
answered Jan 2 at 1:35
user3407688user3407688
283
answered Jan 2 at 1:35
user3407688user3407688
283
283
add a comment |
add a comment |
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%2f53998608%2fheroku-deploy-fails-with-fog-aws-says-formatador-removed%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
maybe post the gemfile too.
– Aaditya Maheshwari
Jan 1 at 20:17