31 lines
1.6 KiB
Markdown
Executable File
31 lines
1.6 KiB
Markdown
Executable File
|
|
# Homelab Brisbane Home Page
|
|
|
|
A simple `docker compose up` will launch this on your machine. The **home** page will be bound to `http://localhost:8080` and the **administration** page on `http://localhost:8081`.
|
|
|
|
By default the contents of `dat.live` will be mounted, so changes made on the **administration** page will modify `dat.live/events.json`.
|
|
|
|
If you want to experiment a little without interfering with the master calendar there is a `dat.test` folder that can be used instead. Switch to using that folder by launching with...
|
|
|
|
```bash
|
|
HLBDAT=dat.test docker compose up
|
|
```
|
|
|
|
Even if you forget to use the `dat.test` folder, you'd still need to `git add`, `git commit` and `git push` before anything leaves 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.
|
|
|