fix vagrant #480
Loading…
Reference in a new issue
No description provided.
Delete branch "vagrant12"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The only problem I still get it the fonts that doesn't work for some reason. I spent some time on that but couldn't find why. Especially as it is working on my home machine, so I guess a problem with nginx config...
Don't know why, but it seems that disabling the use of
sendfile()
- by addingsendfile off;
to nginx config - will fix the fonts download issue.Oh true, I remember doing this a while back. I've added that, thanks @floss4good
WIP: fix vagrantto fix vagrantSpeaking to myself (and for posterity):
I was tempted to think that (since only font files were affected) it would be wiser to add
sendfile off;
within alocation
block. However, knowing almost nothing about NGINX configurations I further investigated this and found out it is actually an old VirtualBox issue: when the web server (be it Apache or NGINX, maybe also others) tries to deliver static files using sendfile (a kernel feature) that were transferred to the VM using VirtualBox Shared Folders issues might occur (mainly caching issues).NGINX has a VirtualBox headline within Pitfalls and Common Mistakes wiki page that recommends setting sendfile off when deployed in VB:
Also, in case of Apache httpd, the docs of EnableSendfile Directive, recommend disabling the use of this feature in certain situations (including for network mounted files).
These being said, since the Vagrant box it is just a development environment, I conclude that in our case disabling sendfile at server level is a good workaround.