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
Can't seem to deploy with capistrano3... but all responses are successful. #41
Comments
Is that your full deploy log? Change this to |
Thanks, that helped me... been a long day... I've done this 100 times and today I'm just losing it. |
my only issue now seems to be this:
|
Does running http://discourse.roots.io/t/capistrano-composer-step-failure/1046 |
Yep it does work if I SSH into the server. |
Well then you may need to update your command map to point to the absolute path of set :default_env, { path: "/usr/local/bin:$PATH" } Either way, this isn't a Bedrock issue as we don't include any server configuration yet. I suggest checking into Capistrano docs/help and/or SSHKit. Or you can post in the Roots discourse forum. |
That fixed it! Thank you!
|
Can you post exactly what you changed for reference? Helps if someone else comes across this issue. |
Well, it will definitely be different for everyone but you just set this line in your deploy.rb Mine happened to be under the current user's "bin" directory. But it could be anywhere, really. |
I have both lines in set :default_env, { path: "/usr/local/bin:$PATH" }
SSHKit.config.command_map[:composer] = "/usr/local/bin/composer" and I'm still getting the composer stdout error: INFO [17eba5fc] Running /usr/local/bin/composer install --no-dev --no-scripts --quiet --optimize-autoloader on staging.thisisreneruiz.com
cap aborted!
composer stdout: Nothing written
composer stderr: Nothing written I even tried installing composer with Capistrano's available tasks: I've tried rebooting the machine. Based on those two links that @swalkinshaw posted, I updated EDIT: Okay, looks like I had to add this to
That was the location that |
Shouldn't have anything to do with memory. I would remove the Please try with |
I have similar problem with my deployment process. I set the default env to "set :default_env, { path: "/usr/local/bin:$PATH" }" and additionally added this line "SSHKit.config.command_map[:composer] = "/usr/local/bin/composer"". Now I wonder if i get this whole thing right. Does composer has to be installed on my server or just on my local machine? I have composer installed on my local machine and it is in the /usr/local/bin folder. The error looks like this: |
@byrus It's executing that command on the remote server. So you need Composer installed there and the command map should reference the path on the remote server. |
I had a similar issue. Capistrano deployment would throw an error when attempting to run the composer tasks.
I installed composer on my remote server, in my user directory ( Then I moved composer.phar to enable the Everything works fine now. |
I am now running into this issue. The only thing about my local setup that changed is that I am directly plugged into my router now instead of using my WiFi. Not sure if that would make any difference. I'm still able to SSH into my shared host and running composer with Here is my complete deploy log: http://pastebin.com/1WB4AyVu There are failures on lines 73, 76, 82, 85, and 94 but from what I remember these have been present all along and deploys have been fine. It's been about a month since my last successful deploy. Any troubleshooting help would be great guys. Thanks! |
Have you tried going into the written deploy directory on the remote server and running composer install manually to see what the error is? |
@etcook thank you! Noob mistake. I thought for sure the written deploy dir would be removed if the deploy was unsuccessful. Shame on me for not checking. Running Thanks again! |
Since this is top result for google... figured I'd post this other thing that helped resolve my issues for some strange reason... added: set :composer_install_flags, '--no-dev --no-interaction --optimize-autoloader' by removing the |
This all looks good, but it doesn't create the directories or anything.
The text was updated successfully, but these errors were encountered: