# Keeping rails/dev up to date **URL:** https://meta.discourse.org/t/keeping-rails-dev-up-to-date/94832 **Category:** Development **Created:** [August 15, 2018, 10:50pm UTC](https://meta.discourse.org/t/keeping-rails-dev-up-to-date/94832 "2018-08-15T22:50:53Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![LeoMcA](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leomca/32/87233_2.png) [@LeoMcA](https://meta.discourse.org/u/LeoMcA) #### Post date: [August 16, 2018, 1:35pm UTC](https://meta.discourse.org/t/keeping-rails-dev-up-to-date/94832/5 "2018-08-16T13:35:56Z")
Not on the team, but I use it near daily for all my Discourse core/plugin development work. I rolled my own scripts to help with my particular workflow (which requires pretty regular switching between a vanilla discourse instance, and one with all the bells, whistles and API keys we hang off Discourse within Mozilla): > [@Dev environments scripts](https://meta.discourse.org/t/dev-environments-scripts/66319): > > I’ve been using the [docker scripts bundled with discourse](https://github.com/discourse/discourse/tree/master/bin/docker) for a while, but I’ve found they don’t work particularly well with my want to often switch between different dev instances (for instance, one running tests-passed, one running a branch where I’m developing an awesome new feature, one running a plugin I’m developing, and so on). So, I rolled my own, heavily inspired by the originals: [https://github.com/LeoMcA/discourse-dev-scripts](https://github.com/LeoMcA/discourse-dev-scripts) I’ve been using them for about a week now and they haven… --- _[View the full topic](https://meta.discourse.org/t/keeping-rails-dev-up-to-date/94832)._