# 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:** 1

<div class="post-metadata">

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

</div>

Thanks for the guides, I think I have the basics to get me started with Plugin dev.

Wanted to ask about whether its worth having an IDE for plugin development?

Secondly, I’m hosting my dev server on a remote cloud VPS because my laptop is too slow to run a VM locally at reasonable speed, [as suggested](https://meta.discourse.org/t/discourse-dev-server-using-a-rock64/79378/2) by @Hector

In this setup, whats the best workflow?

Can I use some protocol to connect to the remote VPS files directly within an IDE running locally, or should I clone locally, edit, commit, then separately download from source control to server and restart to test?

Apologies for any newbieness!

---

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