Windows: generate and backfill TRITON_MANAGE_JWT_SIGNING_KEY #18
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
primatekuntech/triton-install!18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/windows-jwt-signing-key"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Same bug as #16, on the Windows installer this time.
install.ps1generatesPOSTGRES_PASSWORD,TRITON_MANAGE_WORKER_KEY, andTRITON_VAULT_KEYbut neverTRITON_MANAGE_JWT_SIGNING_KEY, which the manage-server binary requires to start — same crash-loop as the Linux bug fixed in #16.compose.yamlis shared across platforms and already whitelists the variable (from #16), so only the Windows-side generation was missing.install.ps1: generate the key alongside the other auto-generated secrets on first installupgrade.ps1: backfill the key into.envfiles created before this fix, mirroringupgrade.shFound while working on #11/#17; unrelated to the runtime choice so split out into its own PR.