Comment on Is anyone self-hosting their own AI?
panda_abyss@lemmy.ca 5 days ago
I run lemonade on my strix halo box, I change the models I use, but the qwens are pretty good.
I access it via Tailscale on my phone, then I have a page I can use. The Lemonade interface forces you into the app, so you’ll want some other interface for your LLMs, as the app is junk.
I used to run llama.cpp and llama swap, but lemonade combines them and makes managing different ai backends easier.
Seralth@piefed.seralth.com 5 days ago
I’ve been eyeing lemonade as I am on llama and swap my self. How much of a pita was the migration. I’m a lazy bastard.
MalReynolds@slrpnk.net 5 days ago
Lemonade is pretty good, especially for AMD GPUs and the lazy, but it’s pretty opinionated (like ollama but not as toxic) and it’s not easy to directly control llama-server parameters. It feels a bit commercial / we want to IPO.
Seeing as you already have your parameters, llama-swap might be a better fit, lets you configure llama-server directly in a yaml, and switch between them. You can even have multiple versions of the same model (e.g. thinking or not, try out different parameters) and change without reloading.
Both work fine with e.g. Open WebUI and Pi (lemonade its own integration and llama-server needs an extension).
panda_abyss@lemmy.ca 4 days ago
If you update the model json you can pass through almost any parameters you want
It is an extra step though
MalReynolds@slrpnk.net 4 days ago
Good to know, it’s been a while since I played with it and the docs were sparse.
panda_abyss@lemmy.ca 5 days ago
I pointed lemonade at my llama.cpp model folder but it uses json files to configure them. I think it was fine for importing them or you could have an agent write them for you. After that you can manage models inside the app
Overall it wasn’t a huge deal, it’s easier than managing llama.cpp directly with rocm updates.