Skip to content

Commit 733c5b1

Browse files
committed
add note for scaling
1 parent 42a8f93 commit 733c5b1

File tree

1 file changed

+24
-1
lines changed

1 file changed

+24
-1
lines changed

README.md

Lines changed: 24 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,8 @@ This repository contains a comprehensive set of scripts for deploying, securing,
1717
9. [Password Rotation](#password-rotation)
1818
10. [Backup and Restore](#backup-and-restore)
1919
11. [Troubleshooting](#troubleshooting)
20-
12. [Reset and Cleanup](#reset-and-cleanup)
20+
12. [Scaling](#scaling)
21+
13. [Reset and Cleanup](#reset-and-cleanup)
2122

2223
## Overview
2324

@@ -487,6 +488,28 @@ If you encounter issues during the setup process, here are some common troublesh
487488
curl -v "http://your-domain.com/monitor?token=your_secure_monitor_token"
488489
```
489490

491+
## Scaling
492+
493+
Scaling is managed directly via your host. Before scaling, ALWAYS make sure to take a manual backup and confirm it:
494+
495+
```
496+
./utils/create_backup.sh
497+
```
498+
499+
This will take a manual snapshot and upload it to S3. You can pass an additional prefix like this: `./utils/create_backup.sh <prefix>` where `<prefix>` is something like `before_scale`.
500+
501+
After this, just use the manual scaling GUI on your host. If need be, once the server restarts, you can do a manual restore from the backup you took with:
502+
503+
```
504+
./utils/restore_backup.sh <timestamp>
505+
```
506+
507+
You can get the specific backup timestamp by running:
508+
509+
```
510+
./utils/list_backups.sh
511+
```
512+
490513
## Reset and Cleanup
491514

492515
If you need to reset your server and remove all installed components, you can use the reset script:

0 commit comments

Comments
 (0)