Proposal: Add optional BoxLite deployment profile
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 729
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Could we add an optional BoxLite deployment profile for users who want a micro-VM sandbox path?
This is additive only. Existing deployment/runtime defaults should remain unchanged.
Why
- Gives users a stronger-isolation option.
- Preserves current Docker/Apple Container paths.
- Can be introduced as an opt-in profile without breaking current installs.
Suggested scope
- Add an optional BoxLite deployment profile (installer/app marketplace/docs path).
- Keep current default behavior unchanged.
- Document compatibility and rollback path.
Minimal integration checklist
- Install path for BoxLite runtime.
- One quick verification command.
- Rollback to existing runtime path.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified. Start by locating the installer, app marketplace, and documentation entry points, then determine where deployment profiles and runtime defaults are defined; done means an optional BoxLite path, a documented verification command, compatibility notes, and rollback guidance without changing existing defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100