Skip to content

Run live API development inside the private managed service network #110

Description

@adrianwebb

Problem

The live-api recipe currently starts Node on the host. Even after the manager injects the declared database secret, the process cannot resolve private managed service identities such as database, mailpit, and treedx. Publishing those dependencies to the host would violate the development architecture.

Required recipe

  • Run source-watched Node in a project-owned development Compose service attached to treeseed-platform.
  • Publish only API port 3000 to 127.0.0.1 for manager readiness and canonical edge routing.
  • Propagate validated component environment and only declared target secrets.
  • Reuse the managed compatible database without automatic migrations beyond the API's existing startup contract.
  • Stop cleanly with the development process group; no public route or persistent development container remains.
  • Keep release Compose immutable and unchanged.

Discovered by the real seven-project development session. Deployment counterpart: treeseed-ai/deployment#173.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions