설치 / 업그레 이드 WordPress의 Subversion을 함께 - VPS 성경 # 15

이 방법 안내를 다운로드 및 여러분의 리눅스 커맨드 라인 인터페이스에서 독립 WordPress의 블로그 및 자신의 플러그인을 신속하고 쉽게 설치, 간단한 업데이트 이후에 Subversion을 사용합니다. 또한 세부 정보 WordPress의 MySQL 데이터베이스 설정을 처리합니다.

좋아, 나도 인정하지만, 나는 WordPress의 대한 편견을이야! 그리고이 가이드는 그 빠른 시간에 VPS에서 자신의 WP 블로그를 시작하고 미래를 설계하고자 교정을위한 완벽한 적합이다.

만약 당신이 하나를 다른 플랫폼의 수천의 Subversion을 사용하여 설치할 수있는 사용이 아니라서, 설치 프로세스 disimilar 아니라고 밝혔다. 만약 당신이 코멘트를두고 내가 도와 노력하겠습니다 원하는 플랫폼에 대한 특정 질문이있다. 누가 알겠어, 난 심지어 특정 자습서를 쓸 수있습니다.

WordPressers - 시간의 번들을하기 위해 준비.

필수 WordPress의 웹 서버 준비하기

파트 8 있음 : 빠른 VPS! PHP는 MySQL이 & Xcache, 다른 것들 사이에 최대로 설정, 우리는 Subversion을 설치합니다. 부품 11 년 : NGINX 설치 (Apache 또는 Lighttpd 이상) Nginx 설정 우리는 더 나은. 부품 13 년 : 구성 NGINX 멀티 - 사이트 가상 Nginx 우리는 파일 구조가 향상된 멀티 허용 사이트를 호스팅하는 호스트. 부품 14 년 : NGINX에 설치 WordPress의 (FURLs & 캐시), 우리는 WordPress의 최적화를 제공 Nginx 불통. 만약 당신이 어떤 사람의 캐다 싶었어.

이 튜토리얼의이 끝날 무렵, 우리는 WordPress의 작동이됩니다. 부드러워.

여기에 귀하의 요구 사항 위치 : -

• 데이터베이스를 만들려
• WordPress의 설치
• 원하는 플러그인 추가
• 테마 수입
• 이주의 데이터

만약 당신이 새로운 블로그를 원한다면 그 첫 번째 4 단계로 수행됩니다.

터미널 CLI는 것좀를 엽니다. 만약 로컬 및 Windows를 사용하여 이미 이렇게하지 않았다면 원격 서버에 액세스를 안전하게 만들 해산물 로그온 프로세스를 쉽게합니다. 그 들어, 읽기 파트 3 : 원격 암호화된 연결 및 제 4 부 : 숨기기 데이터 및 간단한 로그인 - SSH를 & PuTTY를 설정합니다.

... 그러나 난 잔소리를 해요, 만약 당신이 이미 당신은 또한 6 부 수행 했어야 : LOCK 리눅스 - SSH를 & iptables 방화벽.

마지막 단 하나 적어 둡니다. throughout this guide. 이 가이드를 통해 내가 예를 들어 내 리눅스 / MySQL의 사용자 이름 guvnr 내 웹사이트 waywiderweb.com. 고객님의 교체 그 가치를

오른쪽. 롤 준비했다.

워드 프레스에 대한 명령줄에서 MySQL 데이터베이스 만들기

로그인과 MySQL을 위해 : -

mysql -u root -p

Add your password, or the password we created when we installed MySQL in Part 8: FASTER VPS! Set Up PHP, MySQL & Xcache .

Now paste this lot, replacing your_wordpress_username , your_wordpress_password and wp_database_name with yours, and leaving the quote marks I've included for the password:-

grant all privileges on *.* to your_wordpress_username@localhost identified by "your_wordpress_password";
create database wp_database_name;
quit

Install WordPress on your Linux VPS Using Subversion

Let's go to the directory in which to install WordPress. I'm installing to my root directory, /home/public_html/waywiderweb.com/public , which I created in Part 13: Configure NGINX Multi-Site Virtual Hosts (the directory structure is explained most comprehensively in the video in Part 13.) If you want your blog to appear in a sub-directory, such as waywiderweb.com/blog, then use /home/public_html/waywiderweb.com/public/blog . Of course, change waywiderweb.com for your domain:-

cd /home/public_html/waywiderweb.com/public

If you created a test index.html file in Part 13: Configure NGINX Multi-Site Virtual Hosts , let's bin it:-

sudo rm index.html

Now we'll use the subversion command to install the latest version of WordPress. Ammend this version with any newer one. Leave the dot at the end, it's not a typo:-

sudo svn co http://svn.automattic.com/wordpress/tags/2.8.4 .

And create the WordPress config file:-

sudo mv wp-config-sample.php wp-config.php

Now let's connect the database. Open the WP config file:-

sudo nano wp-config.php

...and add the details you entered above into your new MySQL database. So, in the wp_config file, swap putyourdbnamehere , usernamehere and yourpasswordhere . Here's the original wp-config, before you change it:-

/** The name of the database for WordPress */
define('DB_NAME', 'putyourdbnamehere');

/** MySQL database username */
define('DB_USER', 'usernamehere');

/** MySQL database password */
define('DB_PASSWORD', 'yourpasswordhere');

While you're in there, for added security, find:-

$table_prefix  = 'wp_';

...and swap wp_ to something unique.

Save and quit (CTRL-X, 'y' to confirm and hit Return.)

Run WordPress Install & Connect the MySQL Database

Open your blog in a browser, so for me, for instance, that's www.waywiderweb.com. Enter a few details, log in and change the password the WP installer gave the newly created Admin user. You should really delete Admin entirely and replace with another user, but that's another story.

Batch-install WordPress Plugins using Subversion

This bit really rocks my roger. If you've got a bunch of blogs with pretty much the same plugins, you may just save a month of Sundays here.

Back at the CLI, goto the plugin directory:-

cd /home/public_html/waywiderweb.com/public/wp-content/plugins

Let's edit our plugin list. Keep that dot:-

sudo svn propedit svn:externals .

OK, so there's only Akismet in there. Let's add some more. Go to the WordPress Subversion plugin repository and take your pick. For each plugin you have 2 download choices:-

• tags - stable releases by version, so choose generally the latest
• trunk - latest version, bleeding edge, occasionally buggy

Personally, I run the trunk versions, for the simple reason that I can install or upgrade all plugins by issuing a simple command, thereafter. If a plugin gives me any gip, I simply delete it and its reference in my svn WP plugins list, else I replace its trunk with a tag. Of course, if you use the tags option, you have to keep editing your plugins file, which largely negates having it in the first place.

So, here's an example externals file that I've thrown together. Note the name of each plugin before the link, 'cos you must have that identifier. If you followed Part 14: Setup WordPress on NGINX (FURLs & Cache), you'll notice I've included the WP Super Cache plugin:-

akismet http://plugins.svn.wordpress.org/akismet/trunk/
wp-phpmyadmin http://svn.wp-plugins.org/wp-phpmyadmin/
wp-super-cache http://svn.wp-plugins.org/wp-super-cache/trunk/

TIDY TIP: If you're happy with trunks, in the WP Sub Vers Repos, look down the list and right mouse click > Copy Link Location , then paste it to a text file, adding the name of the plugin before the link. Do that to as many plugins as you want, then simply paste /trunk at the end of each link. Then paste the lot to your svn plugins file. Much quicker. If you want tagged versions, it's the long way round, 'cos the tags differ. Then again, for some plugins, there is no svn listing at all, so those have to be included the old-fashioned way.

Right, with your plugins file edited, saved and closed, now type:-

sudo svn update

Take tea.

Import Your WordPress Theme

Set Linux Folder Permissions

If you didn't in Part 13: Configure NGINX Multi-Site Virtual Hosts , set your folder permissions, allowing SFTP access, substituting guvnr with your user name:-

sudo chown -R guvnr:webmasters /home/public_html

Add the theme

If you are using a regular theme, add it in the usual WordPress way.

Alternatively, if you want to use a previous, adapted theme:-

Open an SFTP client like FileZilla or WinSCP, browse to your remote themes directory - something like /home/public_html/waywiderweb.com/public/wp-content/themes/ - and upload your bespoke theme.

Either way, you can now enable the theme in the regular way, at http://your_blog.com/wp-admin/themes.php .

Relocate Your Existing WP Blog Data

...If you've got any to relocate! For new blogs, skip this bit.

You can do this by exporting from the old and importing into the new database. In my experience it's far easier to use WP's export/import tools, which also optimises the data.

Surf to your original blog:-

http://www.your_ORIGINAL_blog.com/wp-admin/export.php

...or Dashboard > Tools > Export .

And Download export file .

Now goto your new blog:-

http://www.your_ORIGINAL_blog.com/wp-admin/import.php

...or Dashboard > Tools > Import .

Click the WordPress option, choose the exported file and Upload file and import . Prompted, check the box Download and import file attachments .

If you receive any errors, that's probably a permissions problem. For example, I got this:-

Unable to create directory /home/public_html/waywiderweb.com/public/wp-content/uploads/2009/04. Is its parent directory writable by the server?

...So we'll take ownership of the directory:-

sudo chown -R guvnr:webmasters /home/public_html/waywiderweb.com
sudo chmod -R g+w /home/public_html/waywiderweb.com

And now have another go with Upload file and import , opting for our user imports and checking the box Download and import file attachments .

If you'd prefer to relocate select data, there's always wp-phpmyadmin .

Activating WP Super Cache

Activate in the usual WordPress way, and cash in on the groundwork of Part 13: Configure NGINX Multi-Site Virtual Hosts . Cash in, geddit! Sorry.

Updating WordPress Plugins

While 2.7 brought in some top functionality with the WordPress auto-updating, pretty much negating using Subversion to update the platform or plugins, there will be occasions when it's still faster to upgrade plugins this way.

Particularly this will be the case after a platform upgrade, when plugins race to bring out updates, they can be upgraded together using Subversion:-

sudo svn update

Sending Live a Relocated WordPress Blog

Refer to Part 19: Moving Day! How to Move Your Blog or Site for the best way to do this, with the least downtime or other sticky problems.

Rinse & Repeat

Follow this process for your en 로그인과 MySQL을 위해 : -

mysql -u root -p

Add your password, or the password we created when we installed MySQL in Part 8: FASTER VPS! Set Up PHP, MySQL & Xcache .

Now paste this lot, replacing your_wordpress_username , your_wordpress_password and wp_database_name with yours, and leaving the quote marks I've included for the password:-

grant all privileges on *.* to your_wordpress_username@localhost identified by "your_wordpress_password";
create database wp_database_name;
quit

Install WordPress on your Linux VPS Using Subversion

Let's go to the directory in which to install WordPress. I'm installing to my root directory, /home/public_html/waywiderweb.com/public , which I created in Part 13: Configure NGINX Multi-Site Virtual Hosts (the directory structure is explained most comprehensively in the video in Part 13.) If you want your blog to appear in a sub-directory, such as waywiderweb.com/blog, then use /home/public_html/waywiderweb.com/public/blog . Of course, change waywiderweb.com for your domain:-

cd /home/public_html/waywiderweb.com/public

If you created a test index.html file in Part 13: Configure NGINX Multi-Site Virtual Hosts , let's bin it:-

sudo rm index.html

Now we'll use the subversion command to install the latest version of WordPress. Ammend this version with any newer one. Leave the dot at the end, it's not a typo:-

sudo svn co http://svn.automattic.com/wordpress/tags/2.8.4 .

And create the WordPress config file:-

sudo mv wp-config-sample.php wp-config.php

Now let's connect the database. Open the WP config file:-

sudo nano wp-config.php

...and add the details you entered above into your new MySQL database. So, in the wp_config file, swap putyourdbnamehere , usernamehere and yourpasswordhere . Here's the original wp-config, before you change it:-

/** The name of the database for WordPress */
define('DB_NAME', 'putyourdbnamehere');

/** MySQL database username */
define('DB_USER', 'usernamehere');

/** MySQL database password */
define('DB_PASSWORD', 'yourpasswordhere');

While you're in there, for added security, find:-

$table_prefix  = 'wp_';

...and swap wp_ to something unique.

Save and quit (CTRL-X, 'y' to confirm and hit Return.)

Run WordPress Install & Connect the MySQL Database

Open your blog in a browser, so for me, for instance, that's www.waywiderweb.com. Enter a few details, log in and change the password the WP installer gave the newly created Admin user. You should really delete Admin entirely and replace with another user, but that's another story.

Batch-install WordPress Plugins using Subversion

This bit really rocks my roger. If you've got a bunch of blogs with pretty much the same plugins, you may just save a month of Sundays here.

Back at the CLI, goto the plugin directory:-

cd /home/public_html/waywiderweb.com/public/wp-content/plugins

Let's edit our plugin list. Keep that dot:-

sudo svn propedit svn:externals .

OK, so there's only Akismet in there. Let's add some more. Go to the WordPress Subversion plugin repository and take your pick. For each plugin you have 2 download choices:-

• tags - stable releases by version, so choose generally the latest
• trunk - latest version, bleeding edge, occasionally buggy

Personally, I run the trunk versions, for the simple reason that I can install or upgrade all plugins by issuing a simple command, thereafter. If a plugin gives me any gip, I simply delete it and its reference in my svn WP plugins list, else I replace its trunk with a tag. Of course, if you use the tags option, you have to keep editing your plugins file, which largely negates having it in the first place.

So, here's an example externals file that I've thrown together. Note the name of each plugin before the link, 'cos you must have that identifier. If you followed Part 14: Setup WordPress on NGINX (FURLs & Cache), you'll notice I've included the WP Super Cache plugin:-

akismet http://plugins.svn.wordpress.org/akismet/trunk/
wp-phpmyadmin http://svn.wp-plugins.org/wp-phpmyadmin/
wp-super-cache http://svn.wp-plugins.org/wp-super-cache/trunk/

TIDY TIP: If you're happy with trunks, in the WP Sub Vers Repos, look down the list and right mouse click > Copy Link Location , then paste it to a text file, adding the name of the plugin before the link. Do that to as many plugins as you want, then simply paste /trunk at the end of each link. Then paste the lot to your svn plugins file. Much quicker. If you want tagged versions, it's the long way round, 'cos the tags differ. Then again, for some plugins, there is no svn listing at all, so those have to be included the old-fashioned way.

Right, with your plugins file edited, saved and closed, now type:-

sudo svn update

Take tea.

Import Your WordPress Theme

Set Linux Folder Permissions

If you didn't in Part 13: Configure NGINX Multi-Site Virtual Hosts , set your folder permissions, allowing SFTP access, substituting guvnr with your user name:-

sudo chown -R guvnr:webmasters /home/public_html

Add the theme

If you are using a regular theme, add it in the usual WordPress way.

Alternatively, if you want to use a previous, adapted theme:-

Open an SFTP client like FileZilla or WinSCP, browse to your remote themes directory - something like /home/public_html/waywiderweb.com/public/wp-content/themes/ - and upload your bespoke theme.

Either way, you can now enable the theme in the regular way, at http://your_blog.com/wp-admin/themes.php .

Relocate Your Existing WP Blog Data

...If you've got any to relocate! For new blogs, skip this bit.

You can do this by exporting from the old and importing into the new database. In my experience it's far easier to use WP's export/import tools, which also optimises the data.

Surf to your original blog:-

http://www.your_ORIGINAL_blog.com/wp-admin/export.php

...or Dashboard > Tools > Export .

And Download export file .

Now goto your new blog:-

http://www.your_ORIGINAL_blog.com/wp-admin/import.php

...or Dashboard > Tools > Import .

Click the WordPress option, choose the exported file and Upload file and import . Prompted, check the box Download and import file attachments .

If you receive any errors, that's probably a permissions problem. For example, I got this:-

Unable to create directory /home/public_html/waywiderweb.com/public/wp-content/uploads/2009/04. Is its parent directory writable by the server?

...So we'll take ownership of the directory:-

sudo chown -R guvnr:webmasters /home/public_html/waywiderweb.com
sudo chmod -R g+w /home/public_html/waywiderweb.com

And now have another go with Upload file and import , opting for our user imports and checking the box Download and import file attachments .

If you'd prefer to relocate select data, there's always wp-phpmyadmin .

Activating WP Super Cache

Activate in the usual WordPress way, and cash in on the groundwork of Part 13: Configure NGINX Multi-Site Virtual Hosts . Cash in, geddit! Sorry.

Updating WordPress Plugins

While 2.7 brought in some top functionality with the WordPress auto-updating, pretty much negating using Subversion to update the platform or plugins, there will be occasions when it's still faster to upgrade plugins this way.

Particularly this will be the case after a platform upgrade, when plugins race to bring out updates, they can be upgraded together using Subversion:-

sudo svn update

Sending Live a Relocated WordPress Blog

Refer to Part 19: Moving Day! How to Move Your Blog or Site for the best way to do this, with the least downtime or other sticky problems.

Rinse & Repeat

Follow this process for your entire blog farm.

Just Round the Corner

For WordPress, that's all the specifics taken care of, I think. You tell me, what have I forgotten? Lemme know and I'll write it up.

More generally, I'll wrap up the series - Set Up Unmanaged VPS (4 Newbies) .. The VPS Bible - by showing how and why to setup Google Apps in Part 17: Google Apps for Domain-Specific Email , which keeps our VPS server resources jealously focussed on our sites and blogs, before running down the all-important moving day checklist mentioned above. Then there'll be a handy backup guide before linking a heap of top resources for Linux newbies in Part 20: Blogroll, Links, Credits, Resources .

Guess what...