By rcc
So I created a new default nginx/unicorn/rails droplet and then modified just the default homepage file (/home/rails/app/views/home/index.html.erb).
The change never showed up when I reloaded the page. Not in any number of browsers, not after emptying their caches. Today I found that the change DID show up after I restarted the unicorn service.
So my question is, why did that fix it, and why should it be necessary? I’ve reviewed the configuration files for both unicorn and nginx, and I can’t see anything that should be causing the pages to be cached…
TiA
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
This question is very similar. The quick answer is that, yes, with the default unicorn settings you will need to perform a unicorn restart for your changes to appear. Adjustments to your configuration may allow you to make changes to your erb files without a reload being required but at the expense of some caching.
Hi, I have question based on updating or changing css/js files. The changes are not reflected. Any help so that on refresh changes made are shown?
Regards, Polycarp
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.