Earlier I asked about how to disable the SASS / Ruby stuff in Omega 4. As I understood it from that answer plus other reading, the SASS / Ruby compatibility in Omega 4 does nothing until the user tells it to compile SASS into CSS via Compass or Guard, and can be ignored - and that it's normal to not install Ruby on production servers for Drupal sites using Omega 4, since SASS is a development tool.

Great. I uninstalled Ruby from my production server.

Now I'm seeing this strange error message, while manually copying layout template files from Omega theme to my subtheme:

enter image description here

It seems to be trying to trigger some Ruby process while performing a simple cd change directory operation in my Omega theme folders - and it's failing, complaining that Ruby is not installed. This is interfering with normal activities.

When navigating between Omega 4 subtheme directories using cd in SSH, I've also noticed surprising Ruby-related messages.

What's going on here? Something Omega 4 related appears to exist which is trying to respond to folder access attempts by launching a Ruby process. What is it, and how do I get rid of it?

(either that, or my server is haunted)

  • When navigating between Omega 4 subtheme directories using cd in SSH, I've also noticed surprising Ruby-related messages. That's the biggest clue that this isn't Omega's 'fault' if you like. A file's existence can't alter the behaviour of cd, unless the server is watching for it. You've probably got guard/grunt/something else watching those folders – Clive Aug 23 '14 at 17:12
  • That sounds plausible, I'd thought Guard was part of the ruby stack and would disappear when I uninstalled Ruby. So many dependencies for a themer's tool that just writes CSS... I'll research how to kill Guard. – user568458 Aug 23 '14 at 17:15
  • ps aux | grep guard, kill the process, try navigating again. If that works, find out what's instigating that process and kill it – Clive Aug 23 '14 at 17:16
  • They aren't really dependencies as much options - I mean obviously compass relies on ruby so you can't use compass without ruby...but guard is optional, you can just compass compile or compass watch if you prefer. The recent proliferation of these stacks is actually a really good thing, I can't begin to tell you much time they save once you're familiar enough with them to customise your whole front-end dev workflow – Clive Aug 23 '14 at 17:19
  • So after lots of googling it sounds like Guard is a ruby gem. Not sure how it's still running, but presumably this means that if I kill the process with the command you gave, Guard is dead for good? And any "guard files" it's created can be safely ignored? I started guard with drush omega-guard but drush seems to be unable to stop guard. – user568458 Aug 23 '14 at 17:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.