Maybe document subfolder based access (example)

[joshtrichards]

There's a distinction between a subfolder installation of Nextcloud (i.e. somewhere under the docroot) and merely making Nextcloud reachable via a subfolder style URL (https://domain.tld/nextcloud). The former is not something relevant to this image, while the latter is a config matter (including reverse proxy integration)

There's probably an opportunity to improve upstream documentation and/or our docs & examples here at the Docker level.

I mention this so that maybe we can finally close out the following issues:

• Run Nextcloud from Subdirectory #401
• Trick to run docker nextcloud fpm with nginx in a sub directory #1919
• Using the fpm image in a subdirectory of the proxy #2187
• Question: NextCloud available in subfolder #1047

[tzerber]

Current setup:
latest fpm NC running at nextcloud_app:80, config.php allowing the domains below. Proxy listening on https://x.domain.com and NC working fine, then added secondary https://y.domain.com pointing to another working service(not nextcloud). Then added location https://y.domain.com/nextcloud pointing to nextcloud_app:80 to the proxy, and upon opening said url NC forwarded me to the / of the y.domain.com. I know apache rewrite can do this kind of magic, but out of the box it's not working here, so I doubt only proxy config is enough. Probably custom config for fpm variant and custom rewrite config for apache variants because nginx/apache approach to this is different.