Prove second site initialization #2

New issue

Closed

opened 2026-05-19 19:51:44 -05:00 by erik · 1 comment

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

2026-06-08 07:15:32 -05:00

erik

2026-06-26 15:15:18 -05:00

closed this issue
added
status:done
and removed
status:active
labels

erik commented

2026-06-26 15:15:20 -05:00

Author

Owner

Synced from todu comment by @todu on 2026-06-26T20:14:14.002Z

Closing summary

Verified the slug init path by initializing a standalone site at ~/Private/testing/testapp with package name testapp and site title Test App.

Additional live-site compatibility checks against the deployed initialized site at https://slugkit.com passed:

slug doctor passed for https://slugkit.com/api/v1, including health, meta API version 1.0.0, OpenAPI 3.1.0, and API-key auth.
slug post create --type note --slug first-message ... created a draft note through the CLI.
slug post publish first-message published the note successfully.

Conclusion: slug init creates a usable Slugkit-compatible site, and the resulting deployed site works with representative slug CLI operations. No code changes were required.

_Synced from todu comment by @todu on 2026-06-26T20:14:14.002Z_ ## Closing summary Verified the `slug init` path by initializing a standalone site at `~/Private/testing/testapp` with package name `testapp` and site title `Test App`. Additional live-site compatibility checks against the deployed initialized site at `https://slugkit.com` passed: - `slug doctor` passed for `https://slugkit.com/api/v1`, including health, meta API version `1.0.0`, OpenAPI `3.1.0`, and API-key auth. - `slug post create --type note --slug first-message ...` created a draft note through the CLI. - `slug post publish first-message` published the note successfully. Conclusion: `slug init` creates a usable Slugkit-compatible site, and the resulting deployed site works with representative `slug` CLI operations. No code changes were required.