Jon Koops
956133bf45
Node.js 22.21.0+ natively supports HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables via NODE_USE_ENV_PROXY, eliminating the need for undici and global-agent workarounds. This also works with node-fetch and cross-fetch since they delegate to node:http/node:https without overriding the HTTP agent. Add a new corporate proxy tutorial under docs/ with the recommended approach and update the legacy guide in contrib/ to point to it. Update proxy references in the deployment, keeping-backstage-updated, and TechDocs CLI docs to mention NODE_USE_ENV_PROXY. Signed-off-by: Jon Koops <jonkoops@gmail.com>
1.3 KiB
id, title, sidebar_label, description
| id | title | sidebar_label | description |
|---|---|---|---|
| index | Deploying Backstage | Overview | Packaging Backstage and deploying to production |
Backstage provides tooling to build Docker images, but can be deployed with or without Docker on many different infrastructures. The best way to deploy Backstage is in the same way you deploy other software at your organization.
This documentation shows common examples that may be useful when deploying Backstage for the first time, or for those without established deployment practices.
:::note Note
The easiest way to explore Backstage is to visit the live demo site.
:::
At Spotify, we deploy software generally by:
- Building a Docker image
- Storing the Docker image on a container registry
- Referencing the image in a Kubernetes Deployment YAML
- Applying that Deployment to a Kubernetes cluster
This method is covered in Building a Docker image and Deploying with Kubernetes.
There are many ways to deploy Backstage! You can find more examples in the community contributed guides found here.
If you need to run Backstage behind a corporate proxy, see the corporate proxy guide.