WebROaR is under continuous development. We are happy to announce release of WebROaR v0.4.0 which contains new features, enhancements and bug fixes.
Here is the list of changes after v0.3.1 release:
- Supports deflate encoding for static assets.
- Support for passing environment variables to application.
- Support to build server with static Ruby library.
- Tested on Ruby 1.9.2 RC2
- Tested on Ubuntu 10.04.
- Directory path expanded when application is added from command line. (It would allow to pass relative path)
- Fixed incorrect response code of static assets by using 'timegm' function instead of 'mktime'.
- Requiring version.rb using relative path, to work with Ruby 1.9.2.
- Added Config::CONFIG['rubyhdrdir'] in ruby headers search path for Ruby 1.9.
- Sends '503 Service Unavailable' response, if pending message queue overflows.
- Code cleanup in Rake tasks.
- Enhanced SCGI request parsing in Admin Panel to handle chunked request.
- Added tests for application add, remove and zero down time during restart.
- Added Config::CONFIG['includedir'] in include directory list.
- Supports Rails 3 application.
- Created 'config.yml' file with default configuration if it is not found while importing.
- Added support to start/stop/restart static-worker.
- Support to view analytics data for all the application, earlier it was only for the application which has analytics enabled.
- Saving log files after executing load test.
- Improved rake task to execute test-suite.
- Set Expires headers from Admin Panel.
- Server specification code cleanup in Admin Panel.
- Passing application configuration parameters to worker using SCGI.
- Email notification for the captured exceptions made configurable.
- Made many server parameters configurable through config file 'serverinternalconfig.yml'.
- Sends ERROR control message, if application could not be loaded by worker.
- Wait for 30 minutes before creating new worker, if three consecutive newly created worker got timed out.
- Removed 'Cache-Control' response header from static assets. Its incorrect handling choking IE 6.
sudo gem install webroar sudo webroar install
In case you have a previous installation of WebROaR, the install would give an option to import previous configuration, logs and admin panel data. Or you can also choose to install afresh and deploy your application(s) again.
You can also refer the WebROaR User Guide for more detailed information.
We are thankful to all the people who reported the issues on Lighthouse and the mailing list. We would be very happy to receive more feedback/comments and bug-reports. Look forward to your support for WebROaR, please run your ruby web application on it and let us know how it goes.