After 9 years of development, Nginx hit a milestone release this week when version 1.0.0 was released (on 12th April 2011). Despite only now reaching a 1.0 release, it is already in widespread use, powering a lot of high traffic websites and CDN’s and is very popular with developers in particular. With such a milestone [...]
As a followup to my last post I’ve been thinking about the best way to migrate over a production server and be able to test the new config without blatting what’s currently running so that the new setup can be tested before blowing the old one away, so what I did was to test having my unicorn setup running and then a separate instance running the standard WEBrick.
On the puppetmaster (with the nginx+unicorn setup already running) I ran:
/usr/bin/ruby1.8 /usr/bin/puppet master --masterport=18141 --servertype=webrick --pidfile /var/run/puppet/thingy.pid --no-daemonize --verbose --debug
and on my test client:
puppetd --test --verbose --debug --detailed-exitcodes --masterport 18141
With a verified client, this should run just fine, and you should see a load of output scroll past on your non-daemonized puppetmaster instance. This shows that we can (as the documentation would imply) run multiple instances of puppetmasterd via different webservers on different ports, so it is possible to set up and test an entirely different puppetmaster instance using nginx+unicorn whilst the production instance is running. Then it’s just a case of changing the config and changing the ports.
This page should outline how to set up puppet behind and nginx proxy with a unicorn ruby webserver to replace the default WEBrick. The purpose of doing this is to firstly speed up puppet’s file access and script running and then to proxy it so that ngi…
Puppet really shines at configuration management, but there are some things it is not good at, for instance file sourcing of large files, or managing deep hierarchies. Fortunately, most of this efficiency issues will be addressed in a subsequent major version (thanks to some of my patches and other refactorings). Meanwhile it is interesting to [...]
Puppet really shines at configuration management, but there are some things it is not good at, for instance file sourcing of large files, or managing deep hierarchies.
Fortunately, most of this efficiency issues will be addressed in a subsequent major…
At $WORK I started using Nginx a while ago, first as a front end to my mongrel instances for puppet. Recently I began to use it for one of its most know features : reverse proxy (and caching too). Of course this work had to be puppetized !
This is a summary of what I’ve done [...]
As every reader of this blog certainly know, I’m a big fan of Puppet, using it in production on Days of Wonder servers, up to the point I used to contribute regularly bug fixes and new features (not that I stopped, it’s just that my spare time is a scarce resource nowadays). Still, I think [...]
As every reader of this blog certainly know, I’m a big fan of Puppet, using it in production on Days of Wonder servers, up to the point I used to contribute regularly bug fixes and new features (not that I stopped, it’s just that my spare t…
Yes, I know… I released v0.7 less than a month ago. But this release was crippled by a crash that could happen at start or reload. Changes Bonus in this new version, brought to you by Tizoc: JSONP support Long awaited fix for X-Progress-ID to be the last parameter in the request parameter If you [...]
Yes, I know… I released v0.7 less than a month ago. But this release was crippled by a crash that could happen at start or reload.
Changes
Bonus in this new version, brought to you by Tizoc:
JSONP support
Long awaited fix for X-Progress-ID to…
