za0 Indigo still 'touches'/resaves the hosts file
Wow, it should definitely not be doing that. Thanks for noticing it.
za0 it doesn't observe for changes on source files, so it doesn't see changes that Indigo makes when a stack is activated/deactivated
I'm a bit unsure how you would typically use Gas Mask during development (eg previously with Docker). Would you not have a hand-built hosts file somewhere containing your development domains, and then tell Gas Mask to include that file in your
/etc/hosts, perhaps with its "combined files" feature? I guess that's a similar process to how you could do it now, either with Indigo's generated
~/.indigo/hosts file or with one you hand-build, containing your requisite IPv6 entries?
za0 using ~/.indigo/hosts to help manage also doesn't work
Let me know if there's definitely no possible way for it to help you. I lean towards removing that functionality if it's useless.
za0 yes some of these are localhost overrides to real domain names
I won't pretend to understand the complexities you're dealing with here (external auth stuff) 😮 However it sounds like a very specific use-case, so not something Indigo should be doing directly, but definitely something it would ideally enable (my own usage of Indigo is full of similar oddities.) It sounds like you need two things:
- you need IPv6 hosts file entries for each domain
- nginx reverse proxy site definitions should also listen on IPv6 (or just on the port as you said earlier).
The latter should be possible with overrides.
For the IPv6 hosts entries, my hope is you can hard-code a hosts file somewhere and turn it on or off (ie include it or not) using Gas Mask? Another option might be to add a stack which simply serves your custom hosts file over http, for Gas Mask to access.