On Mon, Dec 1, 2008 at 11:05 AM, Mislav Marohnić <[EMAIL PROTECTED]> wrote: > Re: github.com/rails/rails/commit/3b3c05 > Says process scripts were extracted to github.com/rails/irs_process_scripts, > but that repo hasn't been pushed to. Did DHH forget?
Seems like it. > What was the reason for this change; because it wasn't portable (unix only)? > Has it something to do with moving over to Rack? They're not particularly portable, nor are they particularly useful. Every project I've worked on uses some other method of process spawning and monitoring. Monit, God, Runit, mongrel_cluster, etc. Shipping with a mostly-broken set of scripts doesn't seem like something we should do. 2.3 is probably a while off, so hopefully the cobwebs get blown out and no one even notices :). > Default Capistrano recipe > kinda relies on these and I use them in most of my projects that aren't on > Passenger. I think we'll send jamis some patches to change the default capistrano recipes, or remove them entirely, or something. > # Mislav > > > > > > -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
