feat: public domain service #309
Description
This is likely an issue for Infinite itself rather than the OS, but, let's keep here for tracking.
Currently to deploy OS you must provide a PRIMARY_VHOST. That's friction. Users don't want friction.
WHAT IF we had an API that OS can call to get its unique domain, example: os123.something.tld.
That way, we could ask, optionally of course, for a fully qualified domain name (FQDN) during setup.
If the user doesn't want to, no problemo, keep using your something.tld subdomain.
We'd have a NGINX cluster on the something.tld, a wildcard SSL and a wildcard DNS record so exposing an OS to the internet would be pretty straightforward. We already have a getPublicIp method on OS code. OS could POST into an API that handles the registration process behind the scenes.
Sure, there are risks. People may use the temp domain for malware. We could and are likely to receive DDoS on that domain. Nothing that a proper ToS can't handle. We could have a generous rate limit there to prevent abuse and honestly, that service is not meant for production. If someone is heavily using it, that someone is on the wrong.
That would likely allow us to have a simple curl | bash kind of way to deploy an OS for testing. (: