时间:2021-07-01 10:21:17 帮助过:22人阅读
需要做到两个WordPress博客权限上互相安全隔离。
大致步骤:
以下记录步骤, 只针对blog1, blog2和blog1配置完全一样, 改其中个别字段即可:
创建两个系统服务用户:
因为是作为服务用户, 所以shell需要设置为 /sbin/nologin禁止登录; 另外, 不需要生成home目录.
$ useradd -u 1201 -s /sbin/nologin -d /dev/null blog1
MySQL新建用户, 数据库, 配置权限:
数据库级别权限隔离, 且各用户只有自己相关数据库的权限.
CREATE DATABASE dbblog1;CREATE USER 'blog1'@'localhost' IDENTIFIED BY '';GRANT ALL ON dbblog1.* TO 'blog1'@'localhost';FLUSH PRIVILEGE;
WordPress压缩包解压, 更改文件属主:
属主更改是为了PHP-FPM有权限读写站点文件.
$ tar zxvf wordpress-4.4.2-zh_CN.tar.gz$ mv wordpress blog1$ chown -R blog1 blog1$ ls -alhd blog1drwxr-xr-x 5 blog1 nogroup 4.0K Feb 3 08:13 blog1
PHP-FPM 配置:
首先修改主配置 /etc/php/fpm-php5.6/php-fpm.conf:
注释掉 Pool Definitions中的所有配置项, 即去掉默认的 wwwPool; 开启 include项:
; Include one or more files. If glob(3) exists, it is used to include a bunch of; files from a glob(3) pattern. This directive can be used everywhere in the; file.; Relative path can also be used. They will be prefixed by:; - the global prefix if it's been set (-p argument); - /usr/lib64/php5.6 otherwiseinclude=/etc/php/fpm-php5.6/etc/fpm.d/*.conf
每个web site一个独立的php-fpm配置(具体解释看默认的配置文件):
$ cat /etc/php/fpm-php5.6/etc/fpm.d/blog1.conf[blog1]user = blog1 ; php-fpm子进程的uidgroup = nogrouplisten = /var/run/php-fpm-blog1.socklisten.owner = nginx ; sock通信文件的属主, 和nginx通信listen.group = nginx ; sock通信文件的属组, 和nginx通信listen.mode = 0660pm = dynamicpm.max_children = 5pm.start_servers = 2pm.min_spare_servers = 1pm.max_spare_servers = 3chroot = /var/www/blog1chdir = /
配置 user是为了控制权限, 读写站点文件.
配置 listen.owner/group是为了nginx有权限和php-fpm通信.
设置 chroot到站点目录下, 限制最小访问权限. 命令 pwdx可以查看指定进程的当前工作目录.
$ ps aux | grep phproot 5646 0.0 0.3 247836 7192 ? Ss 14:55 0:00 php-fpm: master process (/etc/php/fpm-php5.6/php-fpm.conf)blog1 5647 0.0 0.6 247944 13884 ? S 14:55 0:00 php-fpm: pool blog1blog1 5648 0.0 0.6 247812 13192 ? S 14:55 0:00 php-fpm: pool blog1blog2 5649 0.0 1.4 251840 29756 ? S 14:55 0:00 php-fpm: pool blog2blog2 5650 0.0 0.3 247812 6636 ? S 14:55 0:00 php-fpm: pool blog2root 10071 0.0 0.1 112700 2100 pts/4 S+ 15:52 0:00 grep --color php$ pwdx 56475647: /var/www/blog1
Nginx配置:
server { listen 80; server_name blog1.tankywoo.com; index index.php; access_log /var/log/nginx/blog1_log main; error_log /var/log/nginx/blog1_error_log; root /var/www/blog1/; location ~ .php$ { try_files $uri =404; fastcgi_pass unix:///var/run/php-fpm-blog1.sock; include fastcgi.conf; fastcgi_param SCRIPT_FILENAME /$fastcgi_script_name; }}
注意 fastcgi_param配置. 如果是默认的:
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
则PHP-FPM(fastcgi)读取index.php, 即/var/www/blog1/inex.php.
而因为PHP-FPM配置了chroot, 所以这个目录是当对于chroot后的目录.
即实际读取/var/www/blog1/var/www/blog1/index.php
中间过程中, 遇到几个报错:
php-fpm log:
php-fpm chroot FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream
找不到php文件, 原因就是fastcgi的 SCRIPT_FILENAME配置之前没配.
数据库连接失败
原因是WordPress默认是通过socket连接数据库, 而此时web site是chroot的, 所以没法找到sock文件.
方法1是把sock文件mount进去:
$ mkdir -p /var/www/blog1/var/run/mysqld$ mount --bind /var/run/mysqld /var/www/blog1/var/run/mysqld
不过此方法不够完美。
方法2就是将WordPress改为通过tcp链接MySQL, wp-config.php 增加:
define('DB_HOST', '127.0.0.1');
参考链接: