SwitchPipe 1.04 has been released. There have been no real
architectural changes (these will be for 1.05!) but several pragmatic,
needs-driven improvements, as follows:
* Support for using Host headers to decide which application to run
-
http://groups.google.com/group/switchpipe/browse_thread/thread/74ac837f84cc521b
* Switched from using Curl to using Ruby in the demo app as some
people don't have Curl
-
http://groups.google.com/group/switchpipe/browse_thread/thread/23a9bf970be64eb6
* Support for "min_instances" on app configs, enabling a minimum
number of instances
to have running at any time for an app
-
http://groups.google.com/group/switchpipe/browse_thread/thread/e652a55e8b57e312
* Added an "inactivity_timeout" setting for config.yml so that
connections aren't automatically
wiped after 10 seconds of inactivity (default is now 30)
* Now *removes* apps when config files are deleted while SwitchPipe is
running
It can be checked out at:
http://switchpipe.org/switchpipe1/tags/release-1.04
.. with a tarball available at
http://switchpipe.org/switchpipe-1.04.tar.gz
.. or you can continue to use trunk which includes all of these
features already.
The biggest deal in this release is that it supports "Host" headers so
you can, if you like, use SwitchPipe as the public-facing daemon and
serve full applications on regular hostnames from it. Even though this
appears to work well, I'd recommend this primarily for internal
development use, internal deployments, etc. It has not been heavily
tested enough in full-scale environments.
Many thanks to all of you who have joined the group, posted, or given
feedback in other ways.
Regards,
Peter Cooper
http://www.petercooper.co.uk/