GitHub repository hosting
Deploy applications from GitHub
Turn a source repository into a running application without maintaining the hosting server yourself. Connect GitHub, select the code to build and keep application configuration in your Polyer project.
Configuration checklist
- Repository access and branch: authorize the intended repository and choose the branch that contains the release you want.
- Build context and commands: confirm the application directory, build settings and runtime start command match your project.
- Runtime variables: configure required credentials and environment-specific values without putting secrets into browser code.
- Networking and data: check the listening port, domain configuration, database references and any persistent volume paths.
From configuration to deployment
Connect your repository
Sign in to Polyer, open a project and connect the GitHub repository you are authorized to deploy.
Choose the build and environment
Select the repository branch and target environment. Review the application's directory, build settings and start command.
Review service configuration
Set required variables, resource settings and connections to other services. Review staged changes before submitting deployment.
Inspect the release
Read deployment logs and runtime output. Test the application's endpoint and database connection, then complete any required initialization.
Keep the service running
- For each release, confirm the selected branch and target environment. Inspect the deployment record and use the service's redeploy controls when a new deployment is needed.
- Treat application migrations and external credentials as part of release preparation. A successful container start alone does not confirm the application workflow is correct.
- Keep production and development configuration separate. Use environment and service logs to diagnose build failures, startup errors and connection problems.
Questions before deployment
How do I deploy one application from a monorepo?
Choose the root directory for that service, then check that its build can access the required manifests, lockfiles and shared packages. A Dockerfile path selects the file to build; it does not add files outside the build context. For example, if an apps/web build needs packages/shared, choose a context that includes both and adjust the Dockerfile accordingly.
Why does changing the build command not affect my Dockerfile build?
The build-command setting applies to Railpack builds. When the service builds with a Dockerfile, edit the build steps in that Dockerfile instead. Check the deployment log to confirm which builder ran. If your CI already produces the release image, Docker image hosting lets you deploy that image without rebuilding the repository.
Can I deploy a private GitHub repository?
Repository access must be granted through the GitHub integration. Review the integration's access to your organization and repository before configuring the service.
Does changing a branch change my production environment?
The branch selects the application's code source; the named environment selects where its services run. Review both settings and pending changes before deploying.
What should I check when a GitHub deployment fails?
Start with deployment logs, repository access, build context and commands. For runtime failures, inspect the start command, variables, listening port and dependent service connections.
Configure in your workspace
Signing in opens your workspace. Resources are created only after you submit the deployment configuration.