feat: align CLI environment & project config with the SDK#29
Closed
Marc-AnthonyG wants to merge 1 commit into
Closed
feat: align CLI environment & project config with the SDK#29Marc-AnthonyG wants to merge 1 commit into
Marc-AnthonyG wants to merge 1 commit into
Conversation
Bring the `burn` CLI in line with how the Burn Central SDK handles
environments and project configuration:
- Project linking now lives in a single, committed `tracel.toml` at the
workspace root (matching the SDK's filename and `owner`/`name` fields),
shared across all environments instead of a per-environment `.burn`
folder. Owner/project are therefore identical across dev/staging/prod.
- Drop the `.burn` folder entirely; build/packaging scratch now lives
under `target/burn-central/` (already gitignored).
- `burn [--dev|--staging N] train` exports `TRACEL_ENV` (and, when linked,
`TRACEL_NAMESPACE`/`TRACEL_PROJECT`) to the spawned `cargo run` process,
so the SDK inside the training binary targets the same backend and
project as the CLI. The env string format matches the SDK's parser
(`Production` / `Development` / `Staging(N)`).
- Remove the per-environment `get_burn_dir_name()` and the now-unused
`burn_dir_name` parameter from `ProjectContext::{load,init,unlink}`.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
Claude-Session: https://claude.ai/code/session_01DSi2TvcSnucSP61Ds5Xtnu
Member
Author
|
I will take a look at this when I finish with cross compilation. Just put claude to work on the issue we talk about, but didn't look this up yet. |
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
2 participants
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.
Bring the
burnCLI in line with how the Burn Central SDK handles environments and project configuration:tracel.tomlat the workspace root (matching the SDK's filename andowner/namefields), shared across all environments instead of a per-environment.burnfolder. Owner/project are therefore identical across dev/staging/prod..burnfolder entirely; build/packaging scratch now lives undertarget/burn-central/(already gitignored).burn [--dev|--staging N] trainexportsTRACEL_ENV(and, when linked,TRACEL_NAMESPACE/TRACEL_PROJECT) to the spawnedcargo runprocess, so the SDK inside the training binary targets the same backend and project as the CLI. The env string format matches the SDK's parser (Production/Development/Staging(N)).get_burn_dir_name()and the now-unusedburn_dir_nameparameter fromProjectContext::{load,init,unlink}.