AlamLinux 8.10 部署 LNMP 环境并安装 NextCloud

如果说希望自己的手机可以有一个app自动同步照片到NAS，那NextCloud就是一个不错的选择。虽然服务端确实是臃肿了一些，但是如果只是拿来同步个照片问题不大。
我前前后后折腾了一天，后面又在虚拟机上部署失败了四次，终于算摸索出来了。写一篇博客记录一下折腾过程，供日后参考。

部署目标：

• 目标操作系统：AlmaLinux8.10。
• 使用Nginx作为Web服务器，MariaDB作为数据库，PHP作为后端部署Nextcloud。
• NextCloud本体放在/opt/nextcloud/目录下，数据文件存放在RAID1的硬盘目录/mnt/3T-RAID1/nextcloud_data/下。

前置任务：安装LNMP环境

NextCloud的运行依赖于Nginx(或者Apache)，MariaDB(或者MySQL)，PHP，这些软件一般是部署在Linux上，所以缩写为LNMP环境。如果是经常搞网站的，对这个环境应该挺熟悉的吧，不熟悉就是用宝塔用的（

配置Nginx

安装Nginx：

yum install -y nginx

创建Nginx配置文件/etc/nginx/conf.d/nextcloud.conf：

upstream php-handler {
    server unix:/run/php-fpm/www.sock;
}

# Set the `immutable` cache control options only for assets with a cache busting `v` argument
map $arg_v $asset_immutable {
    "" "";
    default ", immutable";
}


server {
    listen 80;
    listen [::]:80;
    server_name nextcloud.nekopara.uk;

    # Prevent nginx HTTP Server Detection
    server_tokens off;

    # Enforce HTTPS
    return 301 https://$server_name$request_uri;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    # With NGinx >= 1.25.1 you should use this instead:
    # listen 443      ssl;
    # listen [::]:443 ssl;
    # http2 on;
    server_name nextcloud.nekopara.uk;

    # Path to the root of your installation
    root /opt/nextcloud;

    # Use Mozilla's guidelines for SSL/TLS settings
    # https://mozilla.github.io/server-side-tls/ssl-config-generator/
    ssl_certificate     /opt/certs/nekopara.uk.pem;
    ssl_certificate_key /opt/certs/nekopara.uk.key;

    # Prevent nginx HTTP Server Detection
    server_tokens off;

    # HSTS settings
    # WARNING: Only add the preload option once you read about
    # the consequences in https://hstspreload.org/. This option
    # will add the domain to a hardcoded list that is shipped
    # in all major browsers and getting removed from this list
    # could take several months.
    #add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;

    # set max upload size and increase upload timeout:
    client_max_body_size 512M;
    client_body_timeout 300s;
    fastcgi_buffers 64 4K;

    # Enable gzip but do not remove ETag headers
    gzip on;
    gzip_vary on;
    gzip_comp_level 4;
    gzip_min_length 256;
    gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
    gzip_types application/atom+xml text/javascript application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/wasm application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/bmp image/svg+xml image/x-icon text/cache-manifest text/css text/plain text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy;

    # Pagespeed is not supported by Nextcloud, so if your server is built
    # with the `ngx_pagespeed` module, uncomment this line to disable it.
    #pagespeed off;

    # The settings allows you to optimize the HTTP2 bandwidth.
    # See https://blog.cloudflare.com/delivering-http-2-upload-speed-improvements/
    # for tuning hints
    client_body_buffer_size 512k;

    # HTTP response headers borrowed from Nextcloud `.htaccess`
    add_header Referrer-Policy                   "no-referrer"       always;
    add_header X-Content-Type-Options            "nosniff"           always;
    add_header X-Frame-Options                   "SAMEORIGIN"        always;
    add_header X-Permitted-Cross-Domain-Policies "none"              always;
    add_header X-Robots-Tag                      "noindex, nofollow" always;
    add_header X-XSS-Protection                  "1; mode=block"     always;

    # Remove X-Powered-By, which is an information leak
    fastcgi_hide_header X-Powered-By;

    # Set .mjs and .wasm MIME types
    # Either include it in the default mime.types list
    # and include that list explicitly or add the file extension
    # only for Nextcloud like below:
    include mime.types;
    types {
        text/javascript mjs;
    application/wasm wasm;
    }

    # Specify how to handle directories -- specifying `/index.php$request_uri`
    # here as the fallback means that Nginx always exhibits the desired behaviour
    # when a client requests a path that corresponds to a directory that exists
    # on the server. In particular, if that directory contains an index.php file,
    # that file is correctly served; if it doesn't, then the request is passed to
    # the front-end controller. This consistent behaviour means that we don't need
    # to specify custom rules for certain paths (e.g. images and other assets,
    # `/updater`, `/ocs-provider`), and thus
    # `try_files $uri $uri/ /index.php$request_uri`
    # always provides the desired behaviour.
    index index.php index.html /index.php$request_uri;

    # Rule borrowed from `.htaccess` to handle Microsoft DAV clients
    location = / {
        if ( $http_user_agent ~ ^DavClnt ) {
            return 302 /remote.php/webdav/$is_args$args;
        }
    }

    location = /robots.txt {
        allow all;
        log_not_found off;
        access_log off;
    }

    # Make a regex exception for `/.well-known` so that clients can still
    # access it despite the existence of the regex rule
    # `location ~ /(\.|autotest|...)` which would otherwise handle requests
    # for `/.well-known`.
    location ^~ /.well-known {
        # The rules in this block are an adaptation of the rules
        # in `.htaccess` that concern `/.well-known`.

        location = /.well-known/carddav { return 301 /remote.php/dav/; }
        location = /.well-known/caldav  { return 301 /remote.php/dav/; }

        location /.well-known/acme-challenge    { try_files $uri $uri/ =404; }
        location /.well-known/pki-validation    { try_files $uri $uri/ =404; }

        # Let Nextcloud's API for `/.well-known` URIs handle all other
        # requests by passing them to the front-end controller.
        return 301 /index.php$request_uri;
    }

    # Rules borrowed from `.htaccess` to hide certain paths from clients
    location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/)  { return 404; }
    location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console)                { return 404; }

    # Ensure this block, which passes PHP files to the PHP process, is above the blocks
    # which handle static assets (as seen below). If this block is not declared first,
    # then Nginx will encounter an infinite rewriting loop when it prepends `/index.php`
    # to the URI, resulting in a HTTP 500 error response.
    location ~ \.php(?:$|/) {
        # Required for legacy support
        rewrite ^/(?!index|remote|public|cron|core\/ajax\/update|status|ocs\/v[12]|updater\/.+|ocs-provider\/.+|.+\/richdocumentscode(_arm64)?\/proxy) /index.php$request_uri;

        fastcgi_split_path_info ^(.+?\.php)(/.*)$;
        set $path_info $fastcgi_path_info;

        try_files $fastcgi_script_name =404;

        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $path_info;
        fastcgi_param HTTPS on;

        fastcgi_param modHeadersAvailable true;         # Avoid sending the security headers twice
        fastcgi_param front_controller_active true;     # Enable pretty urls
        fastcgi_pass php-handler;

        fastcgi_intercept_errors on;
        fastcgi_request_buffering off;

        fastcgi_max_temp_file_size 0;
    }

    # Serve static files
    location ~ \.(?:css|js|mjs|svg|gif|ico|jpg|png|webp|wasm|tflite|map|ogg|flac)$ {
        try_files $uri /index.php$request_uri;
        # HTTP response headers borrowed from Nextcloud `.htaccess`
        add_header Cache-Control                     "public, max-age=15778463$asset_immutable";
        add_header Referrer-Policy                   "no-referrer"       always;
        add_header X-Content-Type-Options            "nosniff"           always;
        add_header X-Frame-Options                   "SAMEORIGIN"        always;
        add_header X-Permitted-Cross-Domain-Policies "none"              always;
        add_header X-Robots-Tag                      "noindex, nofollow" always;
        add_header X-XSS-Protection                  "1; mode=block"     always;
        access_log off;     # Optional: Don't log access to assets
    }

    location ~ \.(otf|woff2?)$ {
        try_files $uri /index.php$request_uri;
        expires 7d;         # Cache-Control policy borrowed from `.htaccess`
        access_log off;     # Optional: Don't log access to assets
    }

    # Rule borrowed from `.htaccess`
    location /remote {
        return 301 /remote.php$request_uri;
    }

    location / {
        try_files $uri $uri/ /index.php$request_uri;
    }
}

配置文件中的主机名要改为你实际的域名，证书位置改为你实际证书放置的目录。
测试没问题后，就启动Nginx：

nginx -t
systemctl enable --now nginx

配置PHP

安装PHP以及NextCloud需要的模块，由于需要使用PHP8.2，所以需要添加Remi仓库后再安装：

yum install https://rpms.remirepo.net/enterprise/remi-release-8.rpm -y
dnf module reset php -y
dnf module enable php:remi-8.2 -y
dnf install -y php php-cli php-gd php-mbstring php-intl php-pecl-apcu php-mysqlnd php-opcache php-json php-zip

配置/etc/php.ini，查找配置并修改为以下内容：

memory_limit = 512M
upload_max_filesize = 500M
post_max_size = 600M 
max_execution_time = 300

启动PHP：

systemctl enable --now php-fpm

配置MariaDB

安装MariaDB：

yum install mariadb -y

安装完成后，启动数据库，设置NextCloud的数据库：

systemctl enable --now mariadb
mysql -u root -p

默认没有密码，直接回车就进数据库了，然后开始配置：

CREATE DATABASE netxcloud_db;
CREATE USER nextcloud_user@localhost IDENTIFIED BY 'nextcloud_passwd';
GRANT ALL PRIVILEGES ON netxcloud_db.* TO nextcloud_user@localhost;
FLUSH PRIVILEGES;

数据库名称，用户，密码，自己看着改。

至此，前置任务已完成，让我们来开始安装NextCloud。

安装NextCloud

下载NextCloud并解压，我用地是28.0.14版本：

cd /opt
wget https://download.nextcloud.com/server/releases/nextcloud-28.0.14.zip
unzip nextcloud-28.0.14.zip

配置SELinux允许NextCloud进行文件读写操作：

semanage fcontext -a -t httpd_sys_rw_content_t "/opt/nextcloud(/.*)?"
semanage fcontext -a -t httpd_sys_rw_content_t '/opt/nextcloud/data(/.*)?'
semanage fcontext -a -t httpd_sys_rw_content_t '/opt/nextcloud/config(/.*)?'
semanage fcontext -a -t httpd_sys_rw_content_t '/opt/nextcloud/apps(/.*)?'
semanage fcontext -a -t httpd_sys_rw_content_t '/opt/nextcloud/.htaccess'
semanage fcontext -a -t httpd_sys_rw_content_t '/opt/nextcloud/.user.ini'
semanage fcontext -a -t httpd_sys_rw_content_t '/opt/nextcloud/3rdparty/aws/aws-sdk-php/src/data/logs(/.*)?'
restorecon -Rv '/opt/nextcloud/'

设置必要的SELinux规则：

setsebool -P httpd_can_connect_ldap on
setsebool httpd_unified on
setsebool -P httpd_can_network_connect_db on
setsebool -P httpd_can_network_connect on
setsebool -P httpd_can_network_memcache on
setsebool -P mysql_connect_http on

设置文件权限：

chown -R apache:apache /opt/nextcloud
chmod -R 775 /opt/nextcloud

同理，设置数据目录权限：

semanage fcontext -a -t httpd_sys_rw_content_t "/mnt/3T-RAID1/nextcloud_data(/.*)?"
restorecon -Rv /mnt/3T-RAID1/nextcloud_data
chown -R apache:apache /mnt/3T-RAID1/nextcloud_data
chmod -R 775 /mnt/3T-RAID1/nextcloud_data

配置NextCloud

在浏览器输入你的域名，按理来说应该可以正常打开NextCloud的安装界面，按照提示设置用户名，密码，文件目录，数据库，安装完成后就应该是可以正常使用的了。