Thin

Comments and changes to this ticket

• 

  Kevin Williams January 19th, 2008 @ 07:51 PM

  • → Milestone cleared.
  • → State changed from “new” to “open”
• 

  macournoyer January 19th, 2008 @ 10:35 PM

  • → Assigned user changed from “macournoyer” to “James”
• 

  Kevin Williams January 26th, 2008 @ 11:32 AM

  • → Milestone changed from “” to “0.6.2”
• 

  macournoyer January 30th, 2008 @ 12:44 AM

  • → Milestone changed from “0.6.2” to “0.7.0”
• 

  Gump February 5th, 2008 @ 06:27 PM

  Didn't know how this was progressing, but after working on a runlevel service for thin similar to mongrel_cluster I've decided to look into god support. See my attached thin.god file. It is a config file for god that configures watches for each instance of a thin server for each thin configuration file found in /etc/thin. This takes a rather simple approach by taking advantage of the -o flag for thin. This allows us to simply loop through making creating start, stop, and restart commands passing in a config file and number of server. You could add additional optional commands in your thin config files to specify watch intervals and such. In order to get it working on Ubuntu, I had to make a change to god as noted at the following blog:

  http://blog.alexgirard.com/2007/...

  • thin.god 1.6 KB
• 

  macournoyer February 5th, 2008 @ 09:53 PM

  Wow, this is freaking awesome Gump!

  I'd really love to integrate this into thin. What's your idea about this, do you think we should replace runlevel service w/ this eventually?

• 

  Gump February 5th, 2008 @ 10:27 PM

  Marc, I think that runlevel services is a fine thing to integrate tightly with thin. This God config file is something that I see people using as a starting point for using God with Thin. I don't want to see Thin getting extra cruft added just to support this gem or that gem. Thin should stay ... well ... thin (my opinion).

  Since God is a third party gem that really doesn't need too much more than a pid file to integrate with I don't see the need to necessarily add anything to Thin to support it. I can see simply adding this in an examples/god directory or something that the user can copy to their god staging area and add through a "god load " to get it up and running.

  I haven't fully finished testing this yet, it doesn't seem to want to shut things down nicely when you tell god to stop or quit. I'm not sure if it is a God or Thin issue. I find the documentation of God a little lacking at the time, but I'm still learning.

  -Forrest

• 

  macournoyer February 5th, 2008 @ 10:11 PM

  You're right, I'll include it in the example dir for now.

• 

  macournoyer February 6th, 2008 @ 12:17 AM

  I updated the example/thin.god file w/ this one on git.

  thx Gump!

• 

  macournoyer February 15th, 2008 @ 11:20 PM

  • → State changed from “open” to “resolved”

  example file now support unix and tcp sockets

  god leaks mem so I rly don't think it's a good idea to integrate more w/ thin.