# Understanding the development/deployment process

**URL:** https://meta.discourse.org/t/understanding-the-development-deployment-process/92669
**Category:** Development
**Created:** [July 18, 2018, 6:59pm UTC](https://meta.discourse.org/t/understanding-the-development-deployment-process/92669 "2018-07-18T18:59:55Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [July 18, 2018, 7:49pm UTC](https://meta.discourse.org/t/understanding-the-development-deployment-process/92669/2 "2018-07-18T19:49:24Z")

</div>

1. Yes

2. Themes live in their own git repo. So you can create a central theme repo in GitHub and everyone can work on that, test locally and push changes upstream. Check [Structure of themes and theme components](https://meta.discourse.org/t/how-to-develop-custom-themes/60848)

3. In normal instance usage, you almost never change the app.yml. However, nothing stops you from putting that in it’s own repo and symlinking the file where launcher expects it.

---

_[View the full topic](https://meta.discourse.org/t/understanding-the-development-deployment-process/92669)._