I often write my apps with docker-compose to specify all the docker options. I would render to be able to read my docker-compose file, create all the services, and appropriately coordinate between them, as if I had simply run docker-compose up

Currently if you enable PR previews or preview environments for a service, Render generates a preview for every PR unless you skip it with a title string like [skip render] . Add the ability to instead opt _in_ to previews per-PR, making _no_ preview the default behavior.

Nigeria has over 200 million people and AWS now offers a Local Zone in Lagos, so it would be awesome for reducing latency if a local application serving people all over Nigeria did not have to come all the way from Europe or South Africa. EC2 is available in the Local Zone in Lagos, so perhaps that is enough to offer both Render app servers and a Render Postgres database. The closest that Render.com currently offers is Frankfurt, Germany. Even though AWS has a region in South Africa, it seems that Frankfurt has just as fast of a ping time, so I think the only material difference would be to have the servers running right there in West Africa. Also, the rest of West Africa could benefit - half a billion people. Render would be a pioneer in the region since I think they would have no other competition from a managed app/database cloud platform.

I'd like to get notifications when my memory or CPU usage on my web servers is nearing critical levels. Relatedly, I'd like to get notifications when my web service auto-scales (this might already exist). I'd like the notifications to go to Slack at the very least, and allow me to integrate with Pagerduty as well.

Hello, I have a webapp that uses a Webservice, Worker, Redis, PostgreQL and Flower. All are on paid plans and everything if working fine. I have set the auto build feature off at the moment. So it wont rebuild when any changes are made in GitHub unless I manually instruct it to make the new build. My request is, is there a way to manually instruct all the above services to manually build again at one go? At the moment I need to click build for each of them separately. What would be great is an option to Multi-Deploy many services together. Thanks

Can you add support for Bun applications? i have an express node js app and i want to migrate to Bun. Thank you

For financial services products (UK is a FinTech hub) many agreements require that data be located within the UK.

Hi Render friends! I run a blog about render and when I'm looking for topics to help people with, one of the very common things I see (using node as an example) is that people don't know to include NODE_VERSION as an env variable when they deploy a service (afaict, this happens when using the dashboard to create a service and not a blueprint). Despite the documentation about all the different ways of specifying the runtime version, this oversight happens, as you probably already know, constantly. A thought: if someone selects the Node runtime during service definition, if they don't have a .nvmrc/.node-version/engine defined, it might help to either create a default NODE_VERSION env variable or popup/prompt to tell the user: "Hey! I see you don't have a version defined, here's a link you should know about" to inform them of this pretty essential config.

I am interested in using Render as a free alternative to Heroku or Fly to deploy small Ruby on Rails side projects in the context of a course I teach to beginners at the University of Chicago Booth School of Business. Both Heroku and Fly handle the master.key step automatically, whereas it seems this must be done manually in a few steps on Render. Unfortunately, those steps are challenging for beginners and that may prevent us from using Render in the course. We always try to take the simplest possible route in our early projects to empower beginners with deploying their little toy apps (like this Rock, Paper, Scissors game: https://rps-tr2z.onrender.com ) on the web. Is there any plan to follow a similar model to Fly, Heroku, and Hatchbox to ease the deployment process and avoid some of the complications of setting the master.key and changes needed to the database.yml file (in the case of database-backed apps, but we begin with simple dynamic apps with no database)? It would be great if Render could ease these two Ruby on Rails deployment steps in a fashion somewhat similar to Fly, Heroku, or Hatchbox. Mainly that means: not requiring multiple changes to the app configuration or generating new credentials prior to deployment on Render.