31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
|
---
|
||
|
|
title: Static websites are easy to backup
|
||
|
|
date: 2025-03-14
|
||
|
|
permalink: daily/2025/03/14/backup
|
||
|
|
tags:
|
||
|
|
- software-development
|
||
|
|
- static-websites
|
||
|
|
- static-site-generators
|
||
|
|
- sculpin
|
||
|
|
cta: ~
|
||
|
|
snippet: |
|
||
|
|
Static websites are easy to backup and restore.
|
||
|
|
---
|
||
|
|
|
||
|
|
As well as being [easy to build][0] and [simple to deploy][1], static websites are easy to backup and, if needed, restore.
|
||
|
|
|
||
|
|
I backup several static websites from my server using rsync - the same command I use to deploy them.
|
||
|
|
|
||
|
|
rsync is fast as it only downloads files that have changed, so backing up several websites only takes a few seconds.
|
||
|
|
|
||
|
|
There are are no databases to worry about - all I need to do is backup the static files themselves.
|
||
|
|
|
||
|
|
Running the backups is also easy.
|
||
|
|
|
||
|
|
I have a scheduled cron job that downloads everything from the `/var/www/vhosts` directory on my server and creates a local copy.
|
||
|
|
|
||
|
|
If I need to restore from a backup or migrate to a different server, I just run the appropriate rsync command to re-upload them - the same as how I deployed them originally.
|
||
|
|
|
||
|
|
[0]: {{site.url}}/daily/2025/03/12/easy
|
||
|
|
[1]: {{site.url}}/daily/2025/03/13/deploy
|