PageRenderTime 63ms CodeModel.GetById 22ms RepoModel.GetById 0ms app.codeStats 0ms

/content/98bdbbc023d58582046a04e417e88139

https://github.com/tzmartin/gitmarks_tzm
#! | 1838 lines | 1446 code | 392 blank | 0 comment | 0 complexity | 5267c972ceca14f5105e2c74f91e113b MD5 | raw file

Large files files are truncated, but you can click here to view the full file

    

  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

    2. 

  2. <html xmlns="http://www.w3.org/1999/xhtml">

    3. 

  3. <head profile="http://gmpg.org/xfn/11">

    4. 

  4. <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

    5. 

  5. <meta name="distribution" content="global" />

    6. 

  6. <meta name="robots" content="follow, all" />

    7. 

  7. <meta name="language" content="en, sv" />

    8. 

  8. 

    9. 

  9. <title>  Perfect Setup: Ubuntu Hardy+Nginx+MySQL5+PHP5+Wordress : MENSK Technologies Corporation</title>

    10. 

  10. <meta name="generator" content="WordPress 3.0.1" />

    11. 

  11. <!-- leave this for stats please -->

    12. 

  12. 

    13. 

  13. <link rel="Shortcut Icon" href="http://www.mensk.com/wp-content/themes/revolution_tech-30/images/favicon.ico" type="image/x-icon" />

    14. 

  14. <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://www.mensk.com/feed/" />

    15. 

  15. <link rel="alternate" type="text/xml" title="RSS .92" href="http://www.mensk.com/feed/rss/" />

    16. 

  16. <link rel="alternate" type="application/atom+xml" title="Atom 0.3" href="http://www.mensk.com/feed/atom/" />

    17. 

  17. <link rel="pingback" href="http://www.mensk.com/xmlrpc.php" />

    18. 

  18. 	<link rel='archives' title='August 2010' href='http://www.mensk.com/2010/08/' />
    19. 

  19. 	<link rel='archives' title='January 2009' href='http://www.mensk.com/2009/01/' />
    20. 

  20. 	<link rel='archives' title='December 2008' href='http://www.mensk.com/2008/12/' />
    21. 

  21. 	<link rel='archives' title='November 2008' href='http://www.mensk.com/2008/11/' />
    22. 

  22. 	<link rel='archives' title='October 2008' href='http://www.mensk.com/2008/10/' />
    23. 

  23. 	<link rel='archives' title='September 2008' href='http://www.mensk.com/2008/09/' />
    24. 

  24. 	<link rel='archives' title='August 2008' href='http://www.mensk.com/2008/08/' />
    25. 

  25. 	<link rel='archives' title='July 2008' href='http://www.mensk.com/2008/07/' />
    26. 

  26. <link rel="alternate" type="application/rss+xml" title="MENSK Technologies Corporation &raquo; Perfect Setup: Ubuntu Hardy+Nginx+MySQL5+PHP5+Wordress Comments Feed" href="http://www.mensk.com/webmaster-toolbox/perfect-ubuntu-hardy-nginx-mysql5-php5-wordpress/feed/" />
    27. 

  27. <link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://www.mensk.com/xmlrpc.php?rsd" />
    28. 

  28. <link rel="wlwmanifest" type="application/wlwmanifest+xml" href="http://www.mensk.com/wp-includes/wlwmanifest.xml" /> 
    29. 

  29. <link rel='index' title='MENSK Technologies Corporation' href='http://www.mensk.com/' />
    30. 

  30. <link rel='start' title='Use ranking accelerator keywords to boost your organic ranking' href='http://www.mensk.com/seo-sem/use-ranking-accelerator-keywords-to-boost-your-organic-ranking/' />
    31. 

  31. <link rel='prev' title='Ottawa Sales Leadership Initiative &#8211; the missing link?' href='http://www.mensk.com/happenings/ottawa-sales-leadership-initiative-the-missing-link/' />
    32. 

  32. <link rel='next' title='How to prevent wordpress from messing up with your rich editing tags' href='http://www.mensk.com/webmaster-toolbox/wordpress/how-to-prevent-wordpress-from-changing-tags-and-text-formatting-rich-text-editor/' />
    33. 

  33. <meta name="generator" content="WordPress 3.0.1" />
    34. 

  34. <link rel='canonical' href='http://www.mensk.com/webmaster-toolbox/perfect-ubuntu-hardy-nginx-mysql5-php5-wordpress/' />
    35. 

  35. <link rel='shortlink' href='http://www.mensk.com/?p=89' />
    36. 

  36. 

  37. <!-- All in One SEO Pack 1.6.12.1 by Michael Torbert of Semper Fi Web Design[-1,-1] -->
    38. 

  38. <!-- /all in one seo pack -->
    39. 

  39. <script charset="utf-8" type="text/javascript" src="http://w.sharethis.com/widget/?tabs=web%2Cpost%2Cemail&amp;charset=utf-8&amp;style=rotate&amp;publisher=647813e3-68f4-4195-82a1-47462b8fe7b1&amp;wp=3.0.1"></script><!--[if IE]><script src="http://www.mensk.com/wp-content/plugins/wp-gbcf/wp-gbcf_focus.js" type="text/javascript"></script><![endif]-->
    40. 

  40. <!-- GBCF -->
    41. 

  41. 

  42. 

    43. 

  43. <style type="text/css" media="screen"><!-- @import url( http://www.mensk.com/wp-content/themes/revolution_tech-30/style.css ); --></style>

    44. 

  44. 

    45. 

  45. <script type="text/javascript"><!--//--><![CDATA[//><!--

    46. 

  46. sfHover = function() {

    47. 

  47. 	if (!document.getElementsByTagName) return false;

    48. 

  48. 	var sfEls = document.getElementById("nav").getElementsByTagName("li");

    49. 

  49. 

    50. 

  50. 	// if you only have one main menu - delete the line below //

    51. 

  51. 	var sfEls1 = document.getElementById("subnav").getElementsByTagName("li");

    52. 

  52. 	//

    53. 

  53. 

    54. 

  54. 	for (var i=0; i<sfEls.length; i++) {

    55. 

  55. 		sfEls[i].onmouseover=function() {

    56. 

  56. 			this.className+=" sfhover";

    57. 

  57. 		}

    58. 

  58. 		sfEls[i].onmouseout=function() {

    59. 

  59. 			this.className=this.className.replace(new RegExp(" sfhover\\b"), "");

    60. 

  60. 		}

    61. 

  61. 	}

    62. 

  62. 

    63. 

  63. 	// if you only have one main menu - delete the "for" loop below //

    64. 

  64. 	for (var i=0; i<sfEls1.length; i++) {

    65. 

  65. 		sfEls1[i].onmouseover=function() {

    66. 

  66. 			this.className+=" sfhover1";

    67. 

  67. 		}

    68. 

  68. 		sfEls1[i].onmouseout=function() {

    69. 

  69. 			this.className=this.className.replace(new RegExp(" sfhover1\\b"), "");

    70. 

  70. 		}

    71. 

  71. 	}

    72. 

  72. 	//

    73. 

  73. 

    74. 

  74. }

    75. 

  75. if (window.attachEvent) window.attachEvent("onload", sfHover);

    76. 

  76. //--><!]]></script>

    77. 

  77. 

    78. 

  78. </head>

    79. 

  79. 

    80. 

  80. <body>

    81. 

  81. 

    82. 

  82. <div id="wrap">

    83. 

  83. 

    84. 

  84. <div id="top">

    85. 

  85. 	<img src="http://www.mensk.com/wp-content/themes/revolution_tech-30/images/top.gif" alt="Top" />

    86. 

  86. </div>

    87. 

  87. 

    88. 

  88. <div id="header">

    89. 

  89. 

    90. 

  90. 	<div class="headerleft">

    91. 

  91. 		<a href="http://www.mensk.com/"><img src="http://www.mensk.com/wp-content/themes/revolution_tech-30/images/main_logo.jpg" alt="Life and Business &#8211; on Internet and Beyond" /></a>

    92. 

  92. 	</div>

    93. 

  93. 	

    94. 

  94. 	<!--To define the 468x60 ad, go to your WP dashboard and go to Presentation -> Revolution Tech Options and enter the ad code.-->

    95. 

  95. 	

    96. 

  96. 	<div class="headerright">

    97. 

  97. 		<p><a href="http://www.mensk.com/feed/rss/"><img style="vertical-align:middle" src="http://www.mensk.com/wp-content/themes/revolution_tech-30/images/rss.gif" alt="Subscribe to MENSK Technologies Corporation" /></a><a href="http://www.mensk.com/feed/rss/">News Feed</a><a href="http://www.mensk.com/comments/feed/"><img style="vertical-align:middle;margin-left:10px;" src="http://www.mensk.com/wp-content/themes/revolution_tech-30/images/rss.gif" alt="Subscribe to MENSK Technologies Corporation" /></a><a href="http://www.mensk.com/comments/feed/">Comments</a></p>

    98. 

  98. 			</div>

    99. 

  99. 

    100. 

  100. 

    101. 

  101. </div>

    102. 

  102. 

    103. 

  103. <div id="navbar">

    104. 

  104. 

    105. 

  105. 	<div id="navbarleft">

    106. 

  106. 		<ul id="nav">

    107. 

  107. 			<li><a href="http://www.mensk.com">Home</a></li>

    108. 

  108. 			<li class="page_item page-item-2"><a href="http://www.mensk.com/about/" title="About">About</a></li>
    109. 

  109. <li class="page_item page-item-17"><a href="http://www.mensk.com/ask-me/" title="Ask me!">Ask me!</a></li>
    110. 

  110. <li class="page_item page-item-13"><a href="http://www.mensk.com/contact/" title="Contact Us">Contact Us</a></li>
    111. 

  111. 		</ul>

    112. 

  112. 	</div>

    113. 

  113. 	

    114. 

  114. 	<div id="navbarright">

    115. 

  115. 		<form id="searchform" method="get" action="/index.php">

    116. 

  116. 		<input type="text" value="Search this website..." name="s" id="s" onfocus="if (this.value == 'Search this website...') {this.value = '';}" onblur="if (this.value == '') {this.value = 'Search this website...';}" />

    117. 

  117. 		<input type="submit" id="sbutt" value="GO" /></form>

    118. 

  118. 	</div>

    119. 

  119. 	

    120. 

  120. </div>

    121. 

  121. 

    122. 

  122. <div id="subnavbar">

    123. 

  123. 

    124. 

  124. 	<ul id="subnav">

    125. 

  125. 			<li class="cat-item cat-item-9"><a href="http://www.mensk.com/category/seo-sem/" title="View all posts filed under Dancing with Search Engines">Dancing with Search Engines</a>
    126. 

  126. </li>
    127. 

  127. 	<li class="cat-item cat-item-57"><a href="http://www.mensk.com/category/happenings/" title="View all posts filed under Happenings">Happenings</a>
    128. 

  128. </li>
    129. 

  129. 	<li class="cat-item cat-item-13"><a href="http://www.mensk.com/category/internet-marketing/" title="View all posts filed under Marketing on Internet and Beyond">Marketing on Internet and Beyond</a>
    130. 

  130. </li>
    131. 

  131. 	<li class="cat-item cat-item-6"><a href="http://www.mensk.com/category/services/" title="View all posts filed under Services">Services</a>
    132. 

  132. </li>
    133. 

  133. 	<li class="cat-item cat-item-25"><a href="http://www.mensk.com/category/webmaster-toolbox/" title="View all posts filed under Webmaster Toolbox">Webmaster Toolbox</a>
    134. 

  134. <ul class='children'>
    135. 

  135. 	<li class="cat-item cat-item-59"><a href="http://www.mensk.com/category/webmaster-toolbox/wordpress/" title="View all posts filed under Wordpress">Wordpress</a>
    136. 

  136. </li>
    137. 

  137. </ul>
    138. 

  138. </li>
    139. 

  139. 	</ul>

    140. 

  140. 	

    141. 

  141. </div>

    142. 

  142. <div id="content">

    143. 

  143. 

    144. 

  144. 	<div id="contentleft">

    145. 

  145. 	

    146. 

  146. 		<div class="postarea">

    147. 

  147. 		

    148. 

  148. 		<div class="breadcrumb">

    149. 

  149. 		

    150. 

  150. </div>			

    151. 

  151. 						<h1>Perfect Setup: Ubuntu Hardy+Nginx+MySQL5+PHP5+Wordress</h1>

    152. 

  152. 			

    153. 

  153. 			<div class="date">

    154. 

  154. 				<p>August 16, 2008 by <a href="http://www.mensk.com/author/admin/" title="Posts by admin">admin</a>&nbsp;</p>

    155. 

  155. 			</div>

    156. 

  156. 		

    157. 

  157. 			<style type="text/css">

    158. 

  158. <!--

    159. 

  159. pre {

    160. 

  160. 	font-family: "Courier New", Courier, monospace;

    161. 

  161. 	font-size: small;

    162. 

  162. 	background-color: #E6E6E6;

    163. 

  163. 	padding: 6px;

    164. 

  164. 	/* height: 250px; */

    165. 

  165. 	width: 600px;

    166. 

  166. 	border-top-width: 1px;

    167. 

  167. 	border-right-width: 1px;

    168. 

  168. 	border-bottom-width: 1px;

    169. 

  169. 	border-left-width: 1px;

    170. 

  170. 	border-top-style: inset;

    171. 

  171. 	border-right-style: inset;

    172. 

  172. 	border-bottom-style: inset;

    173. 

  173. 	border-left-style: inset;

    174. 

  174. 	overflow:auto

    175. 

  175. 	

    176. 

  176. }

    177. 

  177. .code_tag {

    178. 

  178. 	font-family: "Courier New", Courier, monospace;

    179. 

  179. 	font-size: small;

    180. 

  180. 	font-style: normal;

    181. 

  181. 	font-weight: bold;

    182. 

  182. 	background-color: #333333;

    183. 

  183. 	display: block;

    184. 

  184. 	width: 600px;

    185. 

  185. 	color: #00FF00;

    186. 

  186. 	padding-top: 2px;

    187. 

  187. 	padding-right: 2px;

    188. 

  188. 	padding-bottom: 2px;

    189. 

  189. 	padding-left: 5px;

    190. 

  190. 	margin-bottom: 12px;

    191. 

  191. 	margin-top: 2px;

    192. 

  192. }

    193. 

  193. .in_editor_tag, .in_editor_normal

    194. 

  194. {

    195. 

  195. 	font-family: "Courier New", Courier, monospace;

    196. 

  196. 	font-size: small;

    197. 

  197. 	font-style: normal;

    198. 

  198. 	font-weight: bold;

    199. 

  199. 	background-color: #CCC;

    200. 

  200. 	display: inline;

    201. 

  201. 	/* width: 600px; */

    202. 

  202. 	color: #000;

    203. 

  203. 	padding-top: 1px;

    204. 

  204. 	padding-right: 5px;

    205. 

  205. 	padding-bottom: 1px;

    206. 

  206. 	padding-left: 5px;

    207. 

  207. }

    208. 

  208. .in_editor_normal

    209. 

  209. {

    210. 

  210. 	font-weight: normal;

    211. 

  211. }

    212. 

  212. .main_text {

    213. 

  213. 	font-family: Verdana, Arial, Helvetica, sans-serif;

    214. 

  214. 	font-size: small;

    215. 

  215. }

    216. 

  216. .main_text ul li{

    217. 

  217. margin-left:5px;

    218. 

  218. }

    219. 

  219. 

    220. 

  220. .sub_heading {

    221. 

  221. 	font-size: x-large;

    222. 

  222. 	font-family: Georgia, "Times New Roman", Times, serif;

    223. 

  223. 	margin-top: 55px;

    224. 

  224. 	margin-right: 50px;

    225. 

  225. 	margin-bottom: 10px;

    226. 

  226. 	margin-left: 20px;

    227. 

  227. 	border: 1px solid #666666;

    228. 

  228. 	padding-top: 5px;

    229. 

  229. 	padding-right: 10px;

    230. 

  230. 	padding-bottom: 5px;

    231. 

  231. 	padding-left: 10px;

    232. 

  232. 	background-color: #FFFFCC;

    233. 

  233. 	display: block;

    234. 

  234. }

    235. 

  235. 

    236. 

  236. -->

    237. 

  237. </style>

    238. 

  238. <div class="main_text">

    239. 

  239.  <p>The Perfect Setup:</p>

    240. 

  240.  <p> <strong><a href="http://www.ubuntu.com/getubuntu/download">Ubuntu Server 8.04.1 LTS Hardy</a> (supported to 2013) + EngineX (NGINX) Web Server built from sources + MySQL 5 + PHP 5.</strong> <br />

    241. 

  241.  (Or <strong><em>LEMP</em></strong> )</p>

    242. 

  242.  <p>Tested on <a href="http://www.slicehost.com/">256MB VPS slice at SliceHost</a>. Should work for other hardware.</p>

    243. 

  243.  <p>From baremetal/barebone/empty fresh install of Ubuntu Server to shiny, fast and SEO-friendly WordPress Portal propelled by <a href="http://wordpress.org/extend/plugins/wp-super-cache/">WP Super Cache plugin</a>. <br />

    244. 

  244.    All configured and powered by <a href="http://nginx.net/">NGinx WEB Server</a>.<br />

    245. 

  245.  Step by step copy/paste instructions - from &quot;zero to hero&quot; with everything on a single page (albeit long one) and in the right order. Just what your granma was asking for! </p>

    246. 

  246.  <p>Every time I need to quickly utilize new product or technology it always made me wonder &quot;why don't someone came up with a simple step by step instructions on <strong>which buttons to press</strong> to make this thing work?&quot;. So instead of waiting for someone to do it this time I decided to make one myself.</p>

    247. 

  247. <p>After spending countless hours and days hunting for scripts, searching for clues, scrolling through misleading posts, extracting bits from articles, eliminating blubber and fluff, bugging busy geeky people for hints and getting all necessary pieces together in the right order I finally came up with this instructional post. It all boils down to step-by-step copy/paste instructions that should take you less than 1 hour to get from freshly installed Ubunty server to fully functioning, search engine optimized business-ready WordPress-powered website.</p>

    248. 

  248.  <p>I tested it all on 256MB VPS image offered by <a href="http://www.slicehost.com/">SliceHost</a> but the same instructions should work just just fine on any real hardware as well. <br />

    249. 

  249.  Most credits goes to <a href="http://articles.slicehost.com/ubuntu-hardy">excellent set of articles by PickedOnion at SliceHost</a> plus to some more sources, acknowledged within this post.</p>

    250. 

  250.  <p>This article assumes your username is 'jsmith' and your domain is 'mydomain.com'.</p>

    251. 

  251. <p>Now it's time to get our hands dirty!</p>

    252. 

  252. <span class="sub_heading">Secure and tidy-up your fresh Ubuntu Server installation</span>  

    253. 

  253. <ul>

    254. 

  254. 	<li>Login as root.</li>

    255. 

  255. 	<li>Change root password:

    256. 

  256.       <br />

    257. 

  257.       <span class="code_tag">passwd</span></li>

    258. 

  258.   <li>Add new username -  yourself:<br />

    259. 

  259.     <span class="code_tag">adduser jsmith<br />

    260. 

  260.     visudo</span></li>

    261. 

  261. 	<li>Append this line to end of file (to navigate within 'vi' editor to create next line - use these: <strong>L</strong>, <strong>$</strong>, <strong>a</strong>, &lt;ENTER&gt;):<br />

    262. 

  262. 	  <span class="in_editor_tag">jsmith ALL=(ALL) ALL</span><br />

    263. 

  263. 	  To save and exit do: &lt;ESC&gt;, :wq, &lt;ENTER&gt;<br />

    264. 

  264. 	  <br />

    265. 

  265. 	</li>

    266. 

  266. 	<li>SSH configuration:<br />

    267. 

  267.       <span class="code_tag">nano /etc/ssh/sshd_config</span> - Find <br />

    268. 

  268.       <span class="in_editor_tag">Port 22</span> - and change number to something different (12345) to make hacking more difficult. <br />

    269. 

  269. - Set these to: <br />

    270. 

  270. <span class="in_editor_tag">PermitRootLogin no</span><br />

    271. 

  271. <span class="in_editor_tag">X11Forwarding no</span> <br />

    272. 

  272.  <span class="in_editor_tag">UsePAM no</span><br />

    273. 

  273. 	  - Append these lines to the very end:

    274. 

  274.       <br />

    275. 

  275.       <span class="in_editor_tag">UseDNS no</span>

    276. 

  276.       <br />

    277. 

  277.       <span class="in_editor_tag">AllowUsers jsmith</span><br /><br /></li>

    278. 

  278. 	<li>Secure slice with iptables

    279. 

  279.       <br />

    280. 

  280.       <span class="code_tag">iptables-save &gt; /etc/iptables.up.rules<br />

    281. 

  281.       nano /etc/iptables.test.rules</span></li>

    282. 

  282. 	<li>1. Copy contents of <a href="http://articles.slicehost.com/assets/2007/9/4/iptables.txt"><strong>this file</strong></a>	   -&gt;	and paste it into '</code>iptables.test.rules'.<br />

    283. 

  283.       2. Change port number to your port number on this line:<br />

    284. 

  284.       ...<br />

    285. 

  285.       <span class="in_editor_tag">-A INPUT -p tcp -m state --state NEW --dport 30000 -j ACCEPT</span><br />

    286. 

  286.       ...<br />

    287. 

  287.       3. Save and exit (Ctrl+O, Ctrl+X).<br />

    288. 

  288. 	  <br />

    289. 

  289. 	</li>

    290. 

  290. 	<li>Apply new iptables rules:

    291. 

  291.       <br />

    292. 

  292.       <span class="code_tag">iptables-restore &lt; /etc/iptables.test.rules</span></li>

    293. 

  293. 	<li>Save iptables rules permanently:

    294. 

  294.       <br />

    295. 

  295.       <span class="code_tag">iptables-save &gt; /etc/iptables.up.rules</span></li>

    296. 

  296. 	<li>Make sure iptables rules will apply when server is rebooted as well:

    297. 

  297.   <span class="code_tag"> nano /etc/network/interfaces</span></li>

    298. 

  298. 	<li>Add new line after these 2:

    299. 

  299.       <br />

    300. 

  300.       <span class="in_editor_normal">auto lo</span>      <br />

    301. 

  301.       <span class="in_editor_normal">iface lo inet loopback</span><br />

    302. 

  302.       <span class="in_editor_tag">pre-up iptables-restore &lt; /etc/iptables.up.rules</span><br />

    303. 

  303. Save and exit.</li>

    304. 

  304. 	<li>Reload SSH to use new ports and configurations:

    305. 

  305.       <br />

    306. 

  306.       <span class="code_tag"> /etc/init.d/ssh reload</span></li>

    307. 

  307. 	<li>Keep 'root' session running and open second session.<br />

    308. 

  308. 	  SSH login to your slice to new port, with your new username and password:

    309. 

  309.       <br />

    310. 

  310.       - Linux:  <span class="code_tag">ssh -p 12345 jsmith@123.45.6.78 </span>- Windows: <span class="code_tag">putty jsmith@123.45.6.78 12345</span></li>

    311. 

  311. 	<li>If you logged on successfully via your new username: 'jsmith' - you may close 'root' session now. <br />

    312. 

  312.     If not - you still have 'root' session opened to fix problems. In the worst case - you can use web based console shell login from your manage.slicehost.com dashboard to fix issues.

    313. 

  313. 	<span class="code_tag">sudo aptitude -y install screen</span></li>

    314. 

  314.   <li>Enter screen: <br />

    315. 

  315.     <span class="code_tag">screen </span>Screen is the great little utility that allows your terminal session activity to keep running (say lengthy builds) even if you were cut off or disconnected. You may reenter your abandoned screen session at a later time to check progress and continue working.<br />

    316. 

  316. - Usage notes:<br />	  

    317. 

  317. 	  - <u>new</u> screen session: <strong>screen</strong><br />	  

    318. 

  318. 	  - <u>attach</u> to existing screen session: <strong>screen -r</strong><br />

    319. 

  319. 	  - <u>list</u> all existing screen sessions: <strong>screen -list</strong> (output: <strong><em>12045</em></strong>.pts-0.MENSK (Detached), etc...)<br />	  

    320. 

  320. 	  - <u>attach</u> to existing screen session by number: <strong>screen -r 12045</strong><br />	  

    321. 

  321. 	  - <u>detach</u> from screen session and back to main terminal: <strong>Ctrl+A, D</strong><br />

    322. 

  322. 	  - to <u>rename</u> screen session from inside of it: <strong>Ctrl+A, Shift+A</strong> - and enter it's name.<br />	  

    323. 

  323. 	  - to <u>kill</u> current screen session: <strong>exit </strong>or <strong>Ctrl+A</strong><br />	  

    324. 

  324. 	  - to <u>kill all</u> screen sessions: <strong>Ctrl+A,\</strong><br />

    325. 

  325. 	  <br />

    326. 

  326. 	</li>

    327. 

  327. 	<li>Edit .bashrc file to make terminal window a bit more helpful:

    328. 

  328.       <br />

    329. 

  329.       <span class="code_tag">nano ~/.bashrc</span></li>

    330. 

  330. 	<li>Append these lines to the end of it:

    331. 

  331.       <br />

    332. 

  332.       <span class="in_editor_tag">export PS1="\[\e[32;1m\]\u\[\e[0m\]\[\e[32m\]@\h\[\e[36m\]\w \[\e[33m\]\$ \[\e[0m\]"</span><br />

    333. 

  333.       <span class="in_editor_tag">alias ll="ls -la"      </span><br />

    334. 

  334.       <span class="in_editor_tag">alias a2r="sudo /etc/init.d/apache2 stop &amp;&amp; sleep 2 &amp;&amp; sudo /etc/init.d/apache2 start"</span>      <br />

    335. 

  335.       <span class="in_editor_tag">alias n2r=&quot;sudo /etc/init.d/nginx stop &amp;&amp; sleep 2 &amp;&amp; sudo /etc/init.d/nginx start&quot;</span> <br />

    336. 

  336.       <span class="in_editor_tag">alias ver="cat /etc/lsb-release"</span><br />

    337. 

  337.       Save and exit. <br />

    338. 

  338.       <br />

    339. 

  339.   </li>

    340. 

  340. 	<li>Reload .bashrc to make changes active:

    341. 

  341.       <br />

    342. 

  342.       <span class="code_tag">source ~/.bashrc</span></li>

    343. 

  343. 	<li>Update sources:  <span class="code_tag">sudo aptitude update</span></li>

    344. 

  344. 	<li>Set system locale:

    345. 

  345.       <br />

    346. 

  346.       <span class="code_tag">sudo locale-gen en_US.UTF-8<br />

    347. 

  347.   sudo /usr/sbin/update-locale LANG=en_US.UTF-8</span></li>

    348. 

  348. 	<li>Upgrade system now:<br />

    349. 

  349.       <span class="code_tag">sudo aptitude -y safe-upgrade<br />

    350. 

  350.   sudo aptitude -y full-upgrade</span></li>

    351. 

  351. </ul>

    352. 

  352. <span class="sub_heading">Install PHP 5, Build Essentials and related libraries</span>

    353. 

  353. <ul>

    354. 

  354.   <li>Install Build essentials:<br />

    355. 

  355.     <span class="code_tag">sudo aptitude -y install build-essential</span></li>

    356. 

  356.   <li>Install PHP with php client and without apache (one long line):<br />

    357. 

  357.     <span class="code_tag" >sudo aptitude -y install php5-common php5-dev php5-mysql php5-sqlite php5-tidy php5-xmlrpc  php5-xsl php5-cgi php5-mcrypt php5-curl php5-gd php5-memcache php5-mhash php5-pspell php5-snmp php5-sqlite libmagick9-dev php5-cli</span></li>

    358. 

  358.   <li>Fix issues with imagick:<br />

    359. 

  359.     <span class="code_tag">sudo aptitude -y install make php-pear<br />

    360. 

  360.     sudo pecl install imagick</span> 

    361. 

  361.     (Just press &lt;ENTER&gt; at prompt)<br />

    362. 

  362.     <br />

    363. 

  363.       </li>

    364. 

  364.   <li>Adjust php.ini:<br /><span class="code_tag">sudo nano /etc/php5/cgi/php.ini</span>      Adjust memory limit to accomodate WordPress requirements:<br />

    365. 

  365.     Find line:<br /> 

    366. 

  366.     <code class="in_editor_tag">memory_limit = 16M</code> and change it to: <code class="in_editor_tag">memory_limit = 48M</code><br />

    367. 

  367.     <br />

    368. 

  368.     Append to the end of this file this line:<br />

    369. 

  369.     <code class="in_editor_tag">extension=imagick.so</code><br />

    370. 

  370.     <br />

    371. 

  371.       </li>

    372. 

  372.   <li>Install MySQL server, secure it and create database for wordpress (or other dynamic web app you will be using)<br />

    373. 

  373.     <span class="code_tag">sudo aptitude -y install mysql-server mysql-client libmysqlclient15-dev</span>Secure MySQL server:<br />

    374. 

  374.   <span class="code_tag">mysql_secure_installation</span></li>

    375. 

  375.   <li>Install subversion (best to install and upgrade wordpress is via subversion):<br />

    376. 

  376.     <span class="code_tag">sudo aptitude -y install subversion</span></li>

    377. 

  377. </ul>

    378. 

  378. <span class="sub_heading">Install Postfix to prepare e-mail capabilities for your web application</span>

    379. 

  379. <ul>

    380. 

  380.   <li>First - login into slicemanager at manage.slicehost.com, click &quot;DNS&quot; tab and &quot;Reverse DNS&quot;.<br />

    381. 

  381.     Replace record with: <code class="in_editor_tag">mail.mydomain.com.</code><br />

    382. 

  382.     </li>

    383. 

  383.   <li><span class="code_tag">sudo nano /etc/hostname</span>      Replace <span class="in_editor_tag">slicename</span> with <span class="in_editor_tag">mail.mydomain.com</span><br />

    384. 

  384.     <br />

    385. 

  385.       </li>

    386. 

  386.   <li>      <span class="code_tag">sudo nano /etc/hosts</span><br />

    387. 

  387.     Replace <span class="in_editor_tag">127.0.0.1 slicename</span> with <span class="in_editor_tag">127.0.0.1 mail.mydomain.com</span></li>

    388. 

  388.   <li>Reboot slice:<br />

    389. 

  389.     <span class="code_tag">sudo reboot</span></li>

    390. 

  390.   <li>When rebooted - check slice hostname (it must be mail.mydomain.com):<br />

    391. 

  391.     <span class="code_tag">hostname -f</span></li>

    392. 

  392.   <li>Install dns utils and check RDNS (by using your slice's IP address)<br />

    393. 

  393.     <span class="code_tag">sudo aptitude -y install dnsutils</span></li>

    394. 

  394.   <li>Check if RDNS propagated already:<br />

    395. 

  395.     <span class="code_tag">dig -x 123.45.6.78 <br />

    396. 

  396.     </span>If &quot;ANSWER SECTION&quot; still shows old name (or anytihng other than mail.mydomain.com) - you'll have to wait until propagation will finish before proceeding.</li>

    397. 

  397.   <li>      <span class="code_tag">sudo aptitude -y install postfix telnet mailx</span>

    398. 

  398.     Select &quot;Internet Site&quot;, and then for &quot;System mail name:&quot; -&gt; &quot;mail.mydomain.com&quot;.</li>

    399. 

  399.   <li>Redirect all email destined to 'root' toward 'jsmith':<br />

    400. 

  400.     <span class="code_tag">sudo nano /etc/aliases</span>Append this line to the end of file:<br />

    401. 

  401.     <span class="in_editor_tag">root: jsmith</span><br />

    402. 

  402.       </li>

    403. 

  403.   <li>Refresh aliases database now:<br />

    404. 

  404.     <span class="code_tag">sudo newaliases<br />

    405. 

  405.     </span></li>

    406. 

  406.   <li>Edit main.cf file:<br />

    407. 

  407.     <span class="code_tag">sudo nano /etc/postfix/main.cf<br />

    408. 

  408.     </span>- Replace: <span class="in_editor_tag">myorigin = /etc/mailname </span><br />

    409. 

  409.     - with this: <span class="in_editor_tag">myorigin = $mydomain</span><br />

    410. 

  410.     <br />

    411. 

  411.     - Replace this: <span class="in_editor_tag">mydestination = mail.mydomain.com, localhost.mydomain.com, , localhost</span><br />

    412. 

  412.     - with this: <span class="in_editor_tag">mydestination = $mydomain, localhost.$mydomain, localhost</span><br />

    413. 

  413.     <br />

    414. 

  414.     - Replace this: <span class="in_editor_tag">mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128</span><br />

    415. 

  415.     - with this: <span class="in_editor_tag">mynetworks = 127.0.0.0/8</span><br />

    416. 

  416.     <br />

    417. 

  417.       </li>

    418. 

  418.   <li>Restart postfix to make changes take effect:<span class="code_tag">    sudo /etc/init.d/postfix restart</span></li>

    419. 

  419.   <li>Test email sending capabilities. Run little php console prog to do it. Check if you receive email message.<br />

    420. 

  420.     <span class="code_tag">php -a<br />

    421. 

  421.     mail ('your@email.com', &quot;Hello from slice!&quot;, &quot;My email setup works!&quot;);<br />

    422. 

  422.   exit ();</span></li>

    423. 

  423.   <li>Follow this article if you want to <a href="http://articles.slicehost.com/2008/8/1/postfix-mx-records-and-receiving-emails">setup postfix to receive emails</a> as well (opening port 25 in firewall and configuring stuff):<br />

    424. 

  424.     But what we've done already is enough to have hosted portal with full outgoing email capabilities.<br />

    425. 

  425.   </li>

    426. 

  426. </ul>

    427. 

  427. <span class="sub_heading">Install and configure NGINX</span><br />

    428. 

  428. <ul><li>

    429. 

  429.     Install NGINX. Dependencies first. Check sysoev.ru website first for newer versions though.<br />

    430. 

  430.     <span class="code_tag">sudo aptitude -y install libpcre3 libpcre3-dev libpcrecpp0 libssl-dev zlib1g-dev<br />mkdir ~/sources<br />

    431. 

  431.     cd ~/sources/<br />

    432. 

  432.     wget http://sysoev.ru/nginx/nginx-0.6.32.tar.gz<br />

    433. 

  433.     tar -zxvf nginx-0.6.32.tar.gz<br />

    434. 

  434.     cd nginx-0.6.32<br />

    435. 

  435.     ./configure --sbin-path=/usr/local/sbin --with-http_ssl_module <br />

    436. 

  436.     make<br />

    437. 

  437.   sudo make install</span></li>

    438. 

  438. </ul>

    439. 

  439. <ul>

    440. 

  440.   <li>Start Nginx:<br />

    441. 

  441.     <span class="code_tag">sudo /usr/local/sbin/nginx</span></li>

    442. 

  442.   <li>Navigate to your slice's IP address to test that it works: http://123.45.6.78</li>

    443. 

  443.   <li>Stop Nginx:<br />

    444. 

  444.     <span class="code_tag">sudo kill `cat /usr/local/nginx/logs/nginx.pid`</span> </li>

    445. 

  445.   <li>Create NGINX init script<br />

    446. 

  446.     <span class="code_tag">sudo nano /etc/init.d/nginx</span> Copy/paste this text into it:<br />

    447. 

  447.     <pre>

    448. 

  448. #! /bin/sh

    449. 

  449. 

    450. 

  450. ### BEGIN INIT INFO

    451. 

  451. # Provides:          nginx

    452. 

  452. # Required-Start:    $all

    453. 

  453. # Required-Stop:     $all

    454. 

  454. # Default-Start:     2 3 4 5

    455. 

  455. # Default-Stop:      0 1 6

    456. 

  456. # Short-Description: starts the nginx web server

    457. 

  457. # Description:       starts nginx using start-stop-daemon

    458. 

  458. ### END INIT INFO

    459. 

  459. 

    460. 

  460. PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

    461. 

  461. 

    462. 

  462. 

    463. 

  463. 

    464. 

  464. 

    465. 

  465. 

    466. 

  466. DAEMON=/usr/local/sbin/nginx

    467. 

  467. NAME=nginx

    468. 

  468. DESC=nginx

    469. 

  469. 

    470. 

  470. test -x $DAEMON || exit 0

    471. 

  471. 

    472. 

  472. # Include nginx defaults if available

    473. 

  473. if [ -f /etc/default/nginx ] ; then

    474. 

  474.         . /etc/default/nginx

    475. 

  475. fi

    476. 

  476. 

    477. 

  477. set -e

    478. 

  478. 

    479. 

  479. case "$1" in

    480. 

  480.   start)

    481. 

  481.         echo -n "Starting $DESC: "

    482. 

  482.         start-stop-daemon --start --quiet --pidfile /usr/local/nginx/logs/$NAME.pid \

    483. 

  483.                 --exec $DAEMON -- $DAEMON_OPTS

    484. 

  484.         echo "$NAME."

    485. 

  485.         ;;

    486. 

  486.   stop)

    487. 

  487.         echo -n "Stopping $DESC: "

    488. 

  488.         start-stop-daemon --stop --quiet --pidfile /usr/local/nginx/logs/$NAME.pid \

    489. 

  489.                 --exec $DAEMON

    490. 

  490.         echo "$NAME."

    491. 

  491.         ;;

    492. 

  492. 

    493. 

  493.   restart|force-reload)

    494. 

  494.         echo -n "Restarting $DESC: "

    495. 

  495.         start-stop-daemon --stop --quiet --pidfile \

    496. 

  496.                 /usr/local/nginx/logs/$NAME.pid --exec $DAEMON

    497. 

  497.         sleep 1

    498. 

  498.         start-stop-daemon --start --quiet --pidfile \

    499. 

  499.                 /usr/local/nginx/logs/$NAME.pid --exec $DAEMON -- $DAEMON_OPTS

    500. 

  500.         echo "$NAME."

    501. 

  501.         ;;

    502. 

  502.   reload)

    503. 

  503.       echo -n "Reloading $DESC configuration: "

    504. 

  504.       start-stop-daemon --stop --signal HUP --quiet --pidfile /usr/local/nginx/logs/$NAME.pid \

    505. 

  505.           --exec $DAEMON

    506. 

  506.       echo "$NAME."

    507. 

  507.       ;;

    508. 

  508.   *)

    509. 

  509.         N=/etc/init.d/$NAME

    510. 

  510.         echo "Usage: $N {start|stop|restart|reload|force-reload}" >&#038;2

    511. 

  511.         exit 1

    512. 

  512.         ;;

    513. 

  513. esac

    514. 

  514. 

    515. 

  515. exit 0

    516. 

  516. </pre>

    517. 

  517.   </li>

    518. 

  518.   <li>Set it executable:<br />

    519. 

  519.     <span class="code_tag">sudo chmod +x /etc/init.d/nginx</span> </li>

    520. 

  520.   <li>Add it to the default run levels:<br />

    521. 

  521.     <span class="code_tag">sudo /usr/sbin/update-rc.d -f nginx defaults</span> </li>

    522. 

  522.   <li>Create folder layout:<br />

    523. 

  523.     <span class="code_tag">sudo mkdir /usr/local/nginx/sites-available  

    524. 

  524.     <br />

    525. 

  525.     sudo mkdir /usr/local/nginx/sites-enabled</span>    </li>

    526. 

  526.   <li>

    527. 

  527.     Adjust main NGINX configuration file to look in sites-enabled folder for vhosts:<span class="code_tag">    sudo nano /usr/local/nginx/conf/nginx.conf</span>    Delete all contents of this file and replace it with this:<br />

    528. 

  528.     <pre>

    529. 

  529. user www-data www-data;

    530. 

  530. worker_processes  4;

    531. 

  531. 

    532. 

  532. events {

    533. 

  533.     worker_connections  1024;

    534. 

  534. }

    535. 

  535. 

    536. 

  536. http {

    537. 

  537.     include       mime.types;

    538. 

  538.     default_type  application/octet-stream;

    539. 

  539. 

    540. 

  540.     sendfile        on;

    541. 

  541.     tcp_nopush      on;

    542. 

  542.     tcp_nodelay     off;

    543. 

  543.     keepalive_timeout  5;

    544. 

  544. 

    545. 

  545.     gzip  on;

    546. 

  546.     gzip_comp_level 2;

    547. 

  547.     gzip_proxied any;

    548. 

  548.     gzip_types      text/plain text/html text/css application/x-javascript text/xml application/xml

    549. 

  549.     application/xml+rss text/javascript;

    550. 

  550. 

    551. 

  551.     include /usr/local/nginx/sites-enabled/*;

    552. 

  552. }

    553. 

  553.     </pre>

    554. 

  554.     <br />

    555. 

  555.   </li>

    556. 

  556.   <li>Create default vhost in 'sites-available' folder:<br />

    557. 

  557.     <span class="code_tag">sudo nano /usr/local/nginx/sites-available/default</span>Copy/paste this text into it:<br />

    558. 

  558.   <pre>

    559. 

  559. server {

    560. 

  560.     listen       80;

    561. 

  561.     server_name  localhost;

    562. 

  562. 

    563. 

  563.     location / {

    564. 

  564.         root   html;

    565. 

  565.         index  index.php index.html index.htm;

    566. 

  566.     }

    567. 

  567. 

    568. 

  568. 

    569. 

  569.     # redirect server error pages to the static page /50x.html

    570. 

  570.     #

    571. 

  571.     error_page   500 502 503 504  /50x.html;

    572. 

  572.     location = /50x.html {

    573. 

  573.         root   html;

    574. 

  574.     }

    575. 

  575. 

    576. 

  576. }

    577. 

  577. </pre>

    578. 

  578.   </li>

    579. 

  579.   <li>Enable vhost by creating symlink:<br />

    580. 

  580.     <span class="code_tag">sudo ln -s /usr/local/nginx/sites-available/mydomain.com /usr/local/nginx/sites-enabled/mydomain.com</span></li>

    581. 

  581.   <li>Start NGINX:<br />

    582. 

  582.   <span class="code_tag">sudo /etc/init.d/nginx start</span>  Make sure that navigating to slice IP will show &quot;Welcome to nginx!&quot; default page.<br />

    583. 

  583.   <br />

    584. 

  584.   </li>

    585. 

  585.   <li>Create layouts for domains to be served.<br />

    586. 

  586.     <span class="code_tag">sudo mkdir /home/public_html<br />

    587. 

  587.     sudo mkdir -p /home/public_html/mydomain.com/{public,private,log,backup}</span></li>

    588. 

  588.   <li>Setup users and groups to manage portal:<br />

    589. 

  589.     <span class="code_tag">sudo -i<br />

    590. 

  590.       addgroup webmasters<br />

    591. 

  591.       usermod -G webmasters jsmith<br />

    592. 

  592.     </span>OPTIONAL: Do it for every user who will be allowed to manage files for the portal: <br />

    593. 

  593.     <span class="code_tag">    usermod -G webmasters user_2<br />

    594. 

  594.     usermod -G webmasters user_3<br />

    595. 

  595.     </span>Change ownership of main web files directory:<br />

    596. 

  596.     <span class="code_tag">chown -R jsmith.webmasters /home/public_html<br />

    597. 

  597.     chmod -R g+w /home/public_html<br />

    598. 

  598.     </span>Set group id to 'webmasters' for all newly created files and dirs.<br />

    599. 

  599.     <span class="code_tag">find /home/public_html -type d -exec chmod g+s {} \;<br />

    600. 

  600.   exit</span></li>

    601. 

  601.   <li>Create initial index.html file for the domain:<br />

    602. 

  602.     <span class="code_tag">sudo nano /home/public_html/mydomain.com/public/index.php</span>Paste this into the file:<br />

    603. 

  603.     <pre>&lt;?php echo phpinfo(); ?&gt;        </pre>

    604. 

  604.     First - create supporting wordpress-specific configuration files. 'wordpress_params.regular' - is basic wordpress config file that allows support for nice permalinks.<br />

    605. 

  605.     <span class="code_tag">sudo nano /usr/local/nginx/conf/wordpress_params.regular</span>...And paste into it the following contents:<br />

    606. 

  606.     <pre>  # WordPress pretty URLs: (as per dominiek.com)

    607. 

  607.   if (-f $request_filename) {

    608. 

  608.   break;

    609. 

  609.   }

    610. 

  610.   if (-d $request_filename) {

    611. 

  611.   break;

    612. 

  612.   }

    613. 

  613.   rewrite ^(.+)$ /index.php?q=$1 last;

    614. 

  614. 

    615. 

  615. 

    616. 

  616.   # Enable nice permalinks for WordPress: (as per Yawn.it)

    617. 

  617.   error_page  404  = //index.php?q=$uri;

    618. 

  618. 

    619. 

  619. </pre>

    620. 

  620.     Save and exit.<br />

    621. 

  621.     Next - create second version of NGinx-specific WordPress config file that allows support for nice permalinks + <a href="http://wordpress.org/extend/plugins/wp-super-cache/">WP Super Cache plugin</a>. WP Super Caching gives you extra horse power and juice to handle intense traffic and getting your portal seriously ready to be DIGG-ed.<br />

    622. 

  622.     <span class="code_tag">sudo nano /usr/local/nginx/conf/wordpress_params.super_cache</span>...And paste into it the following contents <a href="http://forum.slicehost.com/comments.php?DiscussionID=2087&amp;page=1">(Credits: Matt Stevens</a>):<br /><pre>

    623. 

  623. # if the requested file exists, return it immediately

    624. 

  624. if (-f $request_filename) {

    625. 

  625. break;

    626. 

  626. }

    627. 

  627. 

    628. 

  628. set $supercache_file '';

    629. 

  629. set $supercache_uri $request_uri;

    630. 

  630. 

    631. 

  631. if ($request_method = POST) {

    632. 

  632. set $supercache_uri '';

    633. 

  633. }

    634. 

  634. 

    635. 

  635. # Using pretty permalinks, so bypass the cache for any query string

    636. 

  636. if ($query_string) {

    637. 

  637. set $supercache_uri '';

    638. 

  638. }

    639. 

  639. 

    640. 

  640. if ($http_cookie ~* "comment_author_|wordpress|wp-postpass_" ) {

    641. 

  641. set $supercache_uri '';

    642. 

  642. }

    643. 

  643. 

    644. 

  644. # if we haven't bypassed the cache, specify our supercache file

    645. 

  645. if ($supercache_uri ~ ^(.+)$) {

    646. 

  646. set $supercache_file /wp-content/cache/supercache/$http_host/$1index.html;

    647. 

  647. }

    648. 

  648. 

    649. 

  649. # only rewrite to the supercache file if it actually exists

    650. 

  650. if (-f $document_root$supercache_file) {

    651. 

  651. rewrite ^(.*)$ $supercache_file break;

    652. 

  652. }

    653. 

  653. 

    654. 

  654. # all other requests go to WordPress

    655. 

  655. if (!-e $request_filename) {

    656. 

  656. rewrite . /index.php last;

    657. 

  657. }

    658. 

  658. 

    659. 

  659. </pre>

    660. 

  660.     Create vhost for domain mydomain.com:<br />

    661. 

  661.     <span class="code_tag">sudo nano /usr/local/nginx/sites-available/mydomain.com</span>...And paste into it the following contents:<br />

    662. 

  662.     <pre>server {

    663. 

  663. 

    664. 

  664.             listen   80;

    665. 

  665.             server_name  mydomain.com;

    666. 

  666.             rewrite ^/(.*) http://www.mydomain.com/$1 permanent;

    667. 

  667. 

    668. 

  668.            }

    669. 

  669. 

    670. 

  670. 

    671. 

  671. server {

    672. 

  672. 

    673. 

  673.             listen   80;

    674. 

  674.             server_name www.mydomain.com;

    675. 

  675. 

    676. 

  676.             access_log /home/public_html/mydomain.com/log/access.log;

    677. 

  677.             error_log /home/public_html/mydomain.com/log/error.log;

    678. 

  678. 

    679. 

  679.             location / {

    680. 

  680. 

    681. 

  681.                         root   /home/public_html/mydomain.com/public/;

    682. 

  682.                         index  index.php index.html;

    683. 

  683. 

    684. 

  684.                         # Basic version of WordPress parameters, supporting nice permalinks.

    685. 

  685.                         # include /usr/local/nginx/conf/wordpress_params.regular;

    686. 

  686.                         # Advanced version of WordPress parameters supporting nice permalinks and WP Super Cache plugin

    687. 

  687.                         include /usr/local/nginx/conf/wordpress_params.super_cache;

    688. 

  688.                         }

    689. 

  689. 

    690. 

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

    691. 

  691.             #

    692. 

  692.             location ~ \.php$ {

    693. 

  693.             fastcgi_pass 127.0.0.1:9000;

    694. 

  694.             fastcgi_index index.php;

    695. 

  695.             include /usr/local/nginx/conf/fastcgi_params;

    696. 

  696.             fastcgi_param SCRIPT_FILENAME /home/public_html/mydomain.com/public/$fastcgi_script_name;

    697. 

  697.             }

    698. 

  698.       }

    699. 

  699.    

    700. 

  700.   </pre>

    701. 

  701.     Above will append 'www' to all non-www requests - all requests for http://mydomain.com/dir/page will be redirected to -&gt; http://www.mydomain.com/dir/page.<br />

    702. 

  702.   As you can also see above we enabled 'wordpress_params.super_cache' settings. If for some reason you'll have problems - you may comment ' ....wordpress_params.super_cache' line out, disable wordpress WP Super Cache plugin via WordPress admin panel and uncomment '...wordpress_params.regular' settings (+restart Nginx). From my own test - they both works with or without WP Super Cache enabled and I'd definitely prefer WP Super Cache to be up and running.</li>

    703. 

  703. </ul>

    704. 

  704. <ul>

    705. 

  705.   <li>Enable site:<br />

    706. 

  706.     <span class="code_tag">sudo ln -s /usr/local/nginx/sites-available/mydomain.com /usr/local/nginx/sites-enabled/mydomain.com</span><br />

    707. 

  707.   </li>

    708. 

  708.   <li>Making NGinx to serve PHP and make it all start automatically after system restart (<a href="http://blog.zhekov.net/2007/8/15/nginx-php-fastcgi/">Credits</a>):<br />

    709. 

  709.     <span class="code_tag">sudo aptitude -y install libfcgi0<br />

    710. 

  710. cd /etc/default/ <br />

    711. 

  711. sudo wget -O php-fastcgi http://www.mensk.com/uploads/php-fastcgi.txt <br />

    712. 

  712. cd /etc/init.d/ <br />

    713. 

  713. sudo wget -O php-fastcgi http://www.mensk.com/uploads/php-fastcgi.rc.txt <br />

    714. 

  714. sudo chmod +x php-fastcgi <br />

    715. 

  715. sudo /usr/sbin/update-rc.d -f php-fastcgi defaults <br />

    716. 

  716. sudo /etc/init.d/php-fastcgi start</span> Restart NGINX:<br />

    717. 

  717.   <span class="code_tag">n2r</span> (or <strong>sudo /etc/init.d/nginx stop</strong>, <strong>sudo /etc/init.d/nginx start</strong>)<br />

    718. 

  718.   <br />

    719. 

  719.   </li>

    720. 

  720.   <li>Navigate to your website: http://mydomain.com you should be redirected to http://www.mydomain.com and then see phpinfo() screen...</li>

    721. 

  721.   <li>Reboot your slice and make sure that after restart everything still works (NGINX &amp; Co restarts properly)

    722. 

  722.     <br />

    723. 

  723.     <span class="code_tag">sudo reboot</span></li>

    724. 

  724. </ul>

    725. 

  725. <span class="sub_heading">Install and configure WordPress + configure WP Super Cache WordPress plugin to work with NGINX</span>

    726. 

  726. <ul><li>Install WordPress. Login to mysql console as mysql's root user:

    727. 

  727.   <span class="code_tag">mysql -u root -p</span></li>

    728. 

  728.   <li>Issue this command to create new username for WordPress database (replace username, password and database name with your values):<br />

    729. 

  729.     <span class="code_tag">mysql&gt; grant all privileges on *.* to wp_user@localhost identified by &quot;wp_pa55w0rd&quot;;<br />

    730. 

  730.     mysql&gt; create database wp_dbase;<br />

    731. 

  731.     mysql&gt; quit</span></li>

    732. 

  732.   <li>Get WordPress files directly from SVN repository. See this <a href="http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion">great article about using subversion to install and update WordPress</a>.<br />

    733. 

  733.     <span class="code_tag">cd /home/public_html/mydomain.com/public<br />

    734. 

  734.     sudo rm index.php<br />

    735. 

  735.     svn co http://svn.automattic.com/wordpress/tags/2.6 .<br />

    736. 

  736.     mv wp-config-sample.php wp-config.php<br />

    737. 

  737.     sudo nano wp-config.php<br />

    738. 

  738.     </span>Set database name, DB user name and password, Change DB prefix to something different (good security measure), save and exit.<strong><code><br />

    739. 

  739.     <br />

    740. 

  740.     </code></strong></li>

    741. 

  741.   <li>Adjust permissions:<br /><span class="code_tag">sudo chmod -R 777 /home/public_html/mydomain.com/public/wp-content<br />

    742. 

  742.     sudo chmod  666 /home/public_html/mydomain.com/public/wp-config.php</span></li>

    743. 

  743.   <li>Access your site: http://www.mydomain.com/<br />

    744. 

  744.     - Enter blog name, remember the password that wordpress gave you.<br />

    745. 

  745.     - Login as admin/password<br />

    746. 

  746.     - Click Users tab at upper right in admin panel<br />

    747. 

  747.     - Click on 'admin' user<br />

    748. 

  748.     - Change password to something secure and you'd remember.<br />

    749. 

  749.     - Logoff, Logon again with your new password.<br />

    750. 

  750.     - Goto Settings-&gt;Permalinks<br />

    751. 

  751.     - Set (x) &quot;Custom Structure&quot; -&gt; <span class="in_editor_tag">/%category%/%postname%/</span>, [Save Changes], ignore WordPress warning: &quot;You should update your .htaccess now.&quot; - it cannot find .htaccess - we are not running apache. <br />

    752. 

  752.   - Access your blog's &quot;About&quot; page - and voila - it should work just fine as this: http://www.mydomain.com/about/ (instead of default ugly: http://www.mydomain.com/?p=123)</li>

    753. 

  753.   <li>Download and unzip <a href="http://wordpress.org/extend/plugins/wp-super-cache/">WP Super Cache plugin</a> into '<strong>/home/public_html/mydomain.com/public/wp-content/plugins</strong>' directory. Activate it via Admin panel.<br />

    754. 

  754.     For FTP-ing purposes I use FileZilla configured to use SFTP. (I don't elaborate on specifics of installing and activating WordPress plugins in this document).<br />

    755. 

  755.     - Goto Plugins, activate &quot;WP Super Cache&quot;.<br />

    756. 

  756.     - Goto Settings-&gt;WP Super Cache and set (x) WP Super Cache Status to &quot;ON&quot;. [Update Status]. <br />

    757. 

  757.     You'll see bunch of warnings on this page regarding &quot;mod rewrite&quot; rules and &quot;.htaccess&quot; file. Just ignore these - we are not using Apache so WP Super Cache cannot find apache specific places to write settings. We did it for WP Super Cache already inside of 'wordpress_params.super_cache' - which contains &quot;translation&quot; of caching rules from Apache to Nginx.<br />

    758. 

  758.   Your WP Super Cache-ed blog should be up and running now at fullest speed.</li>

    759. 

  759.   <li>Make 'wp-content' directory a bit more secure:<span class="code_tag">  sudo chmod -R 755 /home/public_html/mydomain.com/public/wp-content</span>    - Goto Manage-&gt;Categories. Create few categories with subcategories.<br />

    760. 

  760.     - Goto Write-&gt;Post - create few posts and assign them to subcategory, publish, save.<br />

    761. 

  761.     - Access your posts - and see that they all have nice SEO-friendly URLs, thanks to custom wordpress-specific setups we included in our '<strong>/usr/local/nginx/sites-available/mydomain.com</strong>' file.<br />

    762. 

  762.   - This also works just fine with <a href="http://urbangiraffe.com/plugins/redirection/">John Godley's excellent redirection plugin</a> that supports flexible custom redirects with regular expressions.</li>

    763. 

  763.   <li>Customize your theme and go wild!  </li>

    764. 

  764. </ul>

    765. 

  765. <span class="sub_heading">Done!</span>

    766. 

  766. <ul><li>Enjoy your fresh shiny new WordPress blog, with nice SEO friendly permalinks enabled, ready to utilize powerful caching capabilities of <a href="http://wordpress.org/extend/plugins/wp-super-cache/">WP Super Cache plugin</a>, running under cutting edge <a href="http://nginx.net/">NGINX</a> web server, powered by top of the line <a href="http://www.ubuntu.com/getubuntu/download">Long Term Supported (up to 2013) Ubuntu 8.04 Hardy</a>, hosted by great <a href="http://www.slicehost.com/">VPS hosting team at SliceHost.com</a>!<br />

    767. 

  767.     <br />

    768. 

  768.   </li>

    769. 

  769. </ul>

    770. 

  770. </div><p><script type="text/javascript">SHARETHIS.addEntry({ title: "Perfect Setup: Ubuntu Hardy+Nginx+MySQL5+PHP5+Wordress", url: "http://www.mensk.com/webmaster-toolbox/perfect-ubuntu-hardy-nginx-mysql5-php5-wordpress/" });</script></p><div style="clear:both;"></div>

    771. 

  771. 			

    772. 

  772. 			<div class="postmeta">

    773. 

  773. 				Filed Under: <a href="http://www.mensk.com/category/webmaster-toolbox/" title="View all posts in Webmaster Toolbox" rel="category tag">Webmaster Toolbox</a><br />Tagged: <a href="http://www.mensk.com/tag/enginex/" rel="tag">enginex</a>, <a href="http://www.mensk.com/tag/mysql/" rel="tag">mysql</a>, <a href="http://www.mensk.com/tag/nginx/" rel="tag">nginx</a>, <a href="http://www.mensk.com/tag/php/" rel="tag">php</a>, <a href="http://www.mensk.com/tag/prefect-setup/" rel="tag">prefect setup</a>, <a href="http://www.mensk.com/tag/slicehost/" rel="tag">slicehost</a>, <a href="http://www.mensk.com/tag/ubuntu/" rel="tag">ubuntu</a>, <a href="http://www.mensk.com/tag/ubuntu-hardy/" rel="tag">ubuntu hardy</a>, <a href="http://www.mensk.com/tag/wordpress/" rel="tag">Wordpress</a>, <a href="http://www.mensk.com/tag/wp-super-cache-plugin/" rel="tag">wp super cache plugin</a>			</div>

    774. 

  774. 		 			

    775. 

  775. 			<!--

    776. 

  776. 			<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    777. 

  777. 			xmlns:dc="http://purl.org/dc/elements/1.1/"
    778. 

  778. 			xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    779. 

  779. 		<rdf:Description rdf:about="http://www.mensk.com/webmaster-toolbox/perfect-ubuntu-hardy-nginx-mysql5-php5-wordpress/"
    780. 

  780.     dc:identifier="http://www.mensk.com/webmaster-toolbox/perfect-ubuntu-hardy-nginx-mysql5-php5-wordpress/"
    781. 

  781.     dc:title="Perfect Setup: Ubuntu Hardy+Nginx+MySQL5+PHP5+Wordress"
    782. 

  782.     trackback:ping="http://www.mensk.com/webmaster-toolbox/perfect-ubuntu-hardy-nginx-mysql5-php5-wordpress/trackback/" />
    783. 

  783. </rdf:RDF>			-->

    784. 

  784. 			

    785. 

  785. 						

    786. 

  786. 		</div>

    787. 

  787. 		

    788. 

  788. 		<div class="adsense-post">

    789. 

  789. 		

    790. 

  790. 			<!--To activate your Google AdSense ad, go to your WP dashboard and go to Presentation -> Revolution Tech Options and enter your Google Adsense Code.-->

    791. 

  791. 			

    792. 

  792. 									

    793. 

  793. 		</div>

    794. 

  794. 			

    795. 

  795. 		<div class="comments">

    796. 

  796. 	

    797. 

  797. 			<h4>Comments</h4>

    798. 

  798. 			

    799. 

  799. <!-- You can start editing here. -->

    800. 

  800. 

    801. 

  801. <div id="commentblock">

    802. 

  802. 	<p id="comments"><b>61 Responses to &#8220;Perfect Setup: Ubuntu Hardy+Nginx+MySQL5+PHP5+Wordress&#8221;</b></p>

    803. 

  803. 

    804. 

  804. 	<ol class="commentlist">

    805. 

  805. 

    806. 

  806. 	

    807. 

  807. 		<li class="alt" id="comment-181">

    808. 

  808. 			Tony on

    809. 

  809. 						August 14th, 2008 12:07 pm 

    810. 

  810. 			<div class="commenttext">

    811. 

  811. 			<div style="float:left;margin:0px 10px 10px 0px;"><img alt='' src='http://0.gravatar.com/avatar/00c43a6cc4e581649c4e3292951c7871?s=60&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D60&amp;r=G' class='avatar avatar-60 photo' height='60' width='60' /></div><p>How does one go about setting up the iptables to allow postfix to work for email?</p>
    812. 

  812. <div style="clear:both;"></div>

    813. 

  813. 			</div>

    814. 

  814. 

    815. 

  815. 		</li>

    816. 

  816. 

    817. 

  817. 	

    818. 

  818. 	

    819. 

  819. 		<li class="" id="comment-182">

    820. 

  820. 			admin on

    821. 

  821. 						August 14th, 2008 12:16 pm 

    822. 

  822. 			<div class="commenttext">

    823. 

  823. 			<div style="float:left;margin:0px 10px 10px 0px;"><img alt='' src='http://0.gravatar.com/avatar/e303dc75e98569e785d014f77453c23a?s=60&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D60&amp;r=G' class='avatar avatar-60 photo' height='60' width='60' /></div><p>Here&#8217;s the SliceHost&#8217;s article on exactly this subject:<br />
    824. 

  824. <a href="http://articles.slicehost.com/2008/8/1/postfix-mx-records-and-receiving-emails" rel="nofollow">http://articles.slicehost.com/2008/8/1/postfix-mx-records-and-receiving-emails</a><br />
    825. 

  825. I think I might add this info to this article as well eventually.</p>
    826. 

  826. <p>Gleb</p>
    827. 

  827. <div style="clear:both;"></div>

    828. 

  828. 			</div>

    829. 

  829. 

    830. 

  830. 		</li>

    831. 

  831. 

    832. 

  832. 	

    833. 

  833. 	

    834. 

  834. 		<li class="alt" id="comment-183">

    835. 

  835. 			Tony on

    836. 

  836. 						August 14th, 2008 1:07 pm 

    837. 

  837. 			<div class="commenttext">

    838. 

  838. 			<div style="float:left;margin:0px 10px 10px 0px;"><img alt='' src='http://0.gravatar.com/avatar/00c43a6cc4e581649c4e3292951c7871?s=60&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D60&amp;r=G' class='avatar avatar-60 photo' height='60' width='60' /></div><p>When you have this line:</p>
    839. 

  839. <p>- Replace: myorigin = /etc/mailname<br />
    840. 

  840. - with this: myorigin = $mydomain</p>
    841. 

  841. <p>Do you actually mean replace it with the variable &#8220;$mydomain&#8221; or to actually put &#8220;$yahoo.com&#8221; or even just &#8220;yahoo.com&#8221; without the $ if my domain is yahoo.com</p>
    842. 

  842. <div style="clear:both;"></div>

    843. 

  843. 			</div>

    844. 

  844. 

    845. 

  845. 		</li>

    846. 

  846. 

    847. 

  847. 	

    848. 

  848. 	

    849. 

  849. 		<li class="" id="comment-184">

    850. 

  850. 			admin on

    851. 

  851. 						August 14th, 2008 1:46 pm 

    852. 

  852. 			<div class="commenttext">

    853. 

  853. 			<div style="float:left;margin:0px 10px 10px 0px;"><img alt='' src='http://0.gravatar.com/avatar/e303dc75e98569e785d014f77453c23a?s=60&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D60&amp;r=G' class='avatar avatar-60 photo' height='60' width='60' /></div><p>Good question &#8211; actually in this case it has to be used as is, no substitution needed. Regardless of your actual domain &#8211; this text line will have &#8220;$mydomain&#8221;.<br />
    854. 

  854. I guess i should of come up with more clear &#8220;generic&#8221; domain, like: &#8216;myhotsite.com&#8217; or something.</p>
    855. 

  855. <p>Here is the source for these detailed postfix configurations:<br />
    856. 

  856. <a href="http://articles.slicehost.com/2008/7/31/postfix-basic-settings-in-main-cf" rel="nofollow">http://articles.slicehost.com/2008/7/31/postfix-basic-settings-in-main-cf</a></p>
    857. 

  857. <p>Gleb</p>
    858. 

  858. <div style="clear:both;"></div>

    859. 

  859. 			</div>

    860. 

  860. 

    861. 

  861. 		</li>

    862. 

  862. 

    863. 

  863. 	

    864. 

  864. 	

    865. 

  865. 		<li class="alt" id="comment-186">

    866. 

  866. 			<a href='http://pvillega.wordpress.com/2008/08/16/slicehost/' rel='external nofollow' class='url'>SliceHost &laquo; So be IT</a> on

    867. 

  867. 						August 16th, 2008 11:56 am 

    868. 

  868. 			<div class="commenttext">

    869. 

  869. 			<div style="float:left;margin:0px 10px 10px 0px;"></div><p>[...] hecho, he encontrado este manual sobre como instalar WordPress (usando nginx, una versión ligera de Apache muy eficiente) en Slicehost, incluyendo los pasos para [...]</p>
    870. 

  870. <div style="clear:both;"></div>

    871. 

  871. 			</div>

    872. 

  872. 

    873. 

  873. 		</li>

    874. 

  874. 

    875. 

  875. 	

    876. 

  876. 	

    877. 

  877. 		<li class="" id="comment-188">

    878. 

  878. 			<a href='http://scottmotte.com/archives/253' rel='external nofollow' class='url'>Scott Motte &raquo; Blog Archive &raquo; Slicehost, nginx, mysql, php, wordpress setup</a> on

    879. 

  879. 						August 17th, 2008 1:52 pm 

    880. 

  880. 			<div class="commenttext">

    881. 

  881. 			<div style="float:left;margin:0px 10px 10px 0px;"></div><p>[...] Detailed tutorial on nginx, mysql, php, wordpress setup. [...]</p>
    882. 

  882. <div style="clear:both;"></div>

    883. 

  883. 			</div>

    884. 

  884. 

    885. 

  885. 		</li>

    886. 

  886. 

    887. 

  887. 	

    888. 

  888. 	

    889. 

  889. 		<li class="alt" id="comment-189">

    890. 

  890. 			windexh8er on

    891. 

  891. 						August 23rd, 2008 1:52 pm 

    892. 

  892. 			<div class="commenttext">

    893. 

  893. 			<div style="float:left;margin:0px 10px 10px 0px;"><img alt='' src='http://0.gravatar.com/avatar/6f839f6c6b435872ca40b76334e7a44a?s=60&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D60&amp;r=G' class='avatar avatar-60 photo' height='60' width='60' /></div><p>So&#8230;  I&#8217;m confused.  Why do you do this:</p>
    894. 

  894. <p>sudo ln -s /usr/local/nginx/sites-available/mydomain.com /usr/local/nginx/sites-enabled/mydomain.com</p>
    895. 

  895. <p>When you&#8217;re not linking to anything at this point?  Since there&#8217;s nothing in /usr/local/nginx/sites-available at that point in time you just end up with a broken symlink?!?!</p>
    896. 

  896. <p>Thx&#8230;</p>
    897. 

  897. <div style="clear:both;"></div>

    898. 

  898. 			</div>

    899. 

  899. 

    900. 

  900. 		</li>

    901. 

  901. 

    902. 

  902. 	

    903. 

  903. 	

    904. 

  904. 		<li class="" id="comment-190">

    905. 

  905. 			admin on

    906. 

  906. 						August 23rd, 2008 2:47 pm 

    907. 

  907. 			<div class="commenttext">

    908. 

  908. 			<div style="float:left;margin:0px 10px 10px 0px;"><img alt='' src='http://0.gravatar.com/avatar/e303dc75e98569e785d014f77453c23a?s=60&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D60&amp;r=G' class='avatar avatar-60 photo' height='60' width='60' /></div><p>I guess I have 2 places where I do that &#8211; first one is not necessary &#8211; second is done after mydomain.com files are created. So I guess you&#8217;re right &#8211; first one could be eliminated&#8230;</p>
    909. 

  909. <p>Gleb</p>
    910. 

  910. <div style="clear:both;"></div>

    911. 

  911. 			</div>

    912. 

  912. 

    913. 

  913. 		</li>

    914. 

  914. 

    915. 

  915. 	

    916. 

  916. 	

    917. 

  917. 		<li class="alt" id="comment-191">

    918. 

  918. 			windexh8er on

    919. 

  919. 						August 23rd, 2008 2:50 pm 

    920. 

  920. 			<div class="commenttext">

    921. 

  921. 			<div style="float:left;margin:0px 10px 10px 0px;"><img alt='' src='http://0.gravatar.com/avatar/6f839f6c6b435872ca40b76334e7a44a?s=60&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D60&amp;r=G' class='avatar avatar-60 photo' height='60' width='60' /></div><p>Also, can you post the actual files for the FastCGI?  The host that you are referencing in the doc is not valid anymore&#8230;</p>
    922. 

  922. <p>Thanks!</p>
    923. 

  923. <p>( i.e. <a href="http://zhware.net/files/nginx/" rel="nofollow">http://zhware.net/files/nginx/</a>* )</p>
    924. 

  924. <div style="clear:both;"></div>

    925. 

  925. 			</div>

    926. 

  926. 

    927. 

  927. 		</li>

    928. 

  928. 

    929. 

  929. 	

    930. 

  930. 	

    931. 

  931. 		<li class="" id="comment-192">

    932. 

  932. 			admin on

    933. 

  933. 						August 23rd, 2008 3:01 pm 

    934. 

  934. 			<div class="commenttext">

    935. 

  935. 			<div style="float:left;margin:0px 10px 10px 0px;"><img alt='' src='http://0.gravatar.com/avatar/e303dc75e98569e785d014f77453c23a?s=60&amp;d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D60&amp;r=G' class='avatar avatar-60 photo' height='60' width='60' /></div><p>&#8230;that&#8217;s why I never liked referring to too many other sites. It&#8217;s prone to get broken. I love having everything in one place.<br />
    936. 

  936. Thanks for catch &#8211; fixed &#8211; files now at mensk.com &#8211; reload the page and check for new urls:<br />
    937. 

  937. <a href="http://www.mensk.com/uploads/php-fastcgi.rc.txt" rel="nofollow">http://www.mensk.com/uploads/php-fastcgi.rc.txt</a><br />
    938. 

  938. <…
    939.

Large files files are truncated, but you can click here to view the full file