Epigomphus camelus
Epigomphus camelus is a species of dragonfly in the family Gomphidae. It is endemic to Costa Rica. Its natural habitats are subtropical or tropical moist lowland forests and rivers. It is threatened by habitat loss.
Epigomphus camelus | |
---|---|
Scientific classification | |
Kingdom: | |
Phylum: | |
Class: | |
Order: | |
Family: | |
Genus: | |
Species: | E. camelus |
Binomial name | |
Epigomphus camelus Calvert, 1905 | |
Sources
- Paulson, D. & von Ellenrieder, N. 2005. Epigomphus camelus. 2006 IUCN Red List of Threatened Species. Downloaded on 9 August 2007.
gollark: I would probably use nginx, because I'm used to it and it has nicer configuration:```nginxhttp { # whatever important configuration you have for all HTTP servers, `nginx.conf` probably ships with some # fallback in case someone visits with an unrecognized Host header server { listen 80 default_server; listen [::]:80 default_server; return 301 http://somedomain$request_uri; } server { listen 80; # you may (probably do) want HTTPS instead, in which case this bit is somewhat different - you need to deal with certs and stuff, and use port 443 - also you should probably add HTTP/2 listen [::]:80; # IPv6 server_name domain1.com; location / { proxy_pass http://backend1:8080/; } } server { listen 80; listen [::]:80; server_name domain2.com; location / { proxy_pass http://backend2:8080/; } }}```
gollark: The reverse-proxy solution is in my opinion the best one, although it would require some config.
gollark: I think LetsEncrypt may not be very happy with that, though.
gollark: Yes, and you can just use a reverse proxy (with "vhosts" or whatever) for that, easy enough.
gollark: I think those are just what some webservers call "doing different things based on the host header".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.