3 ms·
I moved a Go app with 20k users/mo from heroku to render. 1. It took about 1 week due to lack of render documentation for Docker and buildpacks. I posted on th
by aetch 4y ago
I moved a Go app with 20k users/mo from heroku to render.
1. It took about 1 week due to lack of render documentation for Docker and buildpacks. I posted on the render help forum and contacted their support which did respond but were not the most helpful. I ended up finding a single example buildpack file in a render blog post which shed light on how to structure their build system. If I had not found it I dont think I would have been able to get it to work.
2. I don’t have experience with 3rd party deployment frameworks.
3. Learned how to use Docker in order to utilize Renders blueprint feature which would automatically link a redis instance to my hosted app.
4. $0 to $0
Render has a similar interface to Heroku but some missing features and bugs a few of which I’ve found are:
No newline/special character support in environment variables.
Applications cannot get the public hostname from calling the standard call in the programming language’s library like hostname(). Unlike Heroku where a publicaly reachable host is return, render returns an internal hostname is returned instead.
- raunak 4y agoHow was it 0 to 0? Just curious.
- eropple 4y ago(Render hat on) Thanks for the candid feedback! We've been working on our buildpacks-in-Docker support over the last month or so and it's greatly improved, IMO. (I'm biased--I wrote the changes.) So this should be smoother for newcomers. v3 (or the to-be-released v4) of @renderinc/heroku-import should significantly grease the skids for folks looking to make a similar move, and the Render CLI we've got cooking also includes helpers for making ongoing development with buildpacks more reasonable.