It would be really helpful if the example of a CentOS Configuration Walkthrough would directly contain a working and secure apache configuration.
Just the Reference to the detailed apache config is not adequate and too easy to overlook and users will end up with an unsecure and broken config. This could lead to the usual htaccess not working questions.
So here is my proposal :)
- Changed `try_files` for `/.well-known` to allow URIs that we don't handle and not pass them to our front-end controller
- Changed rule to match `/nextcloud/*` from regex rule to equivalent prefix rule
You probably are correct on NGINX optimizing groups with unused captures into non-capturing groups, but unless we know for sure/see documentation I think it is best we are explicit.
I think we mostly agree on these, grouping them for easy merging.
Creating a new branch is giving me an error for some reason, so I will commit directly. If necessary we can always revert.
Not sure why the needed to be built manually? But a fresh install with remi 7.4 gives `php-pecl-imagick-3.4.4-10.el8.remi.7.4` and `php-pecl-redis5-5.3.1-1.el8.remi.7.4` respectively.
I'm somewhat new to the Linux world and was doing this on a fresh install of Ubuntu. I needed to run the apt update command in order to fetch package information for the following commands and get them to run/install the necessary packages.
I also needed to start the MySQL server instance before I was able to run the listed commands.
- Removed `index.htm` from `index` directive
- Rewrote `DavClnt` user agent handler using `location =` and `return`, rather than `rewrite`
- Removed block which prevents access to hidden files; incorporated rule to prevent access to root-level hidden folders into existing regex rule, as in `.htaccess`
- Removed `$uri/` from `try_files` directives for static files
Signed-off-by: Jivan Pal <jivan.pal@gmail.com>
After inspecting the Nginx configs currently seen at [ https://docs.nextcloud.com/server/19/admin_manual/installation/nginx.html ], I have notice that they are very redundant in some areas, and handle specific paths in special ways which are not needed, and which run the risk of needing to become more specific down the road if NextCloud adds new features, as well as not handling all static filetypes. I have reworked the configs from scratch by directly adapting the `.htaccess` files, and this is the result. Comments are included in the file to give rationale/explanation for why things are written in this new way, and if the maintainers decide to accept this pull request, I will leave it up to them to decide whether to include these expository comments upstream.
Signed-off-by: Jivan Pal <jivan.pal@gmail.com>
That link includes details for how to install snapd if necessary. Also
add a brief blurb about what the snap actually is.
Signed-off-by: Kyle Fazzari <kyrofa@ubuntu.com>
This documentation has been outdated since Ubuntu 18.04 LTS (mysql/mariadb don't prompt for a root password, so you need to create a Nextcloud user), but it doesn't work on Ubuntu 20.04 LTS because it uses explicit PHP version numbers and it omits some recommended PHP modules for Nextcloud Hub 18 and 19. I've updated the instructions to run on Ubuntu 20.04 LTS and have tested each step.
This page now leaves a new Ubuntu 20.04 LTS system in a state to continue the "Installation on Linux" steps starting with configuring Apache2 without errors.
Signed-off-by: Nathan Haines <nhaines@ubuntu.com>
