1. Downloading and Bootstrapping Warehouse

   After purchasing a Warehouse license, a link will be provided to download the latest release as a tar.gz file. The easiest way to deploy this is to unzip on your server and configure it with either Mongrel or FCGI (depending on your host).

   Once it's uncompressed on your server run rake warehouse:bootstrap, and follow along. This will help you setup your database and a few other initialization routines. Note: MySQL is the only supported database, but support for other platforms will come later. Assuming the ruby/subversion bindings have been properly installed, this task will now create your database tables. Note: Warehouse won't create your database, you will need to do that much before beginning.

2. Registering Warehouse

   Now that your database has been created, it's time to register your copy of warehouse. Start rails (script/server is fine) in production mode, and visit the homepage. You will be sent to /install to fill out the installation form.

   Domain

   This is the main domain that this Warehouse instance runs from. In the screenshot example, svn.activereload.net is used to set site-wide settings and view Changeset Activity from multiple repositories. Each repository gets a subdomain, such as lighthouse.svn.activereload.net, where members can interact with only that repository.

   Repository Name

   This just describes your repository. The installer will automatically create a subdomain, converting a title like "Lighthouse" or "Active Reload" to "lighthouse" and "active-reload". Tip: it helps to keep things consistent if you are managing multiple repositories. Keep them in the same directory, name your repository subdomains after them, etc.

   License

   This is where you enter your license key from your purchase. A valid key is required to install Warehouse.

   Absolute Path to Repository

   This is the server path to the subversion repository, such as /var/repos/active-reload.

   OpenID

   An OpenID profile is required for the initial Warehouse admin users.

   After filling in this information and installing, you will be sent to your OpenID server to authenticate, and then you can begin synchronizing.

3. Synchronizing Your Repository

   Synchronizing is the time-consuming process where Warehouse seeds the database with the basic activity information from subversion. Just after installing, you can conveniently synchronize from the web and watch the progress bar. This isn't required, but the Activity section will remain bare until the process is complete.

   You can also run a command from the console. This is a bit faster, and is preferred for large repositories with over 1000 changesets. You simply run rake warehouse:sync RAILS_ENV=production to sync all repositories, or you can specify the subdomain: rake warehouse:sync REPO=lighthouse RAILS_ENV=production.

At this point, installation is complete. However, if you want Warehouse to keep track of future changesets, you need to setup a subversion post-commit hook.

Keep in mind you might need to restart Warehouse after installation or any time the admin settings or plugins are modified, especially if you are running with multiple mongrel processes.

Thanks for using Warehouse!

• Installing and Registering Warehouse

• Installing Warehouse on Dreamhost

• Installing the Ruby Subversion Bindings

We are Active Reload

We focus on building simple tools with beautiful interfaces that help developers and designers do their job.

Need a Bug Tracker?

For complete serenity for you and your team, you should try Lighthouse, our bug tracking and project management application we poured just as much love into as Warehouse.

Hosting by Engine Yard

We've been rocking with Engine Yard since day one of our little company. If sysadmins were ninjas, these guys would kick your ass.