scripts/deploy-prod: Ziel aus git-ignorierter scripts/deploy.env (Fallback)
Ohne Ziel-Argument liest das Skript DEPLOY_TARGET aus scripts/deploy.env (git-ignoriert; Vorlage scripts/deploy.env.example ist eingecheckt). Argument hat weiterhin Vorrang. Der Wert wird bewusst NICHT via `source` gelesen, weil bash bei `host:~/pfad` die Tilde nach dem ':' lokal expandieren wuerde; stattdessen roh ausgelesen, Whitespace/CR + umgebende Quotes gestrippt, das ~ bleibt fuer die Remote-Seite erhalten. Lokal verifiziert: Fallback greift, ~ bleibt in unquoted/single-/ double-quoted erhalten (kein lokales $HOME), Quotes entfernt. .gitignore: scripts/deploy.env ergaenzt (die vorhandene .env-Regel greift wegen des abweichenden Dateinamens nicht). README (de/en) aktualisiert; Beispielpfad auf die htdocs-ssl-Direktaufschaltung umgestellt. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
ecf767cfb5
commit
6b83af7d73
@@ -87,18 +87,24 @@ from `VERSION` + commit count).
|
||||
**Easier: `scripts/deploy-prod.sh`.** The script runs exactly that prod build
|
||||
**and** both fix-ups (drop `LICENSE` alongside + straighten the link, footer
|
||||
version + commit link just like the Pages workflow) and mirrors the result to a
|
||||
server via rsync/SSH. The target path is the only required argument:
|
||||
server via rsync/SSH:
|
||||
|
||||
```bash
|
||||
scripts/deploy-prod.sh mih00@mih00.hostsharing.net:~/doms/javagil.de/subs-ssl/werkbaum/
|
||||
scripts/deploy-prod.sh mih00@mih00.hostsharing.net:~/doms/werkbaum.javagil.de/htdocs-ssl
|
||||
```
|
||||
|
||||
The target is either this argument or — with no argument — the `DEPLOY_TARGET`
|
||||
variable from the **git-ignored** file `scripts/deploy.env` (template:
|
||||
`scripts/deploy.env.example`, copy it once and fill in the path). An argument
|
||||
takes precedence.
|
||||
|
||||
Without `-y` it first shows a `--dry-run` preview and asks for confirmation.
|
||||
`rsync --delete` ensures **nothing old** is left at the target — so the target
|
||||
directory is treated as exclusive to Werkbaum. (Hostsharing: for a **subdomain**
|
||||
like `werkbank.javagil.de` under the parent domain `javagil.de` the web directory
|
||||
is `…/subs-ssl/<name>/`; a directly-served domain would live under
|
||||
`…/htdocs-ssl/`.)
|
||||
directory is treated as exclusive to Werkbaum (an in-flight Let's Encrypt
|
||||
challenge under `.well-known/` is spared via `--filter=protect`, and web-friendly
|
||||
755/644 permissions are enforced). (Hostsharing: a **directly-served** domain is
|
||||
served from `…/htdocs-ssl/`; as a **subdomain** under another domain the web
|
||||
directory would be `…/subs-ssl/<name>/`.)
|
||||
|
||||
## Project documents
|
||||
|
||||
|
||||
Reference in New Issue
Block a user