Add daily email for 2025-03-14
Static websites are easy to backup
This commit is contained in:
parent
e9555ffab0
commit
b7cd03a4b9
1 changed files with 31 additions and 0 deletions
31
source/_daily_emails/2025-03-14.md
Normal file
31
source/_daily_emails/2025-03-14.md
Normal file
|
@ -0,0 +1,31 @@
|
|||
---
|
||||
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.
|
||||
draft: true
|
||||
---
|
||||
|
||||
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
|
Loading…
Add table
Add a link
Reference in a new issue