Summary
Request for a small, optional way to use ember new (Vite blueprint) together with TDK CLI in a local multi-service setup, or, if that is not wanted here, for guidance on where such a note should live.
What TDK is
TDK (Tilt Development Kit, @tdk-landscape/tdk-cli-core) is a local multi-service runner. Every service has a service.json, and tdk up <stack> starts that slice with Docker + Tilt, health-checked boot order and *.localhost routing through Traefik. It is not a deploy tool and not a production Compose replacement. Requirements: Docker, Tilt, Bun (for the services it generates).
| Tool |
Owns |
ember new (Vite blueprint) |
App scaffold and build tooling |
tdk project / tdk resource / tdk up |
The local landscape: ports, stacks, Docker, Tilt, proxy |
Why this might fit
Ember apps can now be built with Vite. TDK's frontend provider contract is for apps where TDK owns the generated Vite config, so an Ember app that owns its own Vite config is a bring-your-own case.
What I am asking for
- A short docs note on running an Ember app in a TDK landscape. I will send the PR if you say where it belongs.
- No code change requested.
Example flow:
# you provide the Dockerfile; TDK does not generate one for bring-your-own
npx ember-cli new shop-web --blueprint @ember/app-blueprint
tdk resource shop-web --type bring-your-own --stack shop --dockerfile ./Dockerfile
tdk up shop
Acceptance
- The note covers the dev-server host/port flags for use in a container.
ember-cli is unchanged.- Optional and additive. TDK is not a required toolchain and does not deploy anything.
Non-goals
- Replacing your deployment guidance. TDK is local-only.
- Making TDK a dependency of Ember.
Related
Companion issue on the TDK side (the provider or recipe that this depends on): tdk-landscape/tdk-cli-core#258
Disclosure: I'm one of the TDK maintainers, and I drafted this issue with AI assistance. TDK is a young, small project (1.3.x), so I'm keeping the ask small and optional. If this isn't a fit, or isn't wanted in the issue tracker, please just say so and I'll close it.
Summary
Request for a small, optional way to use
ember new(Vite blueprint) together with TDK CLI in a local multi-service setup, or, if that is not wanted here, for guidance on where such a note should live.What TDK is
TDK (Tilt Development Kit,
@tdk-landscape/tdk-cli-core) is a local multi-service runner. Every service has aservice.json, andtdk up <stack>starts that slice with Docker + Tilt, health-checked boot order and*.localhostrouting through Traefik. It is not a deploy tool and not a production Compose replacement. Requirements: Docker, Tilt, Bun (for the services it generates).ember new(Vite blueprint)tdk project/tdk resource/tdk upWhy this might fit
Ember apps can now be built with Vite. TDK's frontend provider contract is for apps where TDK owns the generated Vite config, so an Ember app that owns its own Vite config is a bring-your-own case.
What I am asking for
Example flow:
# you provide the Dockerfile; TDK does not generate one for bring-your-own npx ember-cli new shop-web --blueprint @ember/app-blueprint tdk resource shop-web --type bring-your-own --stack shop --dockerfile ./Dockerfile tdk up shopAcceptance
ember-cliis unchanged.Non-goals
Related
Companion issue on the TDK side (the provider or recipe that this depends on): tdk-landscape/tdk-cli-core#258
Disclosure: I'm one of the TDK maintainers, and I drafted this issue with AI assistance. TDK is a young, small project (1.3.x), so I'm keeping the ask small and optional. If this isn't a fit, or isn't wanted in the issue tracker, please just say so and I'll close it.