diff --git a/sources/tech/20180823 How to publish a WordPress blog to a static GitLab Pages site.md b/sources/tech/20180823 How to publish a WordPress blog to a static GitLab Pages site.md deleted file mode 100644 index fd52def010..0000000000 --- a/sources/tech/20180823 How to publish a WordPress blog to a static GitLab Pages site.md +++ /dev/null @@ -1,92 +0,0 @@ -translating---geekpi - -How to publish a WordPress blog to a static GitLab Pages site -====== - -![](https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/web-design-monitor-website.png?itok=yUK7_qR0) - -A long time ago, I set up a WordPress blog for a family member. There are lots of options these days, but back then there were few decent choices if you needed a web-based CMS with a WYSIWYG editor. An unfortunate side effect of things working well is that the blog has generated a lot of content over time. That means I was also regularly updating WordPress to protect against the exploits that are constantly popping up. - -So I decided to convince the family member that switching to [Hugo][1] would be relatively easy, and the blog could then be hosted on [GitLab][2]. But trying to extract all that content and convert it to [Markdown][3] turned into a huge hassle. There were automated scripts that got me 95% there, but nothing worked perfectly. Manually updating all the posts was not something I wanted to do, so eventually, I gave up trying to move the blog. - -Recently, I started thinking about this again and realized there was a solution I hadn't considered: I could continue maintaining the WordPress server but set it up to publish a static mirror and serve that with [GitLab Pages][4] (or [GitHub Pages][5] if you like). This would allow me to automate [Let's Encrypt][6] certificate renewals as well as eliminate the security concerns associated with hosting a WordPress site. This would, however, mean comments would stop working, but that feels like a minor loss in this case because the blog did not garner many comments. - -Here's the solution I came up with, which so far seems to be working well: - - * Host WordPress site at URL that is not linked to or from anywhere else to reduce the odds of it being exploited. In this example, we'll use (even though this site is actually built with Pelican). - * [Set up hosting on GitLab Pages][7] for the public URL . - * Add a [cron job][8] that determines when the last-built date differs between the two URLs; if the build dates differ, mirror the WordPress version. - * After mirroring with `wget`, update all links from "private" version to "public" version. - * Do a `git push` to publish the new content. - - - -These are the two scripts I use: - -`check-diff.sh` (called by cron every 15 minutes) -``` -#!/bin/bash - -ORIGINDATE="$(curl -v --silent http://private.localconspiracy.com/feed/ 2>&1|grep lastBuildDate)" -PUBDATE="$(curl -v --silent https://www.localconspiracy.com/feed/ 2>&1|grep lastBuildDate)" - -if [ "$ORIGINDATE" !=  "$PUBDATE" ] -then -  /home/doc/repos/localconspiracy/mirror.sh -fi -``` - -`mirror.sh:` -``` -#!/bin/sh - -cd /home/doc/repos/localconspiracy - -wget \ ---mirror \ ---convert-links  \ ---adjust-extension \ ---page-requisites  \ ---retry-connrefused  \ ---exclude-directories=comments \ ---execute robots=off \ -http://private.localconspiracy.com - -git rm -rf public/* -mv private.localconspiracy.com/* public/. -rmdir private.localconspiracy.com -find ./public/ -type f -exec sed -i -e 's|http://private.localconspiracy|https://www.localconspiracy|g' {} \; -find ./public/ -type f -exec sed -i -e 's|http://www.localconspiracy|https://www.localconspiracy|g' {} \; -git add public/* -git commit -m "new snapshot" -git push origin master -``` - -That's it! Now, when the blog is changed, within 15 minutes the site is mirrored to a static version and pushed up to the repo where it will be reflected in GitLab pages. - -This concept could be extended a little further if you wanted to [run WordPress locally][9]. In that case, you would not need a server to host your WordPress blog; you could just run it on your local machine. In that scenario, there's no chance of your blog getting exploited. As long as you can run `wget` against it locally, you could use the approach outlined above to have a WordPress site hosted on GitLab Pages. - -_This article was originally posted at[Local Conspiracy][10]. Reposted with permission._ - --------------------------------------------------------------------------------- - -via: https://opensource.com/article/18/8/publish-wordpress-static-gitlab-pages-site - -作者：[Christopher Aedo][a] -选题：[lujun9972](https://github.com/lujun9972) -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]:https://opensource.com/users/docaedo -[1]:https://gohugo.io/ -[2]:https://gitlab.com/ -[3]:https://en.wikipedia.org/wiki/Markdown -[4]:https://docs.gitlab.com/ee/user/project/pages/ -[5]:https://pages.github.com/ -[6]:https://letsencrypt.org/ -[7]:https://about.gitlab.com/2016/04/07/gitlab-pages-setup/ -[8]:https://en.wikipedia.org/wiki/Cron -[9]:https://codex.wordpress.org/Installing_WordPress_Locally_on_Your_Mac_With_MAMP -[10]:https://localconspiracy.com/2018/08/wp-on-gitlab.html diff --git a/translated/tech/20180823 How to publish a WordPress blog to a static GitLab Pages site.md b/translated/tech/20180823 How to publish a WordPress blog to a static GitLab Pages site.md new file mode 100644 index 0000000000..dc10d754d0 --- /dev/null +++ b/translated/tech/20180823 How to publish a WordPress blog to a static GitLab Pages site.md @@ -0,0 +1,90 @@ +如何将 WordPress 博客发布到静态 GitLab Pages 上 +====== + +![](https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/web-design-monitor-website.png?itok=yUK7_qR0) + +很久以前，我为一个家庭成员建立了一个 WordPress 博客。现在有很多选择，但是当时如果你需要一个带有 WYSIWYG 编辑器的基于网络的 CMS，那么当时很少有不错的选择。运行良好的一个不幸的副作用是博客随着时间的推移产生了很多内容。这意味着我要经常更新 WordPress 以防止不断出现的漏洞。 + +因此，我决定劝说家人切换到 [Hugo][1] 会相对容易，然后可以在 [GitLab][2] 上托管博客。但是尝试提取所有内容并将其转换为 [Markdown][3] 变成了一个巨大的麻烦。有自动脚本完成了 95% 的工作，但并不完美。手动更新所有帖子不是我想做的事情，所以最终，我放弃了试图移动博客。 + +最近，我又开始考虑这个问题，并意识到有一个我没有考虑过的解决方案：我可以继续维护 WordPress 服务器，但将其设置为发布静态镜像，并使用 [GitLab Pages][4]（或 [ GitHub Pages][5] ，如果你喜欢的话）服务。这能让我自动化 [Let's Encrypt][6] 证书续订并消除与托管 WordPress 站点相关的安全问题。然而，这意味着评论将无法使用，但在这种情况下感觉就像是一个小损失，因为博客没有收到很多评论。 + +这是我提出的解决方案，到目前为止似乎运作良好： + + * WordPress 站点中的 URL 没有链接到或来自其他任何地方，以减少它被利用的几率。在此例中，我们将使用 （即使此站点实际上是使用 Pelican 构建的）。 + * 为公共 URL [在 GitLab Pages 上设置托管][7]。 + * 添加 [cron job][8]，确定两个 URL 之间的最后构建日期何时不同。如果构建日期不同，则镜像 WordPress 版本。 + * 使用 `wget` 镜像后，将所有链接从“私有”更新成“公共”。 + * 运行 `git push` 来发布新内容。 + + + +这是我使用的两个脚本： + +`check-diff.sh` (cron 每 15 分钟调用一次) +``` +#!/bin/bash + +ORIGINDATE="$(curl -v --silent http://private.localconspiracy.com/feed/ 2>&1|grep lastBuildDate)" +PUBDATE="$(curl -v --silent https://www.localconspiracy.com/feed/ 2>&1|grep lastBuildDate)" + +if [ "$ORIGINDATE" !=  "$PUBDATE" ] +then +  /home/doc/repos/localconspiracy/mirror.sh +fi +``` + +`mirror.sh:` +``` +#!/bin/sh + +cd /home/doc/repos/localconspiracy + +wget \ +--mirror \ +--convert-links  \ +--adjust-extension \ +--page-requisites  \ +--retry-connrefused  \ +--exclude-directories=comments \ +--execute robots=off \ +http://private.localconspiracy.com + +git rm -rf public/* +mv private.localconspiracy.com/* public/. +rmdir private.localconspiracy.com +find ./public/ -type f -exec sed -i -e 's|http://private.localconspiracy|https://www.localconspiracy|g' {} \; +find ./public/ -type f -exec sed -i -e 's|http://www.localconspiracy|https://www.localconspiracy|g' {} \; +git add public/* +git commit -m "new snapshot" +git push origin master +``` + +就是这些了！现在，当博客发生变化时，在 15 分钟内将网站镜像到静态版本并推送到仓库，这将在 GitLab Pages 中反映出来。 + +如果你想[在本地运行 WordPress][9]，这个概念可以进一步扩展。在这种情况下，你不需要服务器来托管你的 WordPress 博客。你可以在本机运行它。在这种情况下，你的博客不可能被利用。只要你可以在本地运行 `wget`，就可以使用上面的方法在 GitLab Pages 上托管 WordPress 站点。 + +_这篇文章最初发表于 [Local Conspiracy] [10]。允许转载。_ + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/18/8/publish-wordpress-static-gitlab-pages-site + +作者：[Christopher Aedo][a] +选题：[lujun9972](https://github.com/lujun9972) +译者：[译者ID](https://github.com/译者ID) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]:https://opensource.com/users/docaedo +[1]:https://gohugo.io/ +[2]:https://gitlab.com/ +[3]:https://en.wikipedia.org/wiki/Markdown +[4]:https://docs.gitlab.com/ee/user/project/pages/ +[5]:https://pages.github.com/ +[6]:https://letsencrypt.org/ +[7]:https://about.gitlab.com/2016/04/07/gitlab-pages-setup/ +[8]:https://en.wikipedia.org/wiki/Cron +[9]:https://codex.wordpress.org/Installing_WordPress_Locally_on_Your_Mac_With_MAMP +[10]:https://localconspiracy.com/2018/08/wp-on-gitlab.html