Prove second site initialization #2

New issue

Open

opened 2026-05-19 19:51:44 -05:00 by erik · 0 comments

erik commented

2026-05-19 19:51:44 -05:00

Owner

Goal

Use slug init to create a second standalone site from the in-repo template and prove the initialized site can run independently while preserving Slugkit compatibility.

Requirements

Run slug init into a clean directory outside the toolkit source tree or another documented test location.
Install dependencies for the initialized site.
Configure the initialized site with distinct site identity values.
Run migrations and start the initialized site locally.
Create/configure an API key for the initialized site.
Configure slug with a profile targeting the initialized site.
Run slug doctor successfully against the initialized site.
Exercise representative CLI commands against the initialized site.
Verify the generated site does not contain the CLI source and can be treated as a standalone codebase.
Document findings and any friction that should feed back into template or slug init improvements.

Acceptance criteria

slug init creates a second standalone site.
The initialized site installs dependencies, runs migrations, and starts locally.
The initialized site has distinct configured identity values.
The initialized site does not include CLI source directories.
slug doctor succeeds against the initialized site.
Representative CLI commands work against the initialized site or documented unsupported operations return 501 Not Implemented clearly.
Findings are documented with follow-up tasks for any setup friction.

Dependencies

task-1cd54958
task-f48ac599
task-3047e4a1

## Goal Use `slug init` to create a second standalone site from the in-repo template and prove the initialized site can run independently while preserving Slugkit compatibility. ## Requirements - Run `slug init` into a clean directory outside the toolkit source tree or another documented test location. - Install dependencies for the initialized site. - Configure the initialized site with distinct site identity values. - Run migrations and start the initialized site locally. - Create/configure an API key for the initialized site. - Configure `slug` with a profile targeting the initialized site. - Run `slug doctor` successfully against the initialized site. - Exercise representative CLI commands against the initialized site. - Verify the generated site does not contain the CLI source and can be treated as a standalone codebase. - Document findings and any friction that should feed back into template or `slug init` improvements. ## Acceptance criteria - [ ] `slug init` creates a second standalone site. - [ ] The initialized site installs dependencies, runs migrations, and starts locally. - [ ] The initialized site has distinct configured identity values. - [ ] The initialized site does not include CLI source directories. - [ ] `slug doctor` succeeds against the initialized site. - [ ] Representative CLI commands work against the initialized site or documented unsupported operations return `501 Not Implemented` clearly. - [ ] Findings are documented with follow-up tasks for any setup friction. ## Dependencies - task-1cd54958 - task-f48ac599 - task-3047e4a1

erik added the

labels

2026-05-19 19:51:44 -05:00

erik added

priority:low

and removed

priority:medium

labels