Support Forums

Separate proxies for production and branch deploys?

Is it possible to write a netlify.toml file that specifies one api proxy for production deploys? but a different api proxy for non-production deploys ?

e.g. say I have a production and a staging backend server on google app engine, I’d want the staging deploy on netlify to talk to the staging backend.

Is this possible ?

From the docs:

Certain keys, such as [build] and [[plugins]] but not [[redirects]] or [[headers]] , allow you to set [context] properties based on the kind of deploy. These keys are context-aware .

so I guess the answer is no. Bummer!

The workaround would be to create multiple redirects files in your repo and copy the appropriate one in the build command.