Running "compass:release" (compass) taskDEBUG [325e3552] Warning: Command failed: /bin/sh: compass: command not found Use --force to continue.
I read http://capistranorb.com/documentation/advanced-features/ptys/ and it specifically calls out that rbenv causes issues, however the documentation doesn't provide links on how to fix anything. Now, we're not using multiple versions of Ruby as mentioned in the document, but we are using rbenv so we can run Ruby 2.2 on CentOS 6.x. The default on Cent 6 is 1.8 and our want / need is to use 2.2 because it is several orders faster with Compass than 1.8. But rbenv relies on files in /etc/profile.d.
I would be appreciative if someone could just point me to documentation on how to properly implement a solution - do I just use the 'with bash_env: "some path" do' method? Or is the "right" answer that we are forced to use Ruby 1.8 because that is the RPM / platform specific and supported version (I probably would be willing to break with standards if that is the case though - Ruby 2.2 is 2x-4x faster than Ruby 1.8 from what I am seeing).
--
You received this message because you are subscribed to the Google Groups "Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+unsubscribe@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/3be2949c-e9c4-4a94-88d4-aaa13c500589%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Justin,Were you still struggling with this?
On 4 November 2016 at 14:00, <justin...@buyerquest.com> wrote:
Versions:
- Ruby - ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux] (from /opt/rbenv/shims/ruby)
- Capistrano - 3.5.0
- Rake / Rails / etc - not installed / used
Platform:
- We are deploying a custom PHP application to a cluster, the deploy works fine, until the code tries to run compass, then we receive the following:
Running "compass:release" (compass) taskDEBUG [325e3552] Warning: Command failed: /bin/sh: compass: command not found Use --force to continue.I read http://capistranorb.com/documentation/advanced-features/ptys/ and it specifically calls out that rbenv causes issues, however the documentation doesn't provide links on how to fix anything. Now, we're not using multiple versions of Ruby as mentioned in the document, but we are using rbenv so we can run Ruby 2.2 on CentOS 6.x. The default on Cent 6 is 1.8 and our want / need is to use 2.2 because it is several orders faster with Compass than 1.8. But rbenv relies on files in /etc/profile.d.I would be appreciative if someone could just point me to documentation on how to properly implement a solution - do I just use the 'with bash_env: "some path" do' method? Or is the "right" answer that we are forced to use Ruby 1.8 because that is the RPM / platform specific and supported version (I probably would be willing to break with standards if that is the case though - Ruby 2.2 is 2x-4x faster than Ruby 1.8 from what I am seeing).
- CentOS 6.x
--
You received this message because you are subscribed to the Google Groups "Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/3be2949c-e9c4-4a94-88d4-aaa13c500589%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+unsubscribe@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/6ee22808-01d9-4c3b-b9e5-e8b94ce8077a%40googlegroups.com.
DEBUG [42d8fbc2] Running "compass:release" (compass) task DEBUG [42d8fbc2] Warning: Command failed: /bin/sh: compass: command not found Use --force to continue. Aborted due to warnings.
[justin.spies@ip-111-111-111-111 ~] :) which compass
/opt/rbenv/shims/compass
[justin.spies@ip-111-111-111-111 dev.yoursite.com] :( sudo su - builds
[sudo] password for justin.spies:
[builds@ip-111-111-111-111 ~] :) cd /var/www/dev.yoursite.com/
[builds@ip-111-111-111-111 dev.yoursite.com] :) grunt
Running "compass:release" (compass) task
write skin/frontend/buyerquest/default/css/admin.css (9.968s)
write skin/frontend/buyerquest/default/css/login.css (1.455s)
To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/7390c6dc-bb76-4ae1-937c-cdba6f76ad04%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+unsubscribe@googlegroups.com.
Lee - no this is good info and what I needed. This is our last site using Compass at the moment and this may just push us to invest the time we need to get rid of Compass. I'm on the Ops, not the Dev side, so will need to take this back to the Devs and get buy in, but I appreciate the feedback.
I had read that link you provided as well, the thing is just getting all the pieces together. I'm wondering if this is a real world example where the docs can be updated to outline best practices?
I'm not familiar with BrightBox and a search for only BrightBox turned up a lot of results (most not relevant). Would be great to get a link from you so I can share that with our Developers.