Hacker News new | ask | show | jobs
by cdubzzz 1387 days ago
Well shit. After the Heroku Dashboard issues I moved my OSS project demo instances and PR reviews process to Fly.io, then Render.com, then Railway, then back to Heroku because it was the only one that had a truly free and well integrated process.

Sigh.
1 comments
anurag 1387 days ago
What would make the process more integrated on Render?
link
cdubzzz 1387 days ago
I should have taken more notes on this...

I think my primary issue with Render.com was the shared database for PR previews. The way I am setup on Heroku is I run a demo instance that resets hourly and build PR reviews from the Heroku Dashboard when necessary. All with no cost. The shared database makes the PR reviews effectively useless because of the need for the ongoing demo database.

I was also turned off by the default service plan being a non-free one. I got a surprise bill in my first month of testing this because I had not specified the free plan in the service configurations.

Also one of the weirdly nice things from Heroku was the ability to run cron jobs for free. Lacking that I had to create a GitHub Action to handle resetting the demo data every few hours. Just an additional pain.

link
anurag 1383 days ago
All valid points. I'm not sure this is what you're looking for, but we have Preview Environments[1] where every PR can have its own database. Happy to chat more over email (in profile).

[1] https://render.com/docs/preview-environments

link