Render is the recommended hosting platform for SteelWorks, supporting Docker-based deployments and managed PostgreSQL out of the box. The SteelWorks CI pipeline triggers a Render deploy hook automatically whenever a push toDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/kishnahai0806/SteelWorks/llms.txt
Use this file to discover all available pages before exploring further.
main passes all tests.
Deploy the web service
Push your code to GitHub
Ensure your latest changes are committed and pushed to the
main branch of your GitHub repository. The Render deployment pulls from this branch.Create a new Web Service on Render
Log in to the Render dashboard and click New → Web Service.
Connect your GitHub repository
Select your GitHub account, then choose the SteelWorks repository. Set the branch to
main.Set Language to Docker
Under the Language selector, choose Docker. Render will detect the
Dockerfile at the repository root and use it to build and run the service.Add environment variables
Scroll to the Environment Variables section and add the following:
| Key | Value |
|---|---|
DATABASE_URL | Your Render managed PostgreSQL connection string (see Managed PostgreSQL below) |
SENTRY_DSN | Your Sentry DSN — optional, omit entirely if not using Sentry |
Deploy the service
Click Deploy Web Service. Render will build the Docker image, push it to its internal registry, and start the container.
Managed PostgreSQL
SteelWorks requires a PostgreSQL database. Render provides a managed PostgreSQL service that integrates cleanly with web services:- In the Render dashboard click New → PostgreSQL.
- Choose a name, region, and plan, then click Create Database.
- Once the database is provisioned, open its detail page and copy the Internal Database URL (use the internal URL for services in the same Render region to avoid egress fees).
- Paste that URL as the value of the
DATABASE_URLenvironment variable on your web service.
The Docker image listens on Render’s
PORT environment variable. Render sets PORT automatically for every web service; the Dockerfile reads it via ${PORT} in the CMD instruction, so no manual port configuration is required.