Skip to content

Starter template: rojo + asphalt + rbx-cli wired with CI, zero-to-staging in 15 minutes #1

Description

@dev-bap

Summary

The complement to rbx import (#44): import serves existing games, a template repo serves new ones. A newcomer should go from clone to a deployed staging place in 15 minutes without reading five docs.

Contents

  • rokit.toml pinning rojo + asphalt + rbx (the composition stance from the README, made runnable).
  • Example rbxplace.toml (dev/staging/prod + a codegen = false CI env), rbxshop.toml, rbxmeta.toml, rbxapikey.toml with the recommended key split (deploy key vs read-only key vs ops key, per docs/ops.md).
  • A minimal rojo project + generated Envs.luau showing the runtime-dispatch pattern.
  • GitHub Actions workflow: rojo buildrbx place upload --env staging → checks (rbx check once #50 exists) → manual-approval rbx place promote staging prod --log.
  • .gitignore covering secret files and data backups.

Notes

  • Separate repo (rbx-forge/rbx-template or similar) marked as a GitHub template repo, referenced from the README and the docs site (#57).
  • The template doubles as living documentation: it's the answer to "how do I structure a project", and CI running on the template repo itself smoke-tests the advertised flow against real releases.

Migrated from the pre-public tracker (was #59). #N references in the text above use the old numbering.


Re-filed from #17 when the repository history was reset for 0.1.0. Issue and PR numbers referenced above belong to the previous numbering and no longer resolve; the reasoning does not depend on them.

Metadata

Metadata

Assignees

No one assigned

    Labels

    deferredDeliberately not now. The reasoning is in the issue; reopen the question, not the ticket

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions