Prevent raw template deployment #102

New issue

Open

opened 2026-06-05 07:58:53 -05:00 by erik · 0 comments

erik commented

2026-06-05 07:58:53 -05:00

Owner

Goal

Prevent the in-repo template site from being accidentally deployed as a real production website before it has been initialized into a standalone site.

Requirements

Add a clear template initialization marker or equivalent signal that distinguishes raw template source from generated site code.
Make production startup fail with a clear message when the raw template is still uninitialized.
Treat local development and tests as safe defaults that do not require production identity values.
Have slug init stamp or replace the marker so generated sites can be deployed after configuration.
Include checks for obvious unsafe production defaults such as localhost site URLs or default admin identity values where appropriate.
Document that template/site in the Slugkit repo is development source and should not be deployed directly.

Acceptance criteria

Raw in-repo template/site cannot start in production with uninitialized defaults.
Generated sites initialized by slug init pass the initialization marker check.
The startup error clearly explains that users should deploy a generated site, not the raw template.
Local development and tests continue to work with safe defaults.
Docs explain the raw-template vs generated-site deployment boundary.
Tests cover raw-template production failure and initialized-site success.
Relevant lint/test checks pass.

Dependencies

task-d60f5efc

## Goal Prevent the in-repo template site from being accidentally deployed as a real production website before it has been initialized into a standalone site. ## Requirements - Add a clear template initialization marker or equivalent signal that distinguishes raw template source from generated site code. - Make production startup fail with a clear message when the raw template is still uninitialized. - Treat local development and tests as safe defaults that do not require production identity values. - Have `slug init` stamp or replace the marker so generated sites can be deployed after configuration. - Include checks for obvious unsafe production defaults such as localhost site URLs or default admin identity values where appropriate. - Document that `template/site` in the Slugkit repo is development source and should not be deployed directly. ## Acceptance criteria - [ ] Raw in-repo `template/site` cannot start in production with uninitialized defaults. - [ ] Generated sites initialized by `slug init` pass the initialization marker check. - [ ] The startup error clearly explains that users should deploy a generated site, not the raw template. - [ ] Local development and tests continue to work with safe defaults. - [ ] Docs explain the raw-template vs generated-site deployment boundary. - [ ] Tests cover raw-template production failure and initialized-site success. - [ ] Relevant lint/test checks pass. ## Dependencies - task-d60f5efc

erik added the

labels

2026-06-05 07:58:53 -05:00

erik added

priority:low

and removed

priority:medium