I’ve written a small tool to warm-up HTTP caches, e.g. services like nginx.
Source code as well as compiled releases are available at Github.
I’ve written a small tool to warm-up HTTP caches, e.g. services like nginx.
Source code as well as compiled releases are available at Github.
I’m editing nginx configuration files. A lot. Naturally, I’ve tried several plugins for my favorite editor vim - but ran around a lot of problems:
ssl_cipher
directives, etc.So, I’ve created a new, super-cool and mega-advanced vim plugin for nginx!
Ladies and gentlemen: Please welcome, chr4/nginx.vim!
Edit: This plugin was integrated into Vim and Neovim upstream!
The plugin is based on the recent vim plugin distributed with nginx-1.12.0
and additionally features the following syntax improvements:
ssl_protocols
as errorsproxy_next_upstream
optionssticky
optionsupstream
server
optionsFurthermore:
When doing maintenance on a web application, you probably have a custom 503
site, showing your customers that the servers are currently lying on the operating table.
At the dynamic ridesharing service flinc, we touch a certain file on our reverse proxies (e.g. using capistrano deploy:web:disable
) when maintenance begins. Nginx then serves a static “we’ve disabled the site for maintenance” site, instead of the actual content.
But wouldn’t it be nice to test your web application before going live for your customers? It sure would. Unfortunately, this is not as simple as a task as you might think, because you cannot nest if
directives in an Nginx location and if is evil.