Run Slugkit development independently on port 3013 #302
No reviewers
Labels
No labels
activitypub
admin
api
architecture
articles
auth
bug
cleanup
cli
comments
compatibility
config
contacts
content
database
deployment
design
dev-env
diagnostics
docs
documentation
email
enhancement
feature
federation
feed
health
homepage
implementation
integration
logging
mastodon
media
navigation
npm-packages
openapi
opengraph
packages
passkeys
preview
priority:high
priority:low
priority:medium
production
proof
proxy
public-routes
public-ui
release
safety
slug-api
slug-auth
slug-core
slug-federation
slug-media
slug-template
social
sources
status:active
status:canceled
status:done
status:inprogress
status:waiting
syndication
tailwind
template
test
web
webauthn
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/slugkit!302
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/task-431d12b5-slugkit-dev-port"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Slugkit toolkit development defaults conflicted with Rott on port 3000 and another website's Garage ports. Repository startup now defaults to port 3013, exports the resolved APP_PORT into Overmind, and uses dedicated Garage ports 3930–3933. Generated website defaults remain unchanged.
Updated environment examples, setup defaults, documentation, and existing development environment regression expectations. The local environment was started through
make dev, and only theslugkit-devCLI API address was changed tohttp://localhost:3013/api/v1; the existing key and all other entries were preserved.Validation: full
./scripts/pre-pr.shpassed (1,261 tests). Installed CLI Doctor passes all seven checks, including contract 1.1.0 and authentication. The served spec matches the official archived reference. Database records, credentials, and federation keys match the pre-start backup, excluding expected API-key usage timestamps. Rott remains reachable on port 3000, and all three Slugkit Overmind services are running. No production rollout or npm release is required.Task: task-431d12b5 — Run versioned Slugkit development on port 3013.
Independent review
607a967b88546fea9099098d7329bddc0e5cc9da./api/v1. Generated-site defaults remain unchanged. Documentation distinguishes global and repository-local CLI entries and records the repeatable startup procedure.