Deploy KBIN on Elest.io and get a working dedicated instance in less than 3 minutes. You can Relax knowing that we are taking care for you of install, configuration, encryption, backups, software updates, os upgrades, live monitoring, alerts, live migrations without downtime ... and more! Kbin is a ...
Hey dear community, we just launched today our fully managed hosting service of KBIN
We offer to do Deployment / Security / SSL / DNS / SMTP / Monitoring / Alerts / Backups / Automated updates / Handle migrations / Fully automated but with Human support :)
We deploy each instance on a dedicated VM, and we provide full root access as well if you want to customize anything.
I just tried this, but it doesn't seem like it's really ready for anything but a basic test environment.
When your system creates the service, it does so with the default elestio domain and there is no way to change it from within KBin, therefore your are stuck with a huge security hole and a nonsense domain name that's impossible for people to remember.
While you can indeed use your own domain name to resolve it, it doesn't appear that the domain is editable once KBin is setup (which is done automatically, and understandably on the federation side, you can't have the domain name changing)... so when you set up a KBin on Elestio, you are forever suck with "kbin-????-u5400.vm.elestio.app" as your server name in the Fediverse, which sucks and is really a non-starter.
I don't want to be @HamSwagwich@kbin-mynewkbininstance-u5400.vm.elestio.app
This appears to have the added effect of making it impossible to use Cloudflare as your proxy, since you get a bunch of 301 redirects bouncing between your resolved domain and the elestio domain, since KBin thinks it's name is the elastio domain and rediredts you, then our browser thinks it's going to the resolved domain and redirects you. Boing boing boing