Automatically skip not found hosts when starting container

[FluffyDiscord]

Is your feature request related to a problem? Please describe.
I am migrating to another server. I don't have all services installed yet, but I would like to start nginx-ui to validate and configure what I need before other services. Right now container enters infinite loop when backend isn't reachable. nginx: [emerg] host not found in upstream XXX

Describe the solution you'd like
Monitor nginx startup, if this message shows up, disable that site config and maybe output another warning in logs or show it in the nginx-ui itself.

Describe alternatives you've considered
Manually removing symlinks from the mounted volumes.

Additional context

[0xJacky]

Sorry, automatically deleting the Nginx configuration files directly is not safe. I'm concerned that it might cause production services to be affected due to accidents. Therefore, we won't implement this requirement. Thank you for your suggestion.

[FluffyDiscord]

@0xJacky I am not talking about deleting, but disabling. You are already doing it when nginx-ui is running, you won't enable site config if backend doesn't respond/exist, why can't this be also done while nginx-ui boots up?