thePR0M3TH3AN/TORCH
1
0 Fork 0
mirror of https://github.com/PR0M3TH3AN/TORCH.git synced 2026-10-27 07:51:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document pinned-commit TORCH installs and verification checks

Browse Source
This commit is contained in:
thePR0M3TH3AN committed 2026-02-25 15:14:07 -05:00
1 parent 4da9753812
commit b5023799d3
2 files changed
+9 -5
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+8 -4
View File
@@ -23,7 +23,7 @@ Prerequisites:
First 5 minutes:
```bash
npm install https://github.com/PR0M3TH3AN/TORCH/archive/refs/heads/main.tar.gz \
npm install https://github.com/PR0M3TH3AN/TORCH/archive/<commit-sha>.tar.gz --force \
&& npx --no-install torch-lock init
# sanity check (optional, but recommended)
@@ -34,13 +34,14 @@ npx --no-install torch-lock dashboard --port 4173 --host 127.0.0.1
```
> TORCH is distributed from GitHub tarballs and is not currently published to the npm registry.
> Use pinned commit tarballs (`archive/<commit-sha>.tar.gz`) for repeatable installs. Avoid `refs/heads/main.tar.gz` for production rollouts.
### Upgrade TORCH In An Existing Repository
Use this when the repository already has a `torch/` directory:
```bash
npm install https://github.com/PR0M3TH3AN/TORCH/archive/refs/heads/main.tar.gz
npm install https://github.com/PR0M3TH3AN/TORCH/archive/<commit-sha>.tar.gz --force
npx --no-install torch-lock update --force
npm install --prefix torch
npm run --prefix torch lock:check:daily -- --json --quiet
@@ -49,7 +50,7 @@ npm run --prefix torch lock:check:daily -- --json --quiet
Use this for first-time setup in a repository without `torch/`:
```bash
npm install https://github.com/PR0M3TH3AN/TORCH/archive/refs/heads/main.tar.gz
npm install https://github.com/PR0M3TH3AN/TORCH/archive/<commit-sha>.tar.gz --force
npx --no-install torch-lock init --force
npm install --prefix torch
npm run --prefix torch lock:check:daily -- --json --quiet
@@ -58,7 +59,7 @@ npm run --prefix torch lock:check:daily -- --json --quiet
One-liner (auto-detect existing vs new install):
```bash
npm install https://github.com/PR0M3TH3AN/TORCH/archive/refs/heads/main.tar.gz && \
npm install https://github.com/PR0M3TH3AN/TORCH/archive/<commit-sha>.tar.gz --force && \
if [ -d torch ]; then npx --no-install torch-lock update --force; else npx --no-install torch-lock init --force; fi && \
npm install --prefix torch && \
npm run --prefix torch lock:check:daily -- --json --quiet
@@ -71,6 +72,9 @@ Post-upgrade validation checklist:
3. Confirm host install dependencies exist: `test -d torch/node_modules`.
4. Run one scheduler cycle (expected to fail on Linux simulation due to artifact checks, but not due to missing config/handoff):
- `AGENT_PLATFORM=linux npm run --prefix torch scheduler:daily`
5. Verify installed package matches expected resolver behavior:
- `rg -n "cwdBaseName === 'torch' && fs.existsSync\\(parentPath\\)" node_modules/torch-lock/src/torch-config.mjs`
- `rg -n "cwdBaseName === 'torch' && fs.existsSync\\(parentPath\\)" torch/src/torch-config.mjs`
## Development
docs/removal.md
+1 -1
View File
@@ -151,5 +151,5 @@ grep '"torch:' package.json
If you want to re-install TORCH later:
```bash
npm install https://github.com/PR0M3TH3AN/TORCH/archive/refs/heads/main.tar.gz && npx torch-lock init
npm install https://github.com/PR0M3TH3AN/TORCH/archive/<commit-sha>.tar.gz --force && npx torch-lock init
```