wordpress部署解决方案，想法？ [英] wordpress deploying solution, ideas?

问题描述

我在本地机器上开发一个Wordpress网站，现在我正在寻找一种轻松快捷地部署它的机制。我正在考虑一个DEV环境（位于我的本地机器上），一个STAGING环境（客户端页面上的一个子域，也许是staging.example.com），当然还有一个LIVE环境（example.com）！

我目前的解决方法：
当我与Aptana合作时，我可以将更改的文件与IDE提供的部署机制同步。导出我的本地数据库，查找/替换固定链接并导入整个事物 - 完成！要实时部署，我必须用实时文件替换所有的分段文件。

这应该更容易！有没有人在那里，有更好的工作流程？
我开放，对你的想法感到非常兴奋！

非常感谢
greetings

解决方案

是的，这是令人沮丧和完全疯狂的Wordpress需要这个过程，因为他们把绝对urls在数据库。我以类似的方式开发使用多个分期站点进行qa和客户端审查。在我第一次部署WordPress之后，我几乎完全放弃了平台。核心开发人员和其他人推荐的所有解决方案根本没有起作用。

所以我写了一个插件： http://wordpress.org/extend/plugins/root-relative-urls/
修复了问题。使用这个插件，你不需要做一个搜索&替换您的内容。没有主机文件黑客或dns技巧。使用我的插件，您可以通过IP地址或Computername或任何类型的转发主机访问该站点。而且由于它在输入数据库之前将url转换为root相对，所以您不用担心它们在不同的域格式之间工作。而且，由于他们并没有对url中的方案（http / s）进行硬编码，所以您不用担心在使用SSL的情况下，在wordpress trac数据库中报告的520个错误。

这是我在这几天工作的任何wordpress项目的主要内容。而且我已经写了几个其他插件来处理你可以在这里查看的平台中存在的特性： http://wordpress.org/extend/plugins/profile/marcuspope

希望能够解决您的问题。

I develop on a local machine a Wordpress site and I'm now looking for a mechanism to deploy it easy and fast. I'm thinking about a DEV environment (located on my local machine), a STAGING environment (a subdomain on the client page, maybe staging.example.com) and of course a LIVE environment (example.com)!

My current workaround: As I work with Aptana I'm able to sync my changed files with the deploy mechanism the IDE provides. Exporting my local database, finding/replacing the permalinks and importing the whole thing - finish! To deploy live, I have to replace all staging files with the live files.

This should be easier! Is there anyone out there, having a better workflow? I'm open and really excited about your ideas!

Thanks a lot greetings

解决方案

Yep, it's frustrating and completely insane that Wordpress requires this process because they put absolute urls in the database. I develop in a similar fashion using multiple staging sites for qa and client review. After my first deployment with Wordpress I almost gave up on the platform entirely. All of the solutions recommended by core developers and others simply didn't work.

So I wrote a plugin: http://wordpress.org/extend/plugins/root-relative-urls/ that fixes the problem. With this plugin you don't need to do a search & replace on your content. No hosts file hacks, or dns tricks. With my plugin you can access the site via IP address or Computername or any type of forwarded host. And since it converts urls to root relative before they enter the database, you won't have to worry about them working between the different domain formats. And since they don't hard-code the scheme (http/s) in the url you won't have to worry about the 520 or so bugs that were reported in the wordpress trac database if you use SSL.

It's a staple for any wordpress project I work on these days. And I have written a couple other plugins to deal with idiosyncrasies that exist in the platform that you can check out here: http://wordpress.org/extend/plugins/profile/marcuspope

Hope that answers your problem.

这篇关于wordpress部署解决方案，想法？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！