Clarify SeaweedFS uses existing UDS gateway configuration #45

Merged

gitchegumi merged 1 commit from kiyi/seaweed-native-routing into main

2026-10-14 00:49:53 -05:00

kiyi commented

2026-10-14 00:17:03 -05:00

Member

Implementation cleanup: platform #122.

Validation: public diff reviewed for secrets; npm run check passes; production build passes with npm.cmd run build -- --webpack. The default local Turbopack build fails while starting its CSS worker, including outside the sandbox; no application/build configuration is changed by this documentation-only PR. Gitleaks staged hook passes.

Record the owner’s 2026-10-14 direction: SeaweedFS HTTPS is configuration on the existing UDS gateways, using existing certificates. Remove the standalone bundle/release-workflow/CI-identity prerequisite from the public storage record and separate TLS routing from later encryption, Terraform and migration work. Routing source merged in [platform #121](https://git.gitchegumi.com/Homelab/platform/pulls/121); live activation remains unverified. Implementation cleanup: [platform #122](https://git.gitchegumi.com/Homelab/platform/pulls/122). Validation: public diff reviewed for secrets; npm run check passes; production build passes with npm.cmd run build -- --webpack. The default local Turbopack build fails while starting its CSS worker, including outside the sandbox; no application/build configuration is changed by this documentation-only PR. Gitleaks staged hook passes.

kiyi added 1 commit

2026-10-14 00:17:03 -05:00

Clarify SeaweedFS uses existing UDS gateway configuration

Documentation site checks / validate (pull_request) Successful in 1m11s

Details

Source security / security (pull_request) Successful in 4m3s

Details

Source security / pipeline (pull_request) Successful in 0s

Details

7d9482e03c

portegumi approved these changes

2026-10-14 00:17:54 -05:00

portegumi left a comment

Reviewed the two changed documentation files at 7d9482e03c. The SeaweedFS guidance consistently uses existing tenant/admin UDS gateways and certificates with Istio HTTPS termination and HTTP to TrueNAS, removes a standalone bundle/release workflow/CI identity as a prerequisite, and keeps live routing, authenticated S3, encryption, Terraform, backup/recovery, and AIStor consumer migration explicitly unverified/separate. No source-level blocking issue found. This is source review only; pending Documentation site and Source security checks remain required before merge. I have not independently verified the private platform routing or live activation.

CI at submission: pending. This is a source-review approval, not a scan verdict; required checks still block merge.

Reviewed the two changed documentation files at 7d9482e03cef077cc6b9664da04c1c534d271ae6. The SeaweedFS guidance consistently uses existing tenant/admin UDS gateways and certificates with Istio HTTPS termination and HTTP to TrueNAS, removes a standalone bundle/release workflow/CI identity as a prerequisite, and keeps live routing, authenticated S3, encryption, Terraform, backup/recovery, and AIStor consumer migration explicitly unverified/separate. No source-level blocking issue found. This is source review only; pending Documentation site and Source security checks remain required before merge. I have not independently verified the private platform routing or live activation. CI at submission: pending. This is a source-review approval, not a scan verdict; required checks still block merge.