GPU count, password hints

[andi-at-1]

Hi,

At fist thanks for your great work, it really helps me getting into this stuff!

I noticed two things:

• If you have more gpus it will bypass only one, i suggest to change that in docker-compose-yml, ollama-gpu -> count:all

• supabase is picky about passwords starting with special chars. Also changing any other of the "changeme"-keys than you mentioned (like vault_enc_key or logflare keys) lead to some supabase containers not starting up. that costed me some hours to figure out...

greetings

[coleam00]

Thanks for these couple of tips!

1. The n8n team in their original starter kit excluded count:all and I'm thinking it's because you might want multiple containers each running a separate Ollama instance on a GPU for parallel processing. But only some use cases would want that, others you would want all the GPU power you have. So I'll have to think about adding this or maybe making it another profile.

2. Do you know what special characters specifically? I know the "@" symbol for sure isn't allowed and I actually updated the README troubleshooting section to call that out. Not sure what else isn't allowed though.

[andi-at-1]

1. Yes, i mean that was pretty straight forward to overcome, just a hint where to change the config seems good enough

2. # : " are also not the best, and quite sure there are more. Haven´t tried more and tested that just with the postgres password. It leads to instant crash or supabases-analytics not starting. That also happens if the special char is somewhere in the password string, but i dunno how to escape the sequence. I run ubuntu 24.10, maybe that differs on windows.

Anyway, enough fun with passwords, time to watch your new video 😄 Keep up your great work here!