分类目录归档：Wordpress&Typecho

Cloudflare 301 域名跳转

老域名mlife.work因为不想续费了，还有半年到期，不想续费了，要提早做好迁移，保持自己在搜索引擎的搜索优先级，需要做好301跳转，让他们知道自己换地方了。

因为cloudflare有免费的CDN加速，所以很早就把域名解析过去了，但是看了看官方好像没有提供DNS 301跳转的选项，但是有类似的解决方案，参考这个链接：

https://support.cloudflare.com/hc/en-us/articles/200172286-How-do-I-perform-URL-forwarding-or-redirects-with-Cloudflare-

范例：

Forwarding examples:

Example forwarding to Google+:

Imagine you have a Google+ profile and you want to make it easy for anyone coming to get to simply by going to a URL like:

    *www.example.com/+

    *example.com/+

This pattern will match:

    http://example.com/+
    http://www.example.com/+
    https://www.example.com/+
    https://blog.example.com/+
    https://www.blog.example.com/+
    Etc...

It will not match:

    http://www.example.com/blog/+  [extra directory before the +]
    http://www.example.com+  [no trailing slash]

Forwarding examples:

Example forwarding to Google+:

Imagine you have a Google+ profile and you want to make it easy for anyone coming to get to simply by going to a URL like:

*www.example.com/+

*example.com/+

This pattern will match:

http://example.com/+

http://www.example.com/+

https://www.example.com/+

https://blog.example.com/+

https://www.blog.example.com/+

Etc...

It will not match:

http://www.example.com/blog/+ [extra directory before the +]

http://www.example.com+ [no trailing slash]

因为自己是从mlife.work跳转到blog.myds.cloud，所以就需要在Page Rules选项里面添加一条跳转记录，如下图：

这样子就搞定了。

WordPress安装插件时提示输入FTP账户密码

发表评论

好久没搞Wordpress平台，因为最近Google统计老是提示typecho对移动平台兼容性不好，一时半会也看不到官方有推出新版的状态，干脆就转到Wordpress好了。

之前是DS215j跑Wordpress实在太慢了，现在弄了个黑裙（Intel G4600 CPU + 8G RAM）辅助，不知道性能高哪里去了，现在不是瓶颈了。

第一步装了个最新的5.1.1，结果群晖官方还没出PHP7.3, Orz只能去找最新的4.9.10了，把英文版的改一下配置，更新上中文界面。

define('WPLANG', 'zh_CN');

1	define('WPLANG', 'zh_CN');

刚装完开始弄插件就提示标题这玩意，只能又去找答案了，解决办法如下：

编辑wp-config.php，添加一列这个：

define('FS_METHOD', 'direct');

1	define('FS_METHOD', 'direct');

然后就不会再问账号密码了，当然前提是http账户已经可以读写wp-content目录。

chmod 777 /wordpress/wp-content/plugins/

1	chmod 777 /wordpress/wp-content/plugins/

参考链接：
https://support.cloudways.com/how-to-resolve-wordpress-asking-for-ftp-credentials-error/
https://stackoverflow.com/questions/17922644/wordpress-asking-for-my-ftp-credentials-to-install-plugins

群晖DSM6开启typecho/wordpress的静态链接

2条回复

搞了几天的OMV，还是觉得群晖的DSM省事省心，就挂了个固态硬盘给群晖，机械硬盘都拨给OMV管理电源。

以前都是在Apache下面用.httaccess做静态链接，这次想在上次研究nginx下弄typecho的静态链接基础下搞掂群晖的DSM。

找到了群晖放vhost的配置文件位置，照样画葫芦修改了配置文件。

@DS918:/etc/nginx/app.d/server.webstation-vhost.conf

1	@DS918:/etc/nginx/app.d/server.webstation-vhost.conf

结果重启nginx服务，配置就洗白回到初始状态了。。。被群晖洗干净了。

只能求助谷歌大神了，找了一篇有帮助的文章。
https://stackoverflow.com/questions/36392365/dsm6-configure-nginx-for-wordpress-permalinks-avoid-404

这里简洁说一下步骤：

先打开

@DS918:/etc/nginx/app.d$ cat server.webstation-vhost.conf

1	@DS918:/etc/nginx/app.d$ cat server.webstation-vhost.conf

文件

server {
listen 80;
listen [::]:80;
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name mlife.work;
[...此处省略500字...]
include /usr/local/etc/nginx/conf.d/9857ed05-0298-40de-b36e-2d7530db4731/user.conf*;
}

server {

listen 80;

listen [::]:80;

listen 443 ssl http2;

listen [::]:443 ssl http2;

server_name mlife.work;

[...此处省略500字...]

include /usr/local/etc/nginx/conf.d/9857ed05-0298-40de-b36e-2d7530db4731/user.conf*;

}

然后根据include的文件位置，提示你的vhost自定义配置文件应该放这里，还有命名规范。

include /usr/local/etc/nginx/conf.d/9857ed05-0298-40de-b36e-2d7530db4731/user.conf*;

1	include /usr/local/etc/nginx/conf.d/9857ed05-0298-40de-b36e-2d7530db4731/user.conf*;

切换到以上这个路径/usr/local/etc/nginx/conf.d/9857ed05-0298-40de-b36e-2d7530db4731，用ls命令会看到是空白的，然后根据文件规范命名自己的自定义文件：

注意每个机器的位置会不一样的，根据自己的id查看，这里的[9857ed05-0298-40de-b36e-2d7530db4731]仅供参考

$ sudo vi user.conf.typecho-permalink

1	$ sudo vi user.conf.typecho-permalink

然后在user.conf.typecho-permalink里面填入url rewrite规则，保存退出vi。

location /{
try_files $uri $uri/ /index.php?$args;
}

location /{

try_files $uri $uri/ /index.php?$args;

}

最后一步就是重启nginx加载配置文件

$sudo synoservicecfg --restart nginx

1	$sudo synoservicecfg --restart nginx

然后再打开你的typecho就好啦，静态链接可以正常打开了，你的vhost配置文件也不会被删掉了。

typecho在nginx开启永久链接

发表评论

最近把家里的NAS平台从群晖迁移到了Openmediavault，简称OMV。就是因为群晖管理硬盘实在太傻了，动不动就把硬盘全部叫起来跑步，新NAS机箱是六盘位的，不希望硬盘没事就转啊转，一来费电二来吵闹兼吸尘。

选来选去用上了OMV系统，这个比较合胃口，简单清爽，关键是硬盘管理比较友善而且适合家用，希望24小时待机候命又不希望它没事瞎跑。

刚开始想用docker搞定所有的LNMP，但是试了几个都不太好玩而且docker的mariadb实在太难练上去了，搞了半天干脆用OMV自带的PHP-FPM和NGinx服务器算了，点几下鼠标搞定了。然后把群晖的blog迁移过来，因为换了平台，之前的静态链接.htaccess没法用了，只能又重新琢磨怎么在nginx下面搞掂永久链接，看了很多资料都是很老的了，好不容易找到一篇新点的平台文章借鉴了一下。

链接这里

但是里面内容还是跟自己的实际情况有些出入，根据实际修改了一下，跑了一下没问题了就记录下俩方便自己下一次折腾。
作者的配置文件：

location / {
# one line for typecho staticize and with cgi.fix_pathinfo=0 in php.ini more secure
try_files $uri $uri/ @typecho;
}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
location ~ \.php$ {
#try_files $uri @typecho;
fastcgi_pass 127.0.0.1:9000;
#include from snippets/fastcgi-php.conf:
# regex to split $uri to $fastcgi_script_name and $fastcgi_path
fastcgi_split_path_info ^(.+\.php)(/.+)$;
# Check that the PHP script exists before passing it
try_files $fastcgi_script_name =404;
# Bypass the fact that try_files resets $fastcgi_path_info
# see: http://trac.nginx.org/nginx/ticket/321
set $path_info $fastcgi_path_info;
fastcgi_param PATH_INFO $path_info;
fastcgi_index index.php;
include fastcgi.conf;
}
location @typecho {
fastcgi_pass 127.0.0.1:9000;
fastcgi_param SCRIPT_FILENAME $document_root/index.php;
include fastcgi_params;
}

location / {

# one line for typecho staticize and with cgi.fix_pathinfo=0 in php.ini more secure

try_files $uri $uri/ @typecho;

}

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000

location ~ \.php$ {

#try_files $uri @typecho;

fastcgi_pass 127.0.0.1:9000;

#include from snippets/fastcgi-php.conf:

# regex to split $uri to $fastcgi_script_name and $fastcgi_path

fastcgi_split_path_info ^(.+\.php)(/.+)$;

# Check that the PHP script exists before passing it

try_files $fastcgi_script_name =404;

# Bypass the fact that try_files resets $fastcgi_path_info

# see: http://trac.nginx.org/nginx/ticket/321

set $path_info $fastcgi_path_info;

fastcgi_param PATH_INFO $path_info;

fastcgi_index index.php;

include fastcgi.conf;

}

location @typecho {

fastcgi_pass 127.0.0.1:9000;

fastcgi_param SCRIPT_FILENAME $document_root/index.php;

include fastcgi_params;

}

但是自己用的是FPM的socket，所以要最后修改如下：

server {
listen 81;
listen [::]:81;
listen 444 ssl http2;
listen [::]:444 ssl http2;
ssl_certificate /etc/ssl/certs/openmediavault-42052d8e-d4b9-4fda-985b-12345678901.crt;
ssl_certificate_key /etc/ssl/private/openmediavault-42052d8e-d4b9-4fda-985b-12345678901.key;
set $root_path "/srv/SSD/web";
root $root_path;
index index.html index.php;
set $socket "unix:/var/run/fpm-f1465962-94b9-4530-9a84-12345678901.sock";
location / {
try_files $uri $uri/ @typecho;
}
location ~ \.php$ {
fastcgi_pass $socket;
fastcgi_split_path_info ^(.+\.php)(/.+)$;
try_files $fastcgi_script_name =404;
set $path_info $fastcgi_path_info;
fastcgi_param PATH_INFO $path_info;
fastcgi_index index.php;
include fastcgi.conf;
}
location @typecho {
fastcgi_pass $socket;
fastcgi_param SCRIPT_FILENAME $document_root/index.php;
include fastcgi_params;
}
access_log /var/log/nginx/b5a4341d-4b02-484d-9403-12345678901-access.log;
error_log /var/log/nginx/b5a4341d-4b02-484d-9403-12345678901-error.log;
autoindex on;
large_client_header_buffers 4 8k;
}

server {

listen 81;

listen [::]:81;

listen 444 ssl http2;

listen [::]:444 ssl http2;

ssl_certificate /etc/ssl/certs/openmediavault-42052d8e-d4b9-4fda-985b-12345678901.crt;

ssl_certificate_key /etc/ssl/private/openmediavault-42052d8e-d4b9-4fda-985b-12345678901.key;

set $root_path "/srv/SSD/web";

root $root_path;

index index.html index.php;

set $socket "unix:/var/run/fpm-f1465962-94b9-4530-9a84-12345678901.sock";

location / {

try_files $uri $uri/ @typecho;

}

location ~ \.php$ {

fastcgi_pass $socket;

fastcgi_split_path_info ^(.+\.php)(/.+)$;

try_files $fastcgi_script_name =404;

set $path_info $fastcgi_path_info;

fastcgi_param PATH_INFO $path_info;

fastcgi_index index.php;

include fastcgi.conf;

}

location @typecho {

fastcgi_pass $socket;

fastcgi_param SCRIPT_FILENAME $document_root/index.php;

include fastcgi_params;

}

access_log /var/log/nginx/b5a4341d-4b02-484d-9403-12345678901-access.log;

error_log /var/log/nginx/b5a4341d-4b02-484d-9403-12345678901-error.log;

autoindex on;

large_client_header_buffers 4 8k;

}

Typecho出现500 Database Server Error

发表评论

把typecho从群晖迁移到OMV，运行发现Database Server Error的问题，

上网找了一下其原因是在php 7.0环境下Mysql的链接函数已经被干掉，推荐使用mysqli 或者 Pdo，而Typecho只有Mysql和Pdo两种适配器

所以就是要替换适配器。

在config.inc.php 55行处

$db = new TypechoDb('Mysql', 'typecho');

1	$db = new TypechoDb('Mysql', 'typecho');

改为

$db = new TypechoDb('PdoMysql', 'typecho_');

1	$db = new TypechoDb('PdoMysql', 'typecho_');

引用：
https://assbbs.com/thread-13054.htm

My life's Work

个人在线笔记

分类目录归档：Wordpress&Typecho

Cloudflare 301 域名跳转

WordPress安装插件时提示输入FTP账户密码

群晖DSM6开启typecho/wordpress的静态链接

typecho在nginx开启永久链接

Typecho出现500 Database Server Error