Open models,on a machine you rent
The Ollama server, with a chat page in front of it.The same port serves the API your own tools call.
$ dxflow workflow create --identity ollama hub://ollama --start --link
Pick a model,and start talking
A chat page over the Ollama server, with the API alongside it.
Pick an installed model and watch the answer stream as it comes.
The Ollama HTTP API sits at /api, behind that same one password.
A GPU is in the definition, and Ollama loads as many layers into VRAM as fit.
A password, a model,and the card
Who gets in, what is waiting when they do, and whether it answers on the GPU.
$ dxflow workflow start ollama --override env.app.PASSWORD=something-long
$ dxflow workflow start ollama --override env.app.STARTUP_MODEL=llama3.1:8b --link
$ dxflow workflow start ollama --override resource.app.gpu= --link
One port,two ways in
The chat page and the API share 8080 and one credential.
One port,one credential
The chat page and the HTTP API are the same door, and the same password opens both.
A React app behind nginx proxies to Ollama on 11434. The UI calls it under /ollama/api, and the standard API sits at /api on the same 8080.
Ollama offloads as many layers as fit into VRAM — nvidia-smi shows it while a model answers. Drop the gpu resource and it falls back to CPU without being told, which suits the small models.
ollama pull from a terminal adds models, and they land on the volume rather than back in the image.
Pulled once,then it stays
Ollama arrives as one image. This is what comes down the first time, and what the disk should have free for it.
What it wants,is what it needs
The definition asks for 4 cores and 8 GB, and the image wants all of it. A start given --fit still caps each step to whatever the machine actually has.
Machines that fit it
Ollama asks for 4 cores and 8 GB, with an NVIDIA GPU. Cheapest first.