GitLab

The APIs we query are optimistic on free space, and windows pages
VRAM, so we don't have to wait to see reported usage recover on unload

This reverts commit 0fec3525.

Make sure the first GPU has the most free space

* rename `--quantization` to `--quantize`

* backwards

* Update api/types.go
Co-authored-by: Michael Yang <mxyng@pm.me>

---------
Co-authored-by: Michael Yang <mxyng@pm.me>

* dont clamp ctx size in `PredictServerFit`

* minimum 4 context

* remove context warning

Ensure the runners are terminated

The GPU drivers take a while to update their free memory reporting, so we need
to wait until the values converge with what we're expecting before proceeding
to start another runner in order to get an accurate picture.

This cleans up the logging for GPU discovery a bit, and can
serve as a foundation to report GPU information in a future UX.

* Add preflight OPTIONS handling and update CORS config

- Implement early return with HTTP 204 (No Content) for OPTIONS requests in allowedHostsMiddleware to optimize preflight handling.

- Extend CORS configuration to explicitly allow 'Authorization' headers and 'OPTIONS' method when OLLAMA_ORIGINS environment variable is set.

* allow auth, content-type, and user-agent headers

* Update routes.go

- FROM /path/to/{safetensors,pytorch}
- FROM /path/to/fp{16,32}.bin
- FROM model:fp{16,32}

The model processing was recently changed to be deferred but
this test scenario hadn't been adjusted for that change in behavior.

This moves all the env var reading into one central module
and logs the loaded config once at startup which should
help in troubleshooting user server logs

This also bumps up the default to be 50 queued requests
instead of 10.

This gives us more headroom on the scheduler tests to tamp
down some flakes.