Live data from Hacker News

Self-Hosting like it's 2025

kiranet.org

111–120 of 240 posts

Re: Self-Hosting like it's 2025

#111

Self-Hosting like it's 2025...uhhgg... Don't get me wrong I love some of the software suggested. However yet a another post that does not take backups as seriously as the rest of the self-hosting stack. Backups are stuck in 2013. We need plug and play backups for containers! No more roll your own with zfs datasets, back up data on the filesystem level (using sanoid/syncoid to manage snapshots or any other alternative…

Best decision of last year for my homelab: run everything in Proxmox VMs/containers and back up to a separate Proxmox Backup Server instance.

Fully automated, incremental, verified backups, and restoring is one click of a button.

Re: Self-Hosting like it's 2025

#112
post #10

Last thing I need is Kubernetes at home

"apt-get install" tends to be enough once you stop chasing latest-and-greatest and start to appreciate things just running with low maintenance more.

I totally agree! Containers are nice when your installation is ephemeral, deploying and updating several time in a short period. But using the package manager is as easy as you get.

Re: Self-Hosting like it's 2025

#113
I think the reasons not to self-host are the difficulty of implementing any type of dynamic scaling. For instance when clicking on this article I get a result that their site is down. Instead of benefiting from the traffic their engagement got them, they are crashing.

Re: Self-Hosting like it's 2025

#114
This site redirects to localhost:1313. Is this some sort of April fool's joke that I'm not getting?

    $ curl https://kiranet.org/self-hosting-like-its-2025/
    
    
      
        //localhost:1313/posts/self-hosting-like-its-2025/
        
        
        
        
      
    

Re: Self-Hosting like it's 2025

#115

What about Kamal? https://kamal-deploy.org/ Did anybody here use it for anything that is not a Ruby on Rails app?

Yes, I have been using it and really enjoying it for deploying web apps. So far I have deployed web apps using: * fastapi (python) * Django ninja (python) * ghost cms (node)

I have been writing up my thoughts (and an example): https://andrewperkins.com.au/kamal/

The ability to deploy to both cloud servers and on-premises is a big win as I often work on projects that have a mix of both.

As the sibling comment says, it’s focussed on web servers. In my use case that is fine!

Re: Self-Hosting like it's 2025

#116
post #25
post #18

i really like this software-centric approach, but I am a bit stuck when it comes to the hardware. Are there some sources around servers that don't suck up too much energy and are fairly quiet? What CPU is a good all-round solution?

Depends on your needs. For some Raspberry Pi (ideally with 8-16GB RAM) + SSD can be enough if you are after low power consumption. If you need more power: I had success with HP ProDesk Mini (or any other one-litre PC), you can get these second hand from like $150 and extend RAM and SSDs however you like. You can even pick processor / generation to fit your needs best. These can have consumption from like 30W if I'm n…

that sounds doable. I have a raspberry pi with an SSD for my pihole (bit of overkill, but i had stuff lying around) but for things like Immich it seems to be not beefy enough.

Re: Self-Hosting like it's 2025

#118
post #10

Last thing I need is Kubernetes at home

It is still my opinion that most businesses do not need Kubernetes, and neither should anyone self-hosting a service at home. I can see running something in a Docker container, and while I'd advise against containers what ships with EVERYTHING, I'd also advise against using Docker-compose to spin up an ungodly amount of containers for every service. You shouldn't be running multiple instances of Postgresql, or anythi…

If it wasn't for Kubernetes we'd need 1/3rd of our operations team. We're keeping unemployment down!

Re: Self-Hosting like it's 2025

#120

Earlier quoted context omitted.

It is still my opinion that most businesses do not need Kubernetes, and neither should anyone self-hosting a service at home. I can see running something in a Docker container, and while I'd advise against containers what ships with EVERYTHING, I'd also advise against using Docker-compose to spin up an ungodly amount of containers for every service. You shouldn't be running multiple instances of Postgresql, or anythi…

I'd love to use Kubernetes for my self hosting. The only problem is it's too expensive.

How is it too expensive? If you want to use the eco system you can still use something like k3s
Post reply on HN