Closed
coder/packages
#8Labels
use-caseA novel and interesting way to use CoderA novel and interesting way to use Coder
Description
Deploy Coder to render.com.
- Use Render's managed PostgresDB https://render.com/docs/databases
- Deploy Coder as Web service https://render.com/docs/web-services
-
Set up a template using render terraform providerThey do not have an official terraform provider yet and there are issues with the 3rd party version crash while running
terraform planjackall3n/terraform-provider-render#4 -
Set up a Docker template that uses a remote docker daemonI will do this as a separate issue. how to use remote Docker host #6921
- Set up a Render template repo to deploy to Render with one click
- Move 1-click Render deploy repo to github.com/coder/packages
-
Add a Deploy to Render Button in README.md - Test deployment by using Fly.io starter template
- Write a blog post on github.com/coder/blogs
Metadata
Metadata
Assignees
Labels
use-caseA novel and interesting way to use CoderA novel and interesting way to use Coder
Activity
[-]Coder as render.com web servive[/-][+]Coder as render.com web service[/+]matifali commentedon Mar 30, 2023
Update: There seems like an issue with Render native PostgresDB; using an externally hosted database works fine. I have raised a ticket with Render support.
matifali commentedon Mar 30, 2023
It looks like if we manually create a database first and then deploy the Coder service, all works fine,
But deploying both of them together as a render blueprint fails,
Some logs,
First Deployment,
Onwards retries,
connect to postgres: migrate up: up: Dirty database version 74. Fix and force version.Can this be a Coder issue? As deploying the Coder service manually after the database is created worked fine, @kylecarbs
johnstcn commentedon Mar 30, 2023
It's possible that Render performs some kind of initial migrations on the database deployment (e.g. creating users, databases). This could be a contributing factor for the deadlocks and incomplete database migration. AFAIK we do not run our migrations in a single database transaction?
matifali commentedon Mar 31, 2023
I have tested the deployment with a Fly.io starter template, and everything works fine.
After further investigation, If I create a database manually and then deploy the blueprint, everything works fine. So I guess Render and Coder are trying to run migrations on the database when it is created as part of the render blueprint.
PS. I am still waiting to hear back from render.com support on this.
matifali commentedon Apr 16, 2023
There is an issue with render.com.
On the first service deployment, render initiates two deployments back to back. As the first deployment is interrupted by the 2nd deployment, it leaves the database in a dirty state.
I have raised this issue with Render support, but their email support cycles are slow.