Views
No views yet
| File | Purpose |
|---|---|
miner.py | Defines the ML model type(s), orchestration, and all pre/postprocessing logic. |
config.yml | Specifies machine configuration (e.g., GPU type, memory, environment variables). |

config.yml and miner.py and saving it into your Huggingface Repo, you will want to test it works locally.scorevision/chute_tmeplate/turbovision_chute.py.j2 as a python file called my_chute.py and fill in the missing variables:1HF_REPO_NAME = "{{ huggingface_repository_name }}"
2HF_REPO_REVISION = "{{ huggingface_repository_revision }}"
3CHUTES_USERNAME = "{{ chute_username }}"
4CHUTE_NAME = "{{ chute_name }}"chutes build my_chute:chute --local --publicCHUTE_NAME) and enter itdocker run -p 8000:8000 -e CHUTES_EXECUTION_CONTEXT=REMOTE -it <image-name> /bin/bashchutes run my_chute:chute --dev --debug1curl -X POST http://localhost:8000/health -d '{}'
2curl -X POST http://localhost:8000/predict -d '{"url": "https://scoredata.me/2025_03_14/35ae7a/h1_0f2ca0.mp4","meta": {}}'chutes chutes listchutes chutes delete <chute-id>chutes images listchutes images delete <chute-image-id>--no-commit. You can also specify a past huggingface revision to point to using --revision and/or the local files you want to upload to your huggingface repo using --model-path)sv -vv pushchutes chutes list or chutes chutes get <chute-id> if you already know its id). Note: Warming up can sometimes take a while but if the chute runs without errors (should be if you've tested locally first) and there are sufficient nodes (i.e. machines) available matching the config.yml you specified, the chute should become hot 🔥!chutes warmup <chute-id>1curl -X POST https://<YOUR-CHUTE-SLUG>.chutes.ai/health -d '{}' -H "Authorization: Bearer $CHUTES_API_KEY"
2curl -X POST https://<YOUR-CHUTE-SLUG>.chutes.ai/predict -d '{"url": "https://scoredata.me/2025_03_14/35ae7a/h1_0f2ca0.mp4","meta": {}}' -H "Authorization: Bearer $CHUTES_API_KEY"sv -vv run-once