restic . Use whatever you want for the back end. If there's important stuff on the machine that's not anywhere else, do NOT rely on any one cloud service.
Ask HN: Developer Workstation Backups
21–30 of 52 posts
Re: Ask HN: Developer Workstation Backups
#22borgbackup + local unraid server + cron
Re: Ask HN: Developer Workstation Backups
#23* Dropbox for documents and important files
* SyncThing (to local Synology and cloud server) for my root git folder (I use the following "style" ~/git//)
* CarbonCopyCloner (to T7 SSD) running daily for a full clone
* Backblaze for my cloud copy
* Time Machine to my Synology just to be safe
Not sure if that meets "without a lot of fuss" but it's all on auto-pilot for me and I never think about it.
Re: Ask HN: Developer Workstation Backups
#24I like https://www.borgbackup.org/ and you can get a relatively cheap storage plan on rsync.net just for Borg (https://www.rsync.net/products/borg.html)
Retrieving backups is a little manual. Perhaps someone has created a nice GUI for it.
Re: Ask HN: Developer Workstation Backups
#25Datto...I frickin love that company.
Not easily accessible though :(
Re: Ask HN: Developer Workstation Backups
#26Treat your workstation much like one would a Docker container: everything should be ephemerally configured, driven by automation, and reproducible on the fly. Always commit frequently, backup large files to cloud storage, and wipe your device clean on a regular basis.
nice
Re: Ask HN: Developer Workstation Backups
#27codeberg.org for code and notes, rsync to local HDDs, SyncThing between workstation, laptop and mobile, Sync.com for things that I need to store privately in the cloud
Re: Ask HN: Developer Workstation Backups
#28Any dev related stuff is checked in, so dockerfiles and code, so that’s easy to spin up again.
Then I have a folder in my home called Sync that has a library and resources folder inside. Documents and Pictures etc are linked to library, and resources contains docs or things that I want to keep.
The sync folder is setup in syncthing to my laptop and nas, then the nas also backups up that to Backblaze.
Dotfiles and ansible books are in GitHub, via chezmoi.
Otherwise I don’t mind if I lose anything else.
Re: Ask HN: Developer Workstation Backups
#29I just don't store anything locally that I don't mind losing. If we are talking about software development then everything is tracked in git. If I'm still part way through some changes at the end of the day I will just `git commit -am "wip"` and push to a remote branch for safe keeping. Then you can rework the commit[s] locally before opening / flagging the PR for review. Documents and stuff are all in google docs/dr…
>Documents and stuff are all in google docs/drive or something like that
There have been horror stories of people randomly loosing access to their Google account, probably because some automatic check decided that they violated some term of use. I see how convenient it is to work "in the cloud", but if those are important documents you should keep a local copy as well.
Re: Ask HN: Developer Workstation Backups
#30I like https://www.borgbackup.org/ and you can get a relatively cheap storage plan on rsync.net just for Borg ( https://www.rsync.net/products/borg.html ) Retrieving backups is a little manual. Perhaps someone has created a nice GUI for it.
There are at least two GUI's for borgbackup:
* Vorta (https://github.com/borgbase/vorta)
* Pika Backup for Gnome (https://apps.gnome.org/app/org.gnome.World.PikaBackup/)
Vorta is multiplatform and more reliable by my experience.