On Linux here. I have a directory for anything that needs to be backed up. That contains: - Business (plans, invoices, tax receipts etc) - Documents (general n

On Linux here. I have a directory for anything that needs to be backed up. That contains: - Business (plans, invoices, tax receipts etc) - Documents (general non-business documents) - Email (Thunderbird profile folders) - Projects - Client 1 - code - docs - Client 2 - code - docs Keeping code and docs together for each client works for me. Apache and hosts are set up to point to various web roots under ~/Projects/Clientn/docs with aliases like https://client2/ https://client2/. Git likewise. Outside the "backupable" root directory are the usual folders like Downloads, Pictures, Videos etc ... I don't care if I lose anything in these locations in a meltdown. Things were much more complicated when I ran Windows as a dev environment, but it's pretty straightforward now.