|
|
@@ -26,7 +26,8 @@ Copy one `<li class="project">` block in `public/index.html` and change:
|
|
|
- the **Visit** link to `https://<name>.monoexp.com/` (leave it out for source-only projects)
|
|
|
- the **Source** link to `https://git.monoexp.com/bajdev/<repo>`
|
|
|
|
|
|
-Open a PR; merging it deploys the page once the site is on the pipeline.
|
|
|
+Open a PR; merging it deploys the page automatically (the site is on the
|
|
|
+merge-to-deploy pipeline).
|
|
|
|
|
|
## Hosting
|
|
|
|
|
|
@@ -66,14 +67,24 @@ DNS needs no change: the `@` and `*` A records at Hover already point here.
|
|
|
Then do the first deploy, **either** yourself:
|
|
|
|
|
|
```bash
|
|
|
- git clone git@git.monoexp.com:bajdev/home.git ~/src/home
|
|
|
+ git clone https://git.monoexp.com/bajdev/home.git ~/src/home
|
|
|
rsync -a --delete ~/src/home/public/ /srv/www/vhosts/monoexp.com/
|
|
|
```
|
|
|
|
|
|
- **or** by asking Claude, which runs
|
|
|
- `deploy-static monoexp.com ~/src/home/public` from its own account. Pass
|
|
|
- the source folder explicitly, because the script's default would look for
|
|
|
- `~/src/monoexp/public`.
|
|
|
+ The clone uses HTTPS because the repo is public, so no SSH key is
|
|
|
+ needed.
|
|
|
+
|
|
|
+ **or** by asking Claude, which runs this from its own account:
|
|
|
+
|
|
|
+ ```bash
|
|
|
+ rsync -rlt -O --delete ~/src/home/public/ /srv/www/vhosts/monoexp.com/
|
|
|
+ ```
|
|
|
+
|
|
|
+ That's `deploy-static` without the parts that need to own the folder:
|
|
|
+ `-rlt -O` copies files and links with their times, but never tries to
|
|
|
+ change the folder's own permissions or timestamp, which only its owner
|
|
|
+ (the Admin) can do. Plain `deploy-static` uses `rsync -a`, which would
|
|
|
+ copy the files and then fail on the folder.
|
|
|
|
|
|
Pick one, not both: whoever deploys first owns the files, and the other
|
|
|
account then can't update them. Merge-to-deploy hands them to the `deploy`
|