Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not location Gemfile for rails tasks #73

Closed
sethvargo opened this issue Dec 4, 2012 · 3 comments
Closed

Could not location Gemfile for rails tasks #73

sethvargo opened this issue Dec 4, 2012 · 3 comments

Comments

@sethvargo
Copy link

All of the Rails tasks are failing. It correctly SSHes to the server, but then fails with:

-----> Precompiling asset files
Could not locate Gemfile
Connection to xxx closed.

 !     Command failed.
       Failed with status 2560

There IS a Gemfile though.

@mikong
Copy link
Member

mikong commented Dec 18, 2012

This just means bundler is being run in a different directory than your Gemfile. Could you share your deploy script in a gist?

@mikong mikong closed this as completed Dec 18, 2012
@jbonney
Copy link

jbonney commented Jul 24, 2013

Just in case it might help others, in order to ensure that you are in the application folder (and therefore have access to the Gemfile), simply do a queue! %[cd "#{deploy_to!}/#{current_path!}"] before calling the action that requires the Gemfile.

@agirorn
Copy link

agirorn commented Sep 23, 2014

Should that not be the responsibility of the command in question?

For instance if calling this command.

mina rails:db_migrate

Should it not first cd into the correct directory and then perform the migration command.
This could be done withe pushd and popd for instance to leave the script in it starting directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants