Allowed hosts config

[neolefty]

Support allowed_hosts when running via docker compose, to avoid this error on development servers:

Related PR — Documentation update: SpeciesFileGroup/taxonworks_doc#108

[LocoDelAssembly]

This would actually allow to apply on ANY environment, not just development? It ADDS more hosts rather than providing the list of allowed hosts?

Not sure what the interaction of this and production deployments would be, looks that config.hosts is undefined and fully managed by nginx/phusion passenger:

root@tw-sandcastle-7bc8d6956b-wjkbh:/app# RAILS_ENV=production bundle exec rails c
Loading production environment (Rails 7.2.2.1)
3.4.2 :001 > TaxonWorks::Application.configure { puts config.hosts }
 => nil 

[neolefty]

This would actually allow to apply on ANY environment, not just development? It ADDS more hosts rather than providing the list of allowed hosts?

Not sure what the interaction of this and production deployments would be, looks that config.hosts is undefined and fully managed by nginx/phusion passenger:

root@tw-sandcastle-7bc8d6956b-wjkbh:/app# RAILS_ENV=production bundle exec rails c
Loading production environment (Rails 7.2.2.1)
3.4.2 :001 > TaxonWorks::Application.configure { puts config.hosts }
 => nil 

I only tested this under docker compose — that's what I meant by "development servers". I assumed a production server would be running under kubernetes.

[LocoDelAssembly]

Note to self

Looks production env does not include the required middleware for above problem to occur:

 ✘ hernan@9900k  ~/Projects/taxonworks   development ±  RAILS_ENV=development rails middleware | grep -i host
use ActionDispatch::HostAuthorization
 hernan@9900k  ~/Projects/taxonworks   development ±  RAILS_ENV=production rails middleware | grep -i host
 ✘ hernan@9900k  ~/Projects/taxonworks   development ± 