sortedcord / sortedcord/bootstrap
Improve Local Development and Framework Testing
Open
@sortedcord is already working on this.
Since Jun 28, 2026.
enhancement
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Bootstrap has 3 execution modes:
- Remote/Production: b.sh auto-updates from the Git server, routes.sh downloads tool scripts via curl
- Installed-local: bootstrap.sh detects a repo checkout and copies files to .config/bootstrap
- Dev mode: You rerun ./bootstrap.sh after every edit to re-copy files then test with b
The issues this causes is that:
- 24-hour auto update in b.sh can overwrite local copy with remote files mid session (Auto update system subject to overhaul #2)
- There is no way to test a single tool in isolation as
b <tool>bootstraps the entire routing + rollback + registry. - Dev testing modifies the actual installation of bootstrap on the system (
~/.local/state/bootstrap/registry.json,history.json, etc). In other words, there is no sandbox and you cannot test install+uninstall cylces without polluting the live system installation. - Currently there is no system for executing dry-run or check modes that help validate that a tool script parses correctly > calls the right helpers > produces the right
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.