grunt watch not working as expected in centos 7

[dhensby]

The sass builder seems to be very intermittent at the moment - I can't get to the bottom of it at all. :(

[dhensby]

It's odd as when I run nohup grunt --base /var/www/html --gruntfile /var/www/html/Gruntfile.js watch > /dev/null 2> /dev/null < /dev/null & from the command line, it works as expected...

Seems to be a problem with the script in init.d...

[dhensby]

ok, when I add this to the end of the provisioners, grunt watch works as expected:

  config.vm.provision :shell, inline: "nohup grunt --base /var/www/html --gruntfile /var/www/html/Gruntfile.js watch \
  > /dev/null 2> /dev/null < /dev/null &", run: "always"

So, unless we have any better ideas, I'm thinking of moving the script into a run: "always" instead of a startup script. Thoughts @willmorgan ?

[dhensby]

bump @willmorgan

[Firesphere]

If I understand correctly, you want SASS to run all the time, on the VM itself?
I don't think this is a good idea. It should run on the host, not taking up VM resources.

[dhensby]

My entire aim with using vagrant is to have a complete ready to go dev environment without needing to install anything on a host apart from the software required to run the VM.

Installing sass on the host defeats my entire aim of having self-containted and self-provisioned environments to pass along to any developer.

[dhensby]

I think that grunt is now working as expected now - but I haven't been hands on recently to be certain

[Firesphere]

Although I agree with having a complete package, I still feel a bit unsettled about running everything in the VM.
Using SASS is a developers choice after all, right?

[dhensby]

Well, sure... but if your project set up dictates it's required, then there's no choice on the individual choice.

I don't see this as an individuals approach to working on a project; it's a holistic approach where the entire team would be developing on a VM.

So any software would only be installed on the VM if the project needed it.

Further, this project is to support SilverStripe developers and their contributions to the OSS project, some contributions require SASS for that and installing it automatically on the VM lowers the barrier to entry for contributors.