nginx.conf + grunt-watch = cool nginx workflow


I started working with nginx+lua, and the first thing that came to my mind when thinking about editing nginx.conf file is having to reload nginx on every edit. So what also came to mind was the great Grunt.js

Grunt has the watch plugin… watch a file, when there is a change: run task. So I set it up to watch the nginx.conf and run nginx -s reload:

1. Install node, grunt, grunt-contrib-watch, grunt-run

sudo apt-get install nodejs npm

I had some problems in npm configured with the nodejs binary and grunt trying to run from the node library, so i simply copied the nodejs library to node

cp /usr/bin/nodejs /usr/bin/node


not about java or php or tools, but the initial words on what to worry about when designing architecture

Gzip on jetty 9.2.1

While learning about the lapis framework and openresty i needed a web server to work in production serving the static html for campobeloresort.

At the moment the site still has the prototype code, which was ‘ok’ enough for production while i re-code it with Lapis. So i needed a quick-setup, easy, capable web server… ended up with jetty. Great, little, capable web server, install java-sdk, download the zip and run (in terminal, inside the directory extracted from the downloaded zip):

java -jar start.jar

It was simple to get it working, but i wanted to enable gzip to get that extra juice of network performance, and had a little headache to get the correct information for setup for version 9.2.1 (current). So here is the configuration that actually Worked!!