init --systemd resolved the configuration through Paths.get(".") while
every other file it touches — the two generated config layers, an applied
fragment, the units, the .htaccess — goes through the git top level. The two
agree only when the process happens to run in the repository root; from a
subdirectory the command silently read a different repository's configuration
or none at all, so --apply's promise that the fragment's port reaches the
generated unit did not hold, and the host integration was skipped as if no
publicBaseUrl were configured.
The root is passed down instead, matching every other caller of ConfigLoader.load.
`init --systemd` resolved the configuration through `Paths.get(".")` while
every other file it touches — the two generated config layers, an applied
fragment, the units, the .htaccess — goes through the git top level. The two
agree only when the process happens to run in the repository root; from a
subdirectory the command silently read a different repository's configuration
or none at all, so `--apply`'s promise that the fragment's port reaches the
generated unit did not hold, and the host integration was skipped as if no
publicBaseUrl were configured.
The root is passed down instead, matching every other caller of
`ConfigLoader.load`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
`init --systemd` read the effective configuration through a catch-all that
swallowed every exception and continued with a default `ServerConfig`. A
repository whose `.werkator.yml` failed validation for any reason then looked
exactly like one with no `publicBaseUrl`: the `.htaccess` and the maintenance
page were skipped without a word, during initial deployment setup of all times.
The fallback stays — the units are still generated — but the exception message
is now printed. The configuration is loaded once per run so the three readers
inside `createSystemdFiles` do not repeat the warning.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
`init --systemd` resolved the configuration through `Paths.get(".")` while
every other file it touches — the two generated config layers, an applied
fragment, the units, the .htaccess — goes through the git top level. The two
agree only when the process happens to run in the repository root; from a
subdirectory the command silently read a different repository's configuration
or none at all, so `--apply`'s promise that the fragment's port reaches the
generated unit did not hold, and the host integration was skipped as if no
publicBaseUrl were configured.
The root is passed down instead, matching every other caller of
`ConfigLoader.load`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
init --systemdresolved the configuration throughPaths.get(".")whileevery other file it touches — the two generated config layers, an applied
fragment, the units, the .htaccess — goes through the git top level. The two
agree only when the process happens to run in the repository root; from a
subdirectory the command silently read a different repository's configuration
or none at all, so
--apply's promise that the fragment's port reaches thegenerated unit did not hold, and the host integration was skipped as if no
publicBaseUrl were configured.
The root is passed down instead, matching every other caller of
ConfigLoader.load.Co-Authored-By: Claude Opus 5 noreply@anthropic.com
`init --systemd` resolved the configuration through `Paths.get(".")` while every other file it touches — the two generated config layers, an applied fragment, the units, the .htaccess — goes through the git top level. The two agree only when the process happens to run in the repository root; from a subdirectory the command silently read a different repository's configuration or none at all, so `--apply`'s promise that the fragment's port reaches the generated unit did not hold, and the host integration was skipped as if no publicBaseUrl were configured. The root is passed down instead, matching every other caller of `ConfigLoader.load`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>branch was merged bypassing GitEA
Pull request closed