remove dated examples
This commit is contained in:
@@ -10,7 +10,6 @@ The logic lives in the scripts, never in the Makefile.
|
||||
|
||||
```bash
|
||||
make build # cfg/standalone -> gen/standalone
|
||||
make build sample # cfg/sample -> gen/sample
|
||||
make start # run it
|
||||
```
|
||||
|
||||
@@ -27,8 +26,8 @@ make start # run it
|
||||
| `make component [list\|publish\|sync\|watch\|diff]` | `ctrl/spr.py` | publish a distributable component |
|
||||
| `make deploy` | `ctrl/deploy.sh` | rsync `gen/standalone` to the server and restart |
|
||||
|
||||
Bare words pass straight through, so `make build sample` becomes
|
||||
`ctrl/build.sh sample`. Anything starting with a dash would be eaten by make
|
||||
Bare words pass straight through, so `make build myroom` becomes
|
||||
`ctrl/build.sh myroom`. Anything starting with a dash would be eaten by make
|
||||
itself, so those go through `ARGS`:
|
||||
|
||||
```bash
|
||||
|
||||
@@ -59,10 +59,10 @@ Open [http://localhost:9000](http://localhost:9000) and configure your room from
|
||||
Start from a sample configuration:
|
||||
|
||||
```bash
|
||||
python -m init.cli myroom --from sample
|
||||
python -m init.cli myroom --from standalone
|
||||
```
|
||||
|
||||
This copies the sample room's config as your starting point.
|
||||
This copies the standalone room's config as your starting point.
|
||||
|
||||
## Rebuild
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ python -m init.cli myroom
|
||||
python -m init.web
|
||||
|
||||
# Clone from existing room
|
||||
python -m init.cli myroom --from sample
|
||||
python -m init.cli myroom --from standalone
|
||||
```
|
||||
|
||||
## Layers
|
||||
|
||||
@@ -28,16 +28,16 @@ files:
|
||||
Then build. The compose merge is a step in [Export / Compile](#export):
|
||||
|
||||
```bash
|
||||
python build.py --cfg sample
|
||||
cd gen/sample && docker compose up -d
|
||||
python build.py --cfg <room>
|
||||
cd gen/<room> && docker compose up -d
|
||||
```
|
||||
|
||||
`build.py` merges each cabinet's compose fragment into the room's
|
||||
`docker-compose.yml`, declares its named volumes, and appends its settings to
|
||||
`.env.example` — never to `.env`.
|
||||
|
||||
**A service the room already declares wins.** `cfg/amar/docker-compose.yml`
|
||||
ships its own `db`; switching the postgres cabinet on will not replace it. The
|
||||
**A service the room already declares wins.** A room whose `docker-compose.yml`
|
||||
ships its own `db`: switching the postgres cabinet on will not replace it. The
|
||||
build says so when it skips one:
|
||||
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user