Set up a stable frack instance at a persistent location

[Jean-Paul Calderone]

Since frack exists now, and already does some useful things, it would be beneficial to have it running somewhere predictable, such that one could reliably connect to it and request information from it.

One specific reason this would be nice is that several of our workflow helpers talk to trac to learn something about tickets or branches. They will eventually need to be updated to talk to frack instead. Then we may as well have them deployed in a frack-using configuration, since it will presumably improve their performance and decrease the load on cube.

The two main requirements for this ticket are:

 * run a stable frack instance. it should be up and running all the time, except for occasional code updates (probably on a regular schedule, like monday morning or something).
 * expose it at a well-known location - note that since frack is multi-protocol, this actually involves more than one address. The HTTP server address is one thing, the AMP server address is another. Several of the tools will need to be configured with this information and changing the configuration will be a hassle, so we should avoid the need to do so.

[Jean-Paul Calderone (exarkun)]

There is now a frack account on cube. I've set it up to only allow internal access for now.

[Glyph Lefkowitz (glyph)]

"internal access" being "bound to 127.0.0.1", you mean?

[Jean-Paul Calderone (exarkun)]

Close: to a UNIX domain socket in /var/run.

[anatoly techtonik (techtonik)]

What's the frack? =)