Live data from Hacker News

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

cloudinabottle.org

221–230 of 330 posts

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

#221
This is a great idea and I wish it success. Self-hosting shouldn't be a nightmare of researching and setting up 20 different applications.

Is there something similar in progress for a "tech company tech stack"? As in, rather than trying to assemble your own custom infrastructure by finding an RPC system, permissions/group manager, credential management, storage, database, service discovery, job management, monitoring etc. one "opinionated" stack that you can easily deploy, as long as you're OK accepting their choices, with all these parts already bundled and wired up.

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

#222
What's wrong with coolify? Their ecosystem help start a service with pretty much zero issues. And they also show that maintaining a large amount of click-n-deploy services can't keep up with the releases of all of them. They hit the sweet spot of having everything in a second and maintaining it with ease over time.

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

#223
You don't need docker anymore - it is safe and fast to deploy as systemd services.

And yeah AWS and the likes made for big money spenders with gigantic DevOps teams, not one person handling everything.

We at DollarDeploy were advocating that for 95% of your usage needs you don't need anything but one server and if outgrow it just switch to a bigger one.

I think one cloud in a bottle should be solved differently - apps deployed independently but additional thin layer for MDM - so logins and core data is at one place.

Imagine if your self hosted wordpress, outline, nextcloud and etc share same logins and access levels, bootstrapped with same information without the need to type it for every app.

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

#224
post #50

These guys have been spamming issues in repos trying to promote this project and no disclosure whatsoever that they are associated with the project. https://github.com/search?q=%22cloudinabottle.toml%22&type=i...

It's 11 issues total and by one person, and the project says here in the thread the issue is being addressed. Please put down the metaphorical pitchforks and torches.

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

#226
post #90

One thing that I found LLMs useful for is devops. I had rather good experience using agents to setup and deploy own cloud, Jellyfin and co. I experimented also getting a VPS, just giving the LLM the ssh keys and having at it. It’s pretty good. If the AI stays afloat, then I think the future lies somewhere there. Not too sure about the security side of the things …

> just giving the LLM the ssh keys and having at it. It’s pretty good. I'm mostly fine letting AI write code because its easily auditable and you can follow changes through the Git history. Whereas, it you let the AI go free on a server, you mostly have no idea what it did and where, so it's quite hard to audit and even harder to try and fix things. So, unless relying on a declarative paradigm like NixOS does, I'm no…

While admittedly this can be a bit risky, there's a lot less possible blast radius or thing that can go catastrophically wrong if you give the LLM the ssh keys and sudo access on a KVM VM (or equivalent) that's been created as a blank slate exclusively as its playground. I have a template debian 13 KVM VM that can have its ssh host keys and hostname wiped, other unique per-node things, and duplicated with a basic bash script in a couple of minutes to deploy for home lab testing.

I'm fine with giving a "smart" self hosted LLM like qwen 3.8-flash-next Q8 access to it to do things in opencode.

Don't give it the keys to any castle but give it access to one specific containerized thing...

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

#227
post #12

Earlier quoted context omitted.

> 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.

Precisely. My uncle has been using the builtin Samsung web browser for years on his phone, just because it said "Internet" in the name, and "Chrome" just wasn't a familiar name to him. Most people are like this.

I actually prefer the Samsung browser over Chrome.

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

#229

Earlier quoted context omitted.

> just giving the LLM the ssh keys and having at it. It’s pretty good. I'm mostly fine letting AI write code because its easily auditable and you can follow changes through the Git history. Whereas, it you let the AI go free on a server, you mostly have no idea what it did and where, so it's quite hard to audit and even harder to try and fix things. So, unless relying on a declarative paradigm like NixOS does, I'm no…

While admittedly this can be a bit risky, there's a lot less possible blast radius or thing that can go catastrophically wrong if you give the LLM the ssh keys and sudo access on a KVM VM (or equivalent) that's been created as a blank slate exclusively as its playground. I have a template debian 13 KVM VM that can have its ssh host keys and hostname wiped, other unique per-node things, and duplicated with a basic bas…

  > for home lab testing
So you're talking about a sandbox, not a prod server hosting personal data?

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

#230

The cloud space is absurd, we've sat by for 2 decades while the likes of AWS define every aspect of deployment, auth, even containerisation. Containerisation was supposed to mean host anywhere, literally redeploy a complex set of services and their connections on any cloud provider at the drop of a hat. That is what a f**ing shipping container is, you rock up to any port in the world and the same container is lifted…

If you don't mind me asking a question to better understand your perspective: Are you old enough to have personally experienced and built self-hosted things before the advent of AWS, cloud hosted stuff, or is your text above (which I do not disagree with in any way) the point of view of a person who began working on this stuff in the "cloud-native" era, post-2012 or around then? I'm thinking from the "20 years ago" i…

Yeah, self-hosting is definitely having a come back. Lots of content creators who would have been evangelizing cloud solutions in the past have been instead going into the various self hosting rabbit holes. There is a bit of a pendulum swing. You now have access to so much information and tooling to host your own things, it’s pretty awesome compared to what we had before 2010.

Not sure how much impact that will have for companies, that will likely stay more niche. Companies will still want to delegate much of the effort to a cloud provider, but with pressure to have less lock-in

Post reply on HN