Live data from Hacker News

Cloud in a Bottle: making self-hosting accessible to everyone

cloudinabottle.org

11–20 of 330 posts

Re: Cloud in a Bottle: making self-hosting accessible to everyone

#11
post #2

> In the pre-cloud days, open source worked - authors distributed their software, and everyone "hosted" it for themselves (i.e. ran it on their own PC) This is just rose tinted vision of the past. None of the software of the past had the capability, reliability or robustness of modern sass.

I'm rather baffled by that statement, with docker its...as easy as its ever been

Docker was first released 11 years after AWS though, so I'm not really sure that it counts as "pre-cloud".

Regardless, I agree that Docker has made self-hosting stuff pretty easy, and arguably even easier than it was in the pre-cloud days.

Re: Cloud in a Bottle: making self-hosting accessible to everyone

#12
post #6

I think the time for this space is here. The appetite to depart from subscriptions and loaning your personal data to ad/ai companies is stronger than ever. Currently, a lot of this space is docker compose based and simply inaccessible to so many who may otherwise be interested. Whether or not it's this project or another, I hope something gathers enough steam soon to truly break the barriers to entry.

> The appetite to depart from subscriptions and loaning your personal data to ad/ai companies is stronger than ever.

Only on HN, the general public don't care, they don't even know the name of their web browser.

Re: Cloud in a Bottle: making self-hosting accessible to everyone

#13
post #8

"We (Imbue, the company I work for) also offer a managed version, which I think is really important to making this widely accessible - and it gives us a straightforward business model to support the project." Looking at your hosted page, I see no reference to backups. I see in your docs reference to backup, but you should definitely offer some sort of turnkey, appropriately-marked-up backup solution. Configuration di…

(author here) Thanks for flagging, I should make this more clear. Our managed instances have pretty small disks (~50GB), but there's a way to link a S3 bucket to your instance to use for bulk data storage. Apps that store bulk data (like immich/jellyfin) should automatically put it in the "archive data tier" which can be configured to go into this S3 bucket instead of local storage. We're planning to make this (and backups) an auto-configured part of our managed instances - billed separately (so you pay for just the additional storage you use; cloudflare R2 (S3 compatible) at-cost is like $15/TB/mo so it should be in that neighborhood).

See docs on how this works: https://cloudinabottle.org/docs/how_it_works/data.html#the-a...

Re: Cloud in a Bottle: making self-hosting accessible to everyone

#15
post #6

I think the time for this space is here. The appetite to depart from subscriptions and loaning your personal data to ad/ai companies is stronger than ever. Currently, a lot of this space is docker compose based and simply inaccessible to so many who may otherwise be interested. Whether or not it's this project or another, I hope something gathers enough steam soon to truly break the barriers to entry.

But this is a company building on AI.

Re: Cloud in a Bottle: making self-hosting accessible to everyone

#17
>At the core, it's just an Ubuntu machine with a web server that hosts a dashboard and routes HTTP(s) requests to containerized apps.

So no fail over/redundancy? I think at minimum it should be two machines, so one can break. That is one of the important features of cloud applications as far as I'm concerned.

You don't have to deal with the problem of a single computer breaking.

Re: Cloud in a Bottle: making self-hosting accessible to everyone

#18

>At the core, it's just an Ubuntu machine with a web server that hosts a dashboard and routes HTTP(s) requests to containerized apps. So no fail over/redundancy? I think at minimum it should be two machines, so one can break. That is one of the important features of cloud applications as far as I'm concerned. You don't have to deal with the problem of a single computer breaking.

This also adds a lot of moving parts and failure modes. For self-hosting I’d rather have downtime on a simple system that’s easy to fix rather than a complex setup that stays up but needs more maintenance when some component fails.
Post reply on HN