Hot answers tagged

2

You will find people from both camps (terminating TLS as soon as possible vs terminating TLS in the application code) but it's not as serious as for example tabs vs spaces. The benefit of terminating TLS by reverse proxy is that application developer does not have to implement TLS in the application itself - possibly introducing bugs. Another benefit ...


1

I suggest you mount your conf file as a volume: docker run -v nginx.conf:/etc/nginx/nginx.conf .... This way you can easily change the file outside the container and then just restart the container. If you change your config file inside the container and then you should have to restart nginx to pick-up the changes. At that point your container will stop ...


1

Oops, turns out I just have to remove the line listen [::]:443 ssl ipv6only=on; and it works. it's leftover from running NGINX certbot, I thought that was important


1

All my searches for a term brought me to conclude that the general term either for one Apache virtual host file or a constellation of Nginx block files (each containing at least one block) is just that --- a virtual host. Per project; either the virtual host (entity) is a single file or a combination of files, and that's true if the webserver software is ...


1

Problem is in resources - I see that each app container has own nginx instance, and server (VPS) must have global nginx, working as reverse proxy for containers. Generally speaking yes, this is how this sort of thing goes. It's more of an issue for PHP than other languages because PHP doesn't really have a standalone application server, but instead is ...


1

I found the problem it is unrelated. The index.html file itself was the 'directory access is forbidden


1

As per this docker documentation the copy instruction may have multiple sources but only one destination. Your first copy is coping two file /etc/passwd and /etc/group to /etc.


Only top voted, non community-wiki answers of a minimum length are eligible