I’ve have sites on Jekyll and Hugo. I prefer Hugo.
One of my Hugo sites is very heavy on images and although it’s not a photography portfolio, it’s a portfolio of progress photos. Almost 1500 images. Hugo builds the site and generates the thumbs in under 3min which is impressive, compared to other SSGs.
I use Go templating in other places so Hugo templates come a lot easier than Jekyll’s. It’s a bonus in my book.
I don’t think such a thing exists. It clashes with the idea of selfhosting. You can shoestring a solution that will do what you ask but it won’t be an appliance/application that someone else maintains.
Weekly unattended apt and docker updates are actually worse than manual ones. I update maybe once a month. Watchtower takes care or checking and downloading new updates but I’m the one to redeploy containers with the new image.
The closest thing that comes to mind is Portainer. It offers point 1, 4, 6. The Business edition has update checking built into the UI. The Community edition lacks update checking but you can substitute it (and improve on it IMO) with Watchtower.
Watchtower can check and download updates while you just click redeploy.
For backups, try Nautical Backup
This leaves only rollbacks unaddressed. But realistically, on a hands-off box, you won’t need it and if you do, copying over from the backup will be enough.
Instead of using Duck DNS, buy a cheap domain, register it with Cloudflare, set up “cloudflared” which dynamically updates your DNS records - a DIY DDNS. You could even call it DDDNS. That way you are in control of the whole chain.
The others gave you a solution but note the following:
Jellyfin in a VM means that once you passthrough the GPU to the VM, you will lose graphical capabilities on the host. That could be a dealbreaker. Segmenting the GPU is inefficient.
I host my Jellyfin in a LXC because I can passthrough the GPU without reserving it to the LXC.
Here is my config. I use the i5-7500 and can say that it’s pretty good. It’s in the main node of my proxmox cluster that hosts my NAS VM and main Docker instance with lots of containers. Average power consumption is about 65-70W.
I started out with just this node as a standalone server so it has everything. I got a FD Define R5 case because it can hold lots of drives. Define R7 is recommended too. R6 isn’t because its generation is the only one using its own HDD trays (IIRC). Overall, they are the best NAS tower cases. Sound-proofed and every HDD is mounted with gromets. I use a Seasonic Focus PSU because they come with a lot of HDD power connections out of the box and I don’t need to daisy-chain.
This is the 4th iteration of this machine and the item I’ve carried over since v1 is the HBA. (RAID card in IT mode). It removes the requirement of the MB to have a high amount of SATA connections. The whole card is passed through in my NAS VM.
What I’m planning to do is to add a NIC. Not sure 4x1GbE or 2x10GbE. Or maybe both. With them, the power usage might go in the mid 80s but that’s fine for a machine that can be a hypervisor, a docker server, a NAS and a network appliance all in one. The downside is that if you reboot it, you lose the network for a while.
Additionally, I got two Lenovo Tiny 920q that run my experimental stuff. They are purely for compute and for HA failover in case the main node fails.
If you can find DDR3 for free and your power is cheap/renewable, stick with it.
In any other scenario - upgrade to newer hardware. Don’t buy e-waste.
It’s worth it. At some point you might enconter a service that requires SSL to work even on LAN. I treat them like pipes. The fewer pipes i need to pipe traffic through, the easier it is.
I use split DNS to access services locally, over the internet and via VPN. Everything is behind a Traefik proxy that uses wildcard certs. It enforces SSL for everything and I have just one pipe to think about.
I can’t speak about AMD but here is a rundown for Intel CPUs.
These are the 3 tiers that I look at. Metor Lake is about to be released with native encode and decode support for AV1 but it’s too early to matter.
More info in the chart here.