Yes, this. I’ve had this happen a number of times and the solution was just to bump the specified elpaca version. I’ve had no negative consequences from doing so.
Yes, this. I’ve had this happen a number of times and the solution was just to bump the specified elpaca version. I’ve had no negative consequences from doing so.
Thank you for all of this info. I’m planning to slowly roll out three of these servers with Proxmox as a cluster. I’m just upgrading all of the available power outlets and spec’ing UPSes now.
Via another reddit thread on the topic, I found this YouTube playlist which has been super helpful. Just re-posting it here for posterity:
https://www.youtube.com/playlist?list=PLbNp7AIu8VYyzsocLUdCScF4zvou8rzS9
Thanks, y’all.
I don’t think I need so many drives so now its just a matter of verifying that if I scoop one or two low-RAM-specs off of eBay for cheap I will be able to re-populate them with RAM.
This is pretty much exactly what I do. The only real hiccups I can think of:
If you use Org Roam the different machines will have their own Sqlite databases and thus you may need to do an org-roam-db-sync when hopping.
org-agenda may need to be refreshed when hopping machines.
I have bound keys for both of those things to make the manual portion as non-disruptive as possible.