I need to pass some startup options on to my rails application. Using environment variables will not work because multiple mongrel clusters of my rails application (each of a slightly different flavour) served from a single code base can run concurrently and each cluster instance is activated via mongrel_service.
Extra arguments passed in to either mongrel_rails service::install or mongrel_rails cause errors. The only documentation on the --script option I could find related to unix so I gave up on that thought. I also tried using the --config option, but I had the same problem there: as soon as I added an option to the YAML file that wasn't documented, mongrel complained with an error. The last one is a real nuisance. It just doesn't make sense that my config file should be restricted to content mongrel understands. Wouldn't it be a better approach to parse that file and look/apply the options mongrel recognises and provide a public interface so that other interested clients can access the config file? Or are there other ways to achieve this without resorting to modifying mongrel and mongrel services startup code? Pete _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
