Top
Best
New

Posted by zplizzi 16 hours ago

Cloud in a Bottle: making self-hosting accessible to everyone(cloudinabottle.org)
531 points | 263 commentspage 10
hnacobsxph 4 hours ago|
[flagged]
devkakadiya 8 hours ago||
[dead]
devkakadiya 8 hours ago||
[dead]
earth-tattoo 6 hours ago||
[flagged]
EGreg 16 hours ago||
How do I reach out to you? We're building something that you might want to be a part of. (The "Safebox" comes with all the software you need, and you can just clone its AMI on AWS etc.) Would love to have a conversation.

If you want to message me, find my email on https://qbix.com/about

0c3ca83 16 hours ago||
It's weird seeing someone trying to promote self-hosting, while building everything with Claude.
ravenstine 16 hours ago||
Does self-hosting need to be all or nothing?
Forgeties79 15 hours ago||
I didn’t get that from their comment at all
senectus1 14 hours ago|||
AI is a tool. the use of this tool to deliver something unrelated is... unrelated
majorchord 15 hours ago||
"It's weird seeing someone pay for food when they have a garden at home."
zdragnar 14 hours ago||
LLMs can be self hosted though. Using Claude to build a self hosting platform is a bit like telling people they should be vegan while you're eating a bacon sandwich.
bitpush 16 hours ago||
> 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.

marknsikora 15 hours ago||
Yea. When people talk about how simple things were in the past, I think they oblivious to the fact we were all writing out X11 configs by hand and having them break in all sort of strange and interesting ways. Open source has always been very "I gave it to you for free, I'm not going to hold your hand".
wizzwizz4 13 hours ago||
I've written X configs by hand, but only to get a few extra pixels of overscan. I've never needed to do this. My experience has always been that things just work. The UI has never been great, in that I need more explanation than the built-in manuals provide – unlike, say, Windows 95, where you can learn everything you need to know by clicking around – but it's not hard to avoid breaking things, and it's not that hard to learn to do new stuff if you have a good book (or, lately, blog post) to consult.
yoz-y 13 hours ago||
The amount of sleepless nights because an update broke sound, video or networking on Linux is uncountable. It was fun though.
wookmaster 16 hours ago|||
I'm rather baffled by that statement, with docker its...as easy as its ever been
lmz 16 hours ago|||
"capability, reliability or robustness" has nothing to do with ease.
gucci-on-fleek 16 hours ago|||
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.

em-bee 16 hours ago||
that statement does not make any claims about capability, reliability or robustness. the claims are rather cost and independence.
Jnr 7 hours ago|
In the age of LLM agents, still going for Docker/Podmam on anything besides local development box seems like a weird choice.

Docker has poor tooling for network level security between the containers, has issues with different runtimes per container, etc.

It is just a bit primitive if you want to expose multiple services to the internet on the same server. One of those apps will get compromised and then all the others will follow.

If you want a decent self hosted server, ask your frontier LLM agent of choice to configure kubernetes (on something like k3s) with mandatory userns mapping so nothing runs as root on the host, default deny firewall so inter-container communication is as locked down as possible, and if your router supports, set up VLANs so none of the containers can access your other devices on the LAN. Use something like backrest to handle backups, alertmanager and Grafana for monitoring, Keel for auto updates. Also consider separating ingress for public and internal services and use Tailscale with split DNS to acces the internal entrypoint. Set up Crowdsec as WAF and subscribe to their free blocklists to filter out bots. Ask it to set this all up using Ansible, so it can be maintained.

While this would be extremely time consuming to set up and maintain by hand, an agent can do and test it in a few hours.

crabmusket 7 hours ago||
> has issues with different runtimes per container

Could you be more specific about that?

> One of those apps will get compromised and then all the others will follow...

Per their security docs, containers are rootless but I don't see anything about VLAN isolation.

https://cloudinabottle.org/docs/how_it_works/security.html

hamdouni 7 hours ago|||
Skip kubernetes and deploy to bare server