Ready, Set, Tumble

Awesome, you installed Rails and unpacked the ozimodo tarball into its own directory. We’ll assume that directory is called ozimodo.

  1. Create a database, naming it what you will.
  2. Copy ozimodo/config/database.yml.example to ozimodo/config/database.yml and configure the development section to point at your new database.
  3. Setup the tables using Rails’ wonderful migration feature.
    $ cd ozimodo
    $ rake migrate
  4. Start your development server.
    $ ruby script/server
  5. Open your browser (or a new tab, if you’re hip) and navigate to http://localhost:3000/. That’s it.

Hurrah, Hurrah

One more thing: how to tumble? Surf to http://localhost:3000/admin/ and login. Your username is admin and your very temporary password is changeme.

You may also want to edit some of the options in config/tumble.yml. This file is used to determine various behaviors, such as how many posts to display on your main page and what site name your Atom feed goes by.

Now that your tumblelog is up and running like a well oiled piece of 1940’s machinery, you probably want to begin hacking it to bits. Head on over to our configure page and start learning the zen of making your tumblelog an extension of self.

You’re going to have to change the permissions of the cache and public/feed directories before launching a production app with caching enabled. Check check check the configure page.

Dreamers: Apply Within

If you’re hosting with the Rails-friendly Dreamhost, you may want to check out zenchi’s guide: Howto: Install ozimodo on Dreamhost

Of interest: Joseph DeVivo has noted the above instructions didn’t work for him on Dreamhost. He says:

chmoding my log and tmp directories to 0666 like in the dreamhost tutorial you link 
to actually was breaking my install. chmoding them the way dreamhost 
suggested fixed it:
chmod a+x dispatch.fcgi
chmod -R u+rwX,go-w public log

Joe recommends checking out the Dreamhost wiki’s entry on Ruby on Rails.

rescue TheDamnThingBroke

Oh, something went wrong? Did you check the gigabytes? They’re fine? In that case, you have a few options:

Please include a quick copy/paste of the error you encountered. Our crackerjack team of lab interns will get right on it. While you’re waiting, you may want to check out our configure page.