# Multiple development instances

**URL:** <https://meta.discourse.org/t/multiple-development-instances/51651>\
**Category:** Development\
**Created:** [October 17, 2016, 6:18pm UTC](https://meta.discourse.org/t/multiple-development-instances/51651 "2016-10-17T18:18:04Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [October 17, 2016, 6:18pm UTC](https://meta.discourse.org/t/multiple-development-instances/51651/1 "2016-10-17T18:18:04Z")

</div>

On my development box, I find myself needing multiple instances. One site I’m importing is on `stable`, others use importers that I am developing. Right now what I do is when switching jobs, I switch branches in git and run a script that does

```bash
RAILS_ENV=development
export RAILS_ENV
RAILS_ENV=development bundle exec rake db:drop db:create db:migrate
bundle exec rake admin:create

```

It’s really annoying when I’ve, say, run an importer that takes several hours and then want to run it again with updated input (and not have to re-import the whole thing).

Is there something different I should be doing? Perhaps I should run separate instances with Vagrant? Contrive to tell Discourse to use a different database for each different job?

Or am I doing the Right Thing?

---

_[View the full topic](https://meta.discourse.org/t/multiple-development-instances/51651)._
