# Plugin development workflow w/ remote dev server

**URL:** <https://meta.discourse.org/t/plugin-development-workflow-w-remote-dev-server/80267>\
**Category:** Development\
**Created:** [February 10, 2018, 4:12pm UTC](https://meta.discourse.org/t/plugin-development-workflow-w-remote-dev-server/80267 "2018-02-10T16:12:21Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [February 21, 2018, 4:56pm UTC](https://meta.discourse.org/t/plugin-development-workflow-w-remote-dev-server/80267/7 "2018-02-21T16:56:30Z")

</div>

For most stuff, I’m using [atom.io](http://atom.io) with the [Sunsetting Atom - The GitHub Blog](https://atom.io/packages/remote-sync) package together with a DigitalOcean box. Works like a charm and you can have it auto-save everything to remote. You can specify exclude directories so it won’t be spending efforts on your test and vendor directories.

Specifically for Discourse plugin development, I’ve been using [https://janitor.technology/](https://janitor.technology/) since a few weeks.

---

_[View the full topic](https://meta.discourse.org/t/plugin-development-workflow-w-remote-dev-server/80267)._