But why stop at 10 years? If the theoretical bandwidth limit of SM Fiber is above 100 Gbit/s then there is simply no way that a household will need more internal bandwidth than that. Even for the next 20-30 years, because other technologies (like SATA) will be the limiting factor.
I believe this could be a case of future proofing that will actually last 30-40 years, no?
Any chance you could point me in the right direction on how to set something like this up?
Right now, I'm using pure CPU Llama but only the 17B version, based on I believe llama.cpp. How do I mix both CPU and GPU together for more performance?
How do you handle backups with your instance? I have a simple bash script that sync the entire data directory to Backblaze and I'd love to hear easier or better ways to do this.
The one thing that gives me hypertension when self hosting a code repository is backups.
The hard drive of your server can fail at any time and when self hosting you are responsible for your backups.
This is giving me night terrors, especially when its on a cloud server and I don't have access to the hardware.
Currently, I'm running a cron task once per day executing a simple backup script that does the following:
Stop the Gitea container, copy the entire Gitea directory (including the docker-compose.yml and the data directory) to a backup folder, restart the container, sync that folder to a Backblaze bucket, delete the backup folder.
Restoring the backup is (should) be as easy as downloading the bucket from Backblaze and simply docker-composing it up.
I'm looking for other ideas advice that will help me sleep at night. Thanks!
Do you have any good recommendations for self hosted services that allow me to save a link and have an archived copy of the website saved to disk?
So far, I've tried Wallabag, Linkwarden and Archivebox but I feel like they don't quite work the way I want to.
What are you experiences with this?