Deployments · 8 min read · Updated August 2026
Deploy a GitHub repository to Azure Container Apps
Short answer
Azure Container Apps is a good fit when your app can run as a container and your team wants Azure to handle the surrounding platform concerns. Start with one service, external ingress only when necessary, and a clear environment-variable strategy.
Choose the right path
| Best for | Stateless web apps, APIs, workers, and containerized services that do not need direct server administration. |
|---|---|
| Bring | A GitHub repository, an Azure subscription, a production environment file, and a plan for the database and file storage. |
| Do not use it for | A workload that depends on untracked server changes, local disk as durable storage, or software that cannot be containerized. |
Walkthrough
- 01
Make the repository deployable
Ensure the app can build from a Dockerfile or from supported source. The service must listen on the configured port and read production configuration from environment variables, not a committed local file.
- 02
Create the Azure deployment boundary
Use a dedicated resource group and choose the region nearest to users and data dependencies. This boundary makes cost, access, and cleanup easier to understand.
- 03
Deploy the first revision
Azure documents az containerapp up for deploying from a repository, local source, or an existing image. Use it to create the initial app, then verify the generated ingress URL before pointing a custom domain at it.
- 04
Move secrets and state outside the container
Store secrets in platform configuration and use a managed database or an intentionally operated database. Never rely on a container filesystem for data that must survive a revision change.
- 05
Create the release check
Every deploy should include a health endpoint, a migration strategy, logs that can be searched, and a rollback decision. A green build is not enough if the application cannot connect to its database.
Before calling it production-ready
- Repository builds from a clean checkout
- Configured target port and health endpoint
- Environment variables set outside Git
- Database backup and migration plan
- Custom domain tested after the default URL works
Questions founders ask
Do I need a Dockerfile?
Not always. Microsoft documents repository deployment paths for projects with and without a Dockerfile. A Dockerfile is still valuable when you need a fully repeatable runtime.
Will every GitHub push deploy?
The repository workflow can create a GitHub Actions pipeline for build and deploy. Review the generated workflow, its secrets, and branch trigger before relying on it.
Where should PostgreSQL run?
Use a managed database or operate one deliberately. Keep its credentials, backup process, and network access separate from application deployment.
Where RepoAssistant fits
We help startup teams turn the right path into a working setup: review the current infrastructure, use available Azure credits deliberately, deploy the app, and leave the team with ownership and handover notes.