# What is the latest recommended workflow for local development? (Ubuntu 16.04)

**URL:** https://meta.discourse.org/t/what-is-the-latest-recommended-workflow-for-local-development-ubuntu-16-04/71213
**Category:** Development
**Created:** [2 באוקטובר,‏ 2017,‏ 10:08pm UTC](https://meta.discourse.org/t/what-is-the-latest-recommended-workflow-for-local-development-ubuntu-16-04/71213 "2017-10-02T22:08:26Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [2 באוקטובר,‏ 2017,‏ 11:13pm UTC](https://meta.discourse.org/t/what-is-the-latest-recommended-workflow-for-local-development-ubuntu-16-04/71213/2 "2017-10-02T23:13:48Z")

</div>

Right. You want the [Install Discourse on Ubuntu or Debian for Development](https://meta.discourse.org/t/beginners-guide-to-install-discourse-on-ubuntu-for-development/14727)

> [@j127](#):
>
> what is the general, recommended workflow for syncing code and data with the live, production Docker install?

I’ve been doing this a year and I mostly don’t know. Here are some things I recommend:

- Always work on a branch
- `git pull upstream master` to re-sync with, uh, upstream

> [@j127](#):
>
> what is the general, recommended workflow for syncing code and data with the live, production Docker install?

Oh. Perhaps this is what you want to know: To sync with production you make plugins. Create a repo for each and symlink it to the plugins directory.

You don’t ever, ever, ever, run your forked code in development.

---

_[View the full topic](https://meta.discourse.org/t/what-is-the-latest-recommended-workflow-for-local-development-ubuntu-16-04/71213)._