# Discourse as Your First Rails App

**URL:** https://meta.discourse.org/t/discourse-as-your-first-rails-app/5751
**Category:** Blog
**Created:** [9. April 2013 um 23:08 UTC](https://meta.discourse.org/t/discourse-as-your-first-rails-app/5751 "2013-04-09T23:08:33Z")
**Posts on this page:** 1
**Showing post:** 115

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [15. Oktober 2015 um 19:05 UTC](https://meta.discourse.org/t/discourse-as-your-first-rails-app/5751/115 "2015-10-15T19:05:07Z")

</div>

@Thrillberg @ptgamr

Maybe these will help

> [@Vagrant based server failing on db:migrate](https://meta.discourse.org/t/vagrant-based-server-failing-on-db-migrate/34566):
>
> I just ran through the instructions in the developer guide to install an environment using a virtual machine with vagrant I found [here](https://github.com/discourse/discourse/blob/master/docs/VAGRANT.md). In my newly created instance, after a bundle update, updating the database with rake like so bundle exec rake db:migrate generates the following error: rake aborted! NameError: uninitialized constant SiteSettings::DbProvider::RailsMultisite /vagrant/lib/site\_settings/db\_provider.rb:52:in `current_site' /vagrant/lib/site_setting_extension.rb:44:in `current' /…

[https://meta.discourse.org/t/upgrade-failed-after-the-recent-todays-commits-cannot-load-such-file-rails-multisite/34396?u=mittineague](https://meta.discourse.org/t/upgrade-failed-after-the-recent-todays-commits-cannot-load-such-file-rails-multisite/34396)

---

_[View the full topic](https://meta.discourse.org/t/discourse-as-your-first-rails-app/5751)._