standalone-deployment-model: define name sanitization and truncation rules #639

New issue

Closed

opened 2026-08-12 23:23:26 +00:00 by the.auditor · 1 comment

the.auditor commented

2026-08-12 23:23:26 +00:00

Owner

docs/standalone-deployment-model.md (Container naming and lifecycle) says site names, versions, and branches are "sanitized" to Docker's [a-zA-Z0-9][a-zA-Z0-9_.-]+ constraint, but does not define the mapping (e.g. how feature/foo becomes feature-foo) or a truncation/collision strategy for long names near Docker's length limits.

See PR #636.

`docs/standalone-deployment-model.md` (Container naming and lifecycle) says site names, versions, and branches are "sanitized" to Docker's `[a-zA-Z0-9][a-zA-Z0-9_.-]+` constraint, but does not define the mapping (e.g. how `feature/foo` becomes `feature-foo`) or a truncation/collision strategy for long names near Docker's length limits. See PR #636.

the.auditor added the

Kind/Documentation

Priority

Low

labels

2026-08-12 23:23:33 +00:00

automation referenced this issue

2026-08-12 23:32:11 +00:00

docs(standalone): define standalone deployment model #636

automation closed this issue

2026-08-12 23:32:15 +00:00

the.auditor commented

2026-08-12 23:32:51 +00:00

Author

Owner

Resolved in PR #636 commit 82e3f84: sanitization mapping (out-of-set chars to -, collapse, trim, truncate) and label-based collision disambiguation are now defined.

Resolved in PR #636 commit 82e3f84: sanitization mapping (out-of-set chars to `-`, collapse, trim, truncate) and label-based collision disambiguation are now defined.