feat: add asobi init --template backend#35
Merged
Conversation
Scaffolds a complete runnable backend (fetches sdk_demo_backend by pinned tag) - docker-compose.yml, the lua/config.lua mode manifest, and all ASOBI_* env vars - alongside the existing engine templates. Bare `asobi init` stays managed/Lua-first; the fuller backend is opt-in. Also document `asobi dev`, config.lua (multiple modes), and the backend template in the starter README.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses PendragonNL's DX feedback: bare
asobi initonly drops a Lua stub, so a new user can't see what a whole backend looks like. Adds an opt-in template that scaffolds a complete, runnable backend.Changes
asobi init --template backendfetchessdk_demo_backendby pinned tag (same mechanism as the engine demos) —docker-compose.yml,lua/config.lua,lua/match.lua, and theASOBI_*env contract in one repo. Runs withdocker compose up -dorasobi dev.Engines()→Names()so the "available templates" error lists all four (backend,defold,godot,unity).initnext-steps (docker compose up -d, README pointer).init) now documentsasobi dev(local run),lua/config.lua(multiple modes), and--template backend. Test asserts all three.Guardian constraints honoured
Bare
initstays managed/Lua-first (front door); backend is opt-in behind--template(not--full). Fetch-by-tag, no compose/config embedded in the binary. Tier-1 only (compose +ASOBI_*), nosys.configin the tree — that's a docs deliverable.Depends on
Pins
sdk_demo_backend@v0.1.0. That tag is cut by widgrensit/sdk_demo_backend#3 — merge it first, then this.Checks
gofmtclean,go vetclean,go build/go test ./...green. The network anti-drift E2E (ASOBI_TEMPLATE_E2E=1) will pass oncev0.1.0exists.