```
The `--demo` flag pulls the [Symfony Demo skeleton](https://github.com/symfony/demo).
The `--upsun` flag automatically generates the Upsun configuration file.
Alternatively, you can deploy an **existing Symfony project**.
To do so, follow these steps:
1. To generate a sensible default Upsun configuration,
run the following command from within the project's directory:
```bash Terminal theme={null}
symfony project:init --upsun
```
This generates the `.upsun/config.yaml` and `php.ini` configuration files.
2. Add and commit your changes:
```bash Terminal theme={null}
git add .upsun/config.yaml php.ini
git commit -m "Add Upsun configuration"
```
## 2. Create your Upsun project
To create a project on Upsun, run the following command from within the project's directory:
```bash Terminal theme={null}
symfony upsun:create --title PROJECT_TITLE --set-remote
```
The `--set-remote` flag sets the new project as the remote for this repository.
Tip
You can link any repository to an existing Upsun project using the following command:
```bash Terminal theme={null}
symfony upsun:set-remote
```
## 3. Deploy your project
To deploy your project, run the following command:
```bash Terminal theme={null}
symfony upsun:deploy
```
During deployment, the logs from the Upsun API are displayed in your terminal so you can monitor progress.
To stop the display of the logs **without interrupting the deployment**,
use `CTRL+C` in your terminal.
To go back to displaying the logs, run `symfony upsun:activity:log`.
Congratulations, your first Symfony app has been deployed on Upsun!
Tip
Now that your app is deployed in production mode,
you can define a custom domain for your live website.
To do so, see how to [set up a custom domain on Upsun](/docs/administration/web/configure-project#domains),
or run the following command:
```bash Terminal theme={null}
symfony upsun:domain:add
```
## 4. Make changes to your project
Now that your project is deployed, you can start making changes to it.
For example, you might want to fix a bug or add a new feature.
In your project, the main branch always represents the production environment.
Other branches are for developing new features, fixing bugs, or updating the infrastructure.
To make changes to your project, follow these steps:
1. Create a new environment (a Git branch) to make changes without impacting production:
```bash Terminal theme={null}
symfony upsun:branch feat-a
```
This command creates a new local `feat-a` Git branch based on the main Git branch,
and activates a related environment on Upsun.
The new environment inherits the data (service data and assets) of its parent environment (the production environment here).
2. Make changes to your project.
For example, if you created a Symfony Demo app,
edit the `templates/default/homepage.html.twig` template and make the following visual changes:
```html {location="templates/default/homepage.html.twig", no-copy="true"} theme={null}
{% block body %}
```
3. Add and commit your changes:
```bash Terminal theme={null}
git commit -a -m "Update text"
```
4. Deploy your changes to the `feat-a` environment:
```bash Terminal theme={null}
symfony upsun:deploy
```
Note that each environment has its own domain name.
To view the domain name of your new environment, run the following command:
```bash Terminal theme={null}
symfony upsun:url --primary
```
5. Iterate by changing the code, committing, and deploying.
When satisfied with your changes, merge them to the main branch, deploy,
and remove the feature branch:
```bash Terminal theme={null}
git checkout main
git merge feat-a
symfony environment:delete feat-a
git branch -d feat-a
symfony upsun:deploy
```
Note that deploying to production is fast because the image built for the `feat-a` environment is reused.
For a long running branch, keep the code up-to-date with the main branch by using `git merge main` or `git rebase main`.
Also, keep the data in sync with the production environment by using `symfony upsun:env:sync`.
## 5. Optional: Use a third-party Git provider
When you choose to use a third-party Git hosting service,
the Upsun Git repository becomes a read-only mirror of the third-party repository.
All your changes take place in the third-party repository.
Add an integration to your existing third-party repository:
* [BitBucket](/docs/integrations/source/bitbucket)
* [GitHub](/docs/integrations/source/github)
* [GitLab](/docs/integrations/source/gitlab)