Document the real deploy setup: SSH port, deploy user, shared key
- SSH on port 42069, deploy user plesk-nachklang, one deploy key for all Nachklang repos as a Gitea organisation secret (host, port and user as organisation variables; path and build values per repository). - Key-only login for the deploy user via a Match block in sshd_config. - Plain /bin/bash instead of Plesk's chrooted shell: bash segfaults in the chroot copy on this server, so every session closed right after login; the read-access trade-off and a stricter rrsync option are noted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2 files changed
+75
-29
No files matched your search
@@ -57,6 +57,11 @@ Collected during the rewrite (September 2026); the progress log in
|
||||
`--delete` must exclude what Plesk or Passenger keep there (`tmp/`, `.well-known/`). The first
|
||||
deploy replaces the Angular build - back it up first, and switch Plesk to the Node app right
|
||||
after the run, because the folder no longer works as a static site.
|
||||
- **Plesk's chrooted SSH shell is broken on this server**: `bash` segfaults in the chroot copy
|
||||
under `/var/www/vhosts/nachklang.art`, so sessions close right after login (and the command of
|
||||
an `ssh host 'cmd'` never runs, exit 255). The deploy user uses plain `/bin/bash` instead.
|
||||
- **SSH is on port 42069**, not 22 (22 is closed); the deploy user is `plesk-nachklang`, not
|
||||
`nachklang`.
|
||||
- **Disable the Jenkins job before merging to master**, or it runs `ng build` on the next push.
|
||||
|
||||
## shadcn / Base UI
|
||||
|
||||
Reference in new issue
Block a user