# Odizy Workflow ### Development You can develop either locally on your Personal Computer or remotely in a muppy managed **Dev Server.** You should create a branch for each new feature (or bugfix) and a merge request that will be used as a collaboration tool. ### Test Servers Each time you commit changes on a **Feature Branch,** muppy will provision or update a **Test Server** depending on parameters defined in **App Definition** (Tab CICD LXC / Test Servers). ### Staging Servers When you are satisfied with your development, you merge your changes (either manually or by closing the Merge Request). This will commit changes on the default branch. Depending on parameters in **App Definition** (Tab CICD LXC / Staging Servers), **Staging Server** can be upgraded automatically or manually. Staging Servers run a copy of the production's database. When you are satisfied of your tests, you should tag your code to make a well identified and easy to install release. ### Production Servers Deployment on Production Servers is manual. For High Availablility Clustered Production Servers, muppy manages deployment on all servers. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.muppy.io/guides/odizy/odizy-workflow.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.