Repository navigation
Support Single-Drone Scenario, with Wildcard Dns #279
Description
Hi there,
This project looks like the perfect foundation for our use case:
We develop a webapp in .NET/Angular and want to spin up a backend (single docker container) for each developer when they click a link in the CI build output of our project (e.g. to Preview a PullRequest).
We want to host plane on our azure infrastructure, but we don't need multiple drones right now.
Is there a way to disable the DNS stuff and just create a single drone and a scheduler?
We would then create a wildcard dns to map *.test-our-webapp.com => The-One-And-Only-Drone-IP. We really don't want to host multiple services (dns, scheduler, drone) for this, because we need to keep our cloud cost at a minimum....
Thanks in advance
Activity
paulgb commentedon Dec 5, 2022
Hi Timo,
Yes, your use case should work.
[dns]line from the toml file passed to the controller (e.g. this line).You'll still need three processes (nats server, controller, and drone), but they can all be run on the same machine (I recommend using Docker Compose for this).
Hope that helps, happy to elaborate more if that would be helpful.
t-moe commentedon Dec 7, 2022
Hi Paul,
Thank you for fast response!
It works! Awesome!!
I've removed the firefox and dnsmasq containers from the docker-compose sample configuration, exposed the nats and drone https port to get the desired use case working. I've also built a small nodejs app that uses the NATS api to spawn our containers. Next, I will be looking at the authentication part...
paulgb commentedon Dec 7, 2022
Awesome, glad that worked! I think we should provide an example like this out of the box, so I've opened #283.