The Deployer documentation
Creating & deploying a project

Build location

The build location decides where your app's image is built. You only need to change it when your company's package repository can't be reached from the internet, or only accepts connections from IP addresses it knows.

Where to find it

Open your project. On its dashboard, the Build settings card has a Build location row. Click Change to open its panel. You need permission to change the project's settings.

The two choices

  • Managed by The Deployer (the default). Builds run in a managed build service with internet access. This works for any repository that is reachable on the internet, and for projects with no package repository at all.
  • Inside my network. Builds run in a network you choose in your own cloud account. Use this when your package repository is private: on a private address, behind a VPN, or connected through a private link from your cloud provider.

Choosing your network

When you pick Inside my network, choose a Network and one or more Private subnets from your cloud account. These lists fill in from the cloud connection the project uses.

Choosing a network from your cloud account isn't available for every cloud and architecture yet. If the lists are empty, the panel says so, and you can keep building with Managed by The Deployer in the meantime.

Where your cloud provider still offers the network build feature as a preview, the option shows a Preview badge. Preview features work, but your cloud provider may change them or limit them to some regions.

A fixed IP address

If your repository only accepts connections from listed IP addresses, tick My repository only accepts listed IP addresses. This adds a gateway with one fixed outgoing IP address to the network you chose. Once it's set up, the panel and the project page show the IP to add to your repository's allowlist.

Costs

Building inside your network, and especially a fixed IP, creates resources in your cloud account that your cloud provider bills you for directly. The Deployer never adds them without asking: the panel shows what will be created, and you have to tick a confirmation before you can save. The button then reads Confirm cost and redeploy.

Switching back to Managed by The Deployer doesn't add any cost.

Checking the connection

After you apply a network, click Check from this network. The Deployer runs a quick check from inside that network and confirms it reached your repository: the name resolved, the certificate was trusted and the token worked. If a step fails, the result names the step so you know what to fix.

Applying the change

Like the other build settings, the panel ends with Apply on next deploy and Redeploy now. Your app keeps running on its current version until the new build passes its health check. You can switch back any time; that also takes effect on the next deploy.

Related