StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>We use a clean, blank slate for our repositories. Specifically, we use <a href="http://www.slicehost.com/" rel="nofollow noreferrer">Slicehost</a> for our main repository.</p> <p>We started with a 256MB slice and upgraded later on to 512MB. Slicehost is great because you know you have a completely clean server to start with, and can build the things you need on your own.</p> <p><a href="http://articles.slicehost.com/" rel="nofollow noreferrer">Slicehosts' articles</a> are top-notch.</p> <p>Our repo server looks like this:</p> <ul> <li><a href="http://articles.slicehost.com/ubuntu-hardy" rel="nofollow noreferrer">Ubuntu Hardy Heron</a></li> <li><a href="http://articles.slicehost.com/tags/subversion" rel="nofollow noreferrer">Subversion</a></li> <li><a href="http://articles.slicehost.com/tags/apache" rel="nofollow noreferrer">Apache</a></li> <li><a href="http://articles.slicehost.com/2008/4/30/ubuntu-hardy-ruby-on-rails" rel="nofollow noreferrer">Ruby on Rails</a></li> <li><a href="http://warehouseapp.com" rel="nofollow noreferrer">Warehouse</a></li> <li><a href="http://articles.slicehost.com/2008/5/1/ubuntu-hardy-mod_rails-installation" rel="nofollow noreferrer">Passenger</a> to serve Warehouse via Apache</li> <li>Daily and weekly backups through Slicehost</li> </ul> <p>And that's about it. Not much overhead.</p> <p>Edit: Not trying to sell Slicehost here, so if that's not kosher, let me know!</p> <p>Edit again: James makes an excellent point about hosting proprietary code on a third-party server. Extra care should certainly be taken when selecting a host to do such a thing. Unfortunately, many companies simply don't have the resources to build and manage servers in house, which is where we found ourselves prior to selecting a host for our code.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload