3

I have vagrant setup as my local dev environment. When vagrant is up and I edit my CSS file and look at its source in the browser the new CSS I have written is not in the file and the file is now appended by loads of question marks:

��������������������������

If I do vagrant halt or destroy and then bring it back up the CSS file is fine with the new code visible and formatted correctly and no sign of the question marks. As soon as I edit it again the same things happens. Obviously I don't want to destroy and create vagrant every time I make a CSS change.

Any ideas on this?

Update: I have been told this may be to do with not having NFS installed with vagrant - I am on ubuntu and my files are within an encrypted home directory so I believe NFS doesn't work - any other solutions?

2 Answers2

0

I had lot of problems with not having nfs activated on my VM

What information do you have when you run a 'ls -la file.css' on the file ?

JulienD
  • 3,172
  • 3
  • 16
  • 16
0

Perhaps you can disable sendfile based on this thread:

JS and CSS files in vagrant not properly encoded when saved outside of the VM

Set enableSendFile to off in httpd.conf.

Community
  • 1
  • 1
Joseph Cardwell
  • 85
  • 1
  • 6