Further to #437 which was closed as "completed", disregarding the actual point of the issue / request:
The purposes of a component like Nginx are well understood, and can all be achieved by Nginx or a functionally equivalent service running in a container separate from seahub/seaf-server, or directly on the host machine, or even elsewhere in the network.
Such a service could direct traffic to standalone seahub and seaf-server containers as well as serve the static files (which don't need to be containerised in the first place, but even so are easily mounted onto the host filesystem).
In fact, any deployment that includes other web services alongside Seafile will have to run a reverse-proxy in front of them, so bundling Nginx with Seafile does nothing but introduce a redundant configuration layer and network hop. It is also bad containerisation practice.
Further to #437 which was closed as "completed", disregarding the actual point of the issue / request:
The purposes of a component like Nginx are well understood, and can all be achieved by Nginx or a functionally equivalent service running in a container separate from seahub/seaf-server, or directly on the host machine, or even elsewhere in the network.
Such a service could direct traffic to standalone seahub and seaf-server containers as well as serve the static files (which don't need to be containerised in the first place, but even so are easily mounted onto the host filesystem).
In fact, any deployment that includes other web services alongside Seafile will have to run a reverse-proxy in front of them, so bundling Nginx with Seafile does nothing but introduce a redundant configuration layer and network hop. It is also bad containerisation practice.