News for hackers. Stuff that matters.
Re:ReleaseHub Environments as a Service Gets 2.7M Seed from ... by abatilo on Thursday April 29, 2021 @11:49AM (#26982714)
Couldn't you just use something like Heroku then?
Re:ReleaseHub Environments as a Service Gets 2.7M Seed from ... by nrmitchi on Thursday April 29, 2021 @12:51PM (#26983524)
Heroku (and pretty much every PaaS) has features like this built in, and they tend to work really well... assuming you're using Heroku.

If you're using a PaaS that offers this, you (99.9% of the time) shouldn't look elsewhere. Just use their offering.

If you're not using an explicit PaaS, rebuilding this functionality yourself can end up being a never-ending rabbit hole.

Re:ReleaseHub Environments as a Service Gets 2.7M Seed from ... by erik_landerholm on Thursday April 29, 2021 @12:10PM (#26982976)
You can use heroku, but as your app grows in complexity, (say static javascript frontend, backend, queue, and maybe a few AWS or GCP native services) you have to stitch something together with heroku + vercel + ?? + can't use RDS, but wish i could. :)

Heroku review apps are analogous to our ephemeral environments, but we can deal with much more complicated environments, which reduces complexity in your CI/CD platform, production deployments or on-premise deployments if needed.

Re:ReleaseHub Environments as a Service Gets 2.7M Seed from ... by ccleve on Thursday April 29, 2021 @11:51AM (#26982732)
Too expensive for larger deployments.
Re:ReleaseHub Environments as a Service Gets 2.7M Seed from ... by koblinski on Thursday April 29, 2021 @12:00PM (#26982859)
Also Heroku deployments are a PITA when you want fully (or partially) isolated environments but also work with a lot of microservices.
Re:ReleaseHub Environments as a Service Gets 2.7M Seed from ... by fnord77 on Thursday April 29, 2021 @12:35PM (#26983292)
and this new thing won't be?