Added some more notes.

This commit is contained in:
2025-07-03 12:33:48 +10:00
parent 0a4fd6360a
commit 0009ac6ad7

View File

@@ -13,3 +13,18 @@ HLBDAT=dat.test docker compose up
Even if you forget, you'd still need to `git add`, `git commit` and `git push` on your local machine. Moreover, *somebody* would need to `git pull` and `docker restart` on the production hosting environment before anybody else would see what you've done, so this is **super** low risk. Even if you forget, you'd still need to `git add`, `git commit` and `git push` on your local machine. Moreover, *somebody* would need to `git pull` and `docker restart` on the production hosting environment before anybody else would see what you've done, so this is **super** low risk.
If you make some changes to `dat.live/events.json` and want to undo them, a `git status` might show something like this...
```
On branch main
Your branch is up to date with 'origin/main'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory) modified: dat.live/events.json
no changes added to commit (use "git add" and/or "git commit -a")
```
Those notes included in the output are 10 / 10 (IMO). Running `git restore dat.live/events.json` will reset your local copy to the contents that you last pulled from the remote repository.