-
-
Notifications
You must be signed in to change notification settings - Fork 39
User backups
See also system backups.
You are working on stuff, it shouldn't go away just because you mistyped a command or botched an edit or accidentally typed rm. Backups are important.
Here are some ways you might back up your own stuff on your own schedule under your own control. It's not a tutorial (yet) so when you see a command that looks interesting type e.g. man tar to get all the gory details. TODO: add examples that can be cut and pasted without too much risk.
Use tar to create a tarball of your stuff, then scp to put it somewhere else. tar stands for tape archiver which shows its venerable age; it still works just fine.
e.g. tar czvf archive.tgz path/to/files, scp archive.tgz <username>@<hostname>:path/to/put/archive.tgz
rsync synchronizes a directory with a remote directory.
e.g. rsync -av --delete <username>@tilde.club:/home/<username> path/to/hold/local/copy
Use sshfs to create a remote filesystem through SSH; then your local machine can copy files to your local drive as if tilde.club were a local file system.
~ke7ofi on totallynuclear.club put together an sshfs tutorial for Linux users with a note on backups. ~jeffbonhag did one for OSX, Windows, and Linux which doesn’t mention backups, but does mention identity files.
Use git to add your home directory as a project, then back up what you have to your favorite git repository. You'll probably want to make that repo private.
Use git to add your ~/public_html directory as a project, then back up what you have to your favorite git repository. You're probably OK with making that repo public.