> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/source-control-environments/setup.md).

# Set up source control in Duaer

Link Duaer to your Git provider.
## Remote URL

Enter the Git remote in source-control settings. Push and pull from this instance both use that remote. Development and production should be two uses of the same remote, not two unrelated repositories.

## Set up a deploy key <a href="#step-3-set-up-a-deploy-key" id="step-3-set-up-a-deploy-key"></a>

1. Duaer shows a deploy public key.
2. Add it as a deploy key on the Git host with the read or write access this instance needs.

The product link about setting up a deploy key opens this step. If the public key is missing, or present without write access, the remote rejects the push. A different instance needs its own key. Do not reuse a private key on another machine.
## Questions

### Where do you add the deploy key?

After you connect the remote, add the deploy public key Duaer shows on the Git host. The “set up a deploy key” link opens this step. Without it, pull and push are rejected.

