Hi Keith,
The launch of projects is very exciting. Is there any way to use this as a deployment mechanism? All I can see is the ability to group existing services.
In particular, I’m looking for a clean solution to these issues:
I am not quite following here. Imagine my main repo is called webApp. That’s where all my code lives. When I create a new repo (webAppProd), do I fork all of my code? I can’t imagine that is what you’re actually suggesting, because it would create a lot of overhead in terms of syncing commits between two repos.
Or are you saying that webAppProd knows to pull the source code from webApp? This seems to initially make more sense, but then it creates all sorts of problems around CI/CD. For example…
I saw another thread re staging/production (strapi, not rails) but to me it seemed to completely miss the important point: to be able to a) have different app names for staging-vs-production AND b) be able to safely push new code to staging WITHOUT affecting production.
(Heroku’s pipelines are a superb feature that make this easy… pushes can go to staging until you explicitly promote staging to production.)
What’s the closest one can come to isolated staging/production builds for Rails on Rend…
Hi there!
There are a few approaches to managing services across environments on Render, so first let me see if I can address some of your questions.
There is nothing environment specific in our blueprint etc. So our services are created with the same name. This can cause confusion when reviewing services and logs. I’d rather have services created by the staging blueprint instance have a “-staging” appended etc. Is the best way to achieve this to manually rename the services after they have b…