I must have been having more basic problems than you. I found LLMs to present the most common solution, and generally the most common way of setting it up is the "right-way", At least for a beginner. Then I'd quiz it on what docker compose environments do, what "ports: ####:####" meant, how I could route one container through another. All very basic stuff. Challenge: ask gpt

what does "ports:

-####:####" mean in a docker compose?

Then tell me it doesn't spit out something a hobbiest could understand, immediately start applying, and is generally correct? Beginners, still verify what gpt spits out.

By the time I wanted to do non-standard stuff I was better equipped with the fundamentals of hobbiest deployment and how to coax an LLM into doing what I needed. It won't write an Nginx config for you, or an ACL file, but with the documentation and an LLM you could teach yourself to write one.

Goes without saying I'd take the output of the LLM to Google for verification, then back to the LLM for a hobbiest's explaination, back to Google for verification... Also, all details are place holders: don't give it your email, api-keys, domains, nothing. Learn to scrub your input there and it'll be a habit here is a bonus too.

Properly made software has great documentation and logs. If you know how to access those logs and read documentation (both skills in themselves)... Not to mention not all software is "properly made" some of it is bare bones and just works(tm). Works it do, absolutely not a criticisms for FOSS projects, I love your stuff keep making it, and I'll keep finding ways to teach myself to use it.