Keep weights out of Gitea

This commit is contained in:
2026-06-30 11:53:46 +08:00
parent 98abafa7cc
commit 69f9a8e29b
5 changed files with 28 additions and 25 deletions

View File

@@ -50,15 +50,16 @@ cd Seg_Data_Server_Net
python scripts/sync_weights.py --mode copy --hash
```
For repository storage, use Git LFS or a Gitea release/package store:
Weights must remain local to the deployment machine. Do not push `.pt`, `.pth`,
`.onnx`, `.engine`, or `weights/files/` into Gitea. The repository stores only
code, `weights/manifest.json`, and helper scripts. Before pushing, run:
```bash
git lfs install
git lfs track "*.pt" "*.pth" "*.onnx" "*.engine"
scripts/check_no_weight_git.sh
```
If Git LFS is not available on the host or server, keep the copied weights on
the deployment volume and commit only `weights/manifest.json`.
If a deployment machine needs weights, run the sync command locally on that
machine after cloning the code.
## Job Types
@@ -76,4 +77,3 @@ The backend exposes all current Seg capabilities as job types. Examples:
Use `GET /api/catalog` to inspect supported models, algorithms, datasets, and
task types discovered from the existing `Seg/` workspace.