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.
It sounds to me like the bar to deploy had been discouraging some from deploying instances.. It will be interesting to see what happens with the instance count after this.
Normally I would check out source, build and deploy, but the docs suggest an entirely manual deployment or build/deploy via docker compose.
The issue I hit was figuring out what had failed in the process, I would have preferred a CI guide to produce working docker images and a CD guide for deploying the docker images.
The reason I gave up is there aren't any release markers, I tried with develop and main and couldn't figure out if it was me or the branches weren't in a buildable state.
I don't expect the a release to be perfect just an indicator that a working product was created at this point.
I'd love to deploy my own instance of either kbin or lemmy, but a ten buck a month price tag is a bit steep (imho). I'll wait until there are better guides for hosting my own.
off-topic, hi ernest, is there a way to contact ppl on kbin somhow? private messages?
now to my question: i see that you own a lot of magazines (mostly auto-created added), now if i create something with a similiar name on /kbin itself, am i allowed to keep it? since the one i see is on a different instance?
i did read the kbin-core/wiki/ but couldn't find anything about it. edit: if there is.. can you please quote / link to it?
That depends on the size of the insurance: keep in mind that, for the most part, kbin is just a list of txt files. 2gb of ram sounds like a lot less than it is since people are used to desktops that have all sorts of additional stuff running on the side which pushes up the overall system consumption
I think a bigger factor may be media uploads. Today, my understanding -- from hearing about a single case of a user in the UAE who couldn't access media after the UAE blocked a Lemmy instance, not from running an instance myself -- is that the instance to which they are uploaded serves them. That is, unlike with messages, media isn't propagated to other instances. I have no idea if support for media uploads is a toggleable flag or what, but if one intends to permit open signups and have users that upload a bunch of large media, it could consume that storage space. I don't know if Elestio presently supports dynamically upgrading a plan to get more storage.
For that price point and management, I sure hope that helps kbin easier for others to get more instances going. Even if folks have a 1-5 user instance $10/mo is great!
@jbenguira What's the support for migrating out your data. Because this could be a great way to get a new instance going, but it would be great to have the option to e.g. move to a self-hosted fork down the line.
Hey @brecht, we provide full root access and tools like VSCode in the browser, file explorer, SFTP access so you can move your files & db. We do plan to have an automated migration system later. But for now KBIN is still young
It's definitely the kind of things we do! We have agreements with several open source software authors and we do give them parts of the profits. FYI we also contribute in code to some projects
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
@jbenguira after fixing the image thing, my main feedback is that it doesn't run that well on the single core 2Gb ram option. It does run, but pretty slowly.
The dual core 4Gb ram version seems to run reasonably well, but I haven't put it under proper load yet.
I just want to point out to anyone interested in kbin+docker stuff that OP has published their Docker image of Kbin to Docker Hub. https://hub.docker.com/r/elestio/kbin
I actually ran across this image before I saw this post.