[Sommaire] [Imprimer]

   1  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   2  <html xmlns="http://www.w3.org/1999/xhtml">
   3  <head>
   4  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
   5      <title>b2evolution Automated Install</title>
   6  </head>
   7  <body>
   8      <h1>b2evolution Automated Install/Upgrade</h1>
   9      <h2>Purpose</h2>
  10      <p>This document describes how you can most easily automate the installation of the <a href="http://b2evolution.net/">b2evolution</a> blog software of a hosting account.</p>
  11      <p>This document also addresses automated upgrade of b2evolution.</p>
  12      <h2>Intended audience</h2>
  13      <ul>
  14          <li>Web hosting providers</li>
  15          <li>Web hosting tool providers</li>
  16      </ul>
  17      <h2>Operating environment</h2>
  18      <p>b2evolution is a PHP + MySQL web application. At this point we strongly recommend the use of PHP 5 as well as MySQL 5 although b2evolution can work perfectly fine on PHP 4.3 and MySQL 4.0.</p>
  19      <p>Please see our <a href="http://manual.b2evolution.net/System_requirements">System Requirements page</a> for details.</p>
  20      <h2>Basics</h2>
  21      <p>Automated installation of web applications such as b2evolution typically involves these steps:</p>
  22      <ol>
  23          <li>Place the application files in the destination directory.</li>
  24          <li>Create a MySQL User, Database and privileges of the user on the database.</li>
  25          <li>Write/update a configuration file with the database login information.</li>
  26          <li>Run the install/setup script of the application.</li>
  27          <li>Delete the installer.</li>
  28      </ol>
  29      <h1>Recommended Auto Install procedure</h1>
  30      <h2>1. Place the application files in the destination directory</h2>
  31      <p>We recommend you prompt the user for a directory to install b2evolution into. If he provides an empty directory, b2evolution would be installed in his web root. Let's pretend the user chose to instal into www/myblog/ .</p>
  32      <p>Once the destination directory selected/created, you need to copy all the contents of the /blogs/ directory as provided in the b2evolution package into the destination directory www/myblog/ . <strong>You should not copy the package info files such as the /doc/ directory.</strong></p>
  33      <h3>File permissions</h3>
  34      <p>You should make sure that the contents of the www/myblog/media/ directory are writable by PHP. This is the place where the user can upload pictures to insert in hos blog posts, etc.</p>
  35      <h2>2. Create a MySQL database</h2>
  36      <p>You will need to provide b2evolution with a database where it will create its own tables.</p>
  37      <h2>3. Write the configuration file</h2>
  38      <p>At this point, you need to write/update the basic configuration file you previously copied to www/myblog/conf/_basic_conf.php .</p>
  39      <p>You need to update the following lines with the database login info:</p>
  40      <pre>$db_config = array(
  41   'user'          =&gt; 'demouser',     // your MySQL username
  42   'password'      =&gt; 'demopass',     // ...and password
  43   'name'          =&gt; 'b2evolution',  // the name of the database
  44   'host'          =&gt; 'localhost',    // MySQL Server (typically 'localhost')
  45   );
  46  </pre>
  47      <p>Then, you should update the user's email address on this line:<br>
  48      </p>
  49      <pre>$admin_email = 'postmaster@localhost';</pre>
  50      <p>and you need to tell b2evolution that the configuration has been done by replacing</p>
  51      <pre>$config_is_done = 0;</pre>
  52      <p>with</p>
  53      <pre>$config_is_done = 1;</pre>
  54      <h2>4. Run the install script</h2>
  55      <p>At this point you can call b2evolution's install script through an HTTP GET request (wget, cURL, etc..) of this form:</p>
  56      <pre>http://example.com/myblogs/install/index.php?locale=en-US&amp;action=newdb&amp;create_sample_contents=1</pre>
  57      <h3>New in b2evo 2.0.2:</h3>
  58      <p>You can detect that installation has been successful by parsing the output and locating the string &lt;evo:password&gt; .</p>
  59      <p>Furthermore, you can parse out the password that has been created for the user by parsing it out between &lt;evo:password&gt; and &lt;/evo:password&gt;. Example:</p>
  60      <pre>&lt;evo:password&gt;testpwd&lt;/evo:password&gt;</pre>
  61      <h2>5. Delete the install folder</h2>
  62      <p>At this point, the www/myblog/install/ folder is no longer needed. We recommend you delete it, both to save space and improve security.</p>
  63      <p>Note: when upgrading, you will need a <strong>new</strong> install folder. So there is really no point in keeping it.</p>
  64      <h1>Recommended Auto Upgrade procedure</h1>
  65      <p>Any newer version of b2evolution can upgrade its database from any older version. It will also refuse to update if for some reason you try to &quot;downgrade&quot; it.</p>
  66      <h2>0. Detecting which version of b2evolution is installed</h2>
  67      <p>Open the file www/myblog/conf/_application.php and parse out the line that says:</p>
  68      <pre>$app_version = '2.0.2-alpha';</pre>
  69      <p>You can safely ignore the part after the hyphen (-). The version <strong>number</strong> will always change when a new version is released.</p>
  70      <p>You can compare this version number with the new one you have available.</p>
  71      <p>Note: if using PHP, you can use version_compare() which does all the work for you.</p>
  72      <h2>1. Getting confirmation that the user wants to upgrade</h2>
  73      <p>You should warn the user that any customizations he may have added to his existing b2evolution may not work properly with the new version. This especially applies to custom skins, custom plugins and custom locales (translations).</p>
  74      <p>Optionally, you may want to provide checkboxes for the following:</p>
  75      <ul>
  76          <li>Reset skins</li>
  77          <li>Reset plugins</li>
  78          <li>Reset locales (translations)</li>
  79      </ul>
  80      <h2>2. Replacing the files</h2>
  81      <p>Delete all files &amp; folders from the <strong>www/myblog/</strong> except:</p>
  82      <ul>
  83          <li> <strong>www/myblog/media/</strong> (where the user has uploaded his content files).</li>
  84          <li>If the user hasn't requested a reset of these, also keep:
  85              <ul>
  86                  <li><strong>www/myblog/skins</strong>/</li>
  87                  <li><strong>www/myblog/plugins/</strong></li>
  88                  <li><strong>www/myblog/locales/</strong></li>
  89              </ul>
  90          </li>
  91          <li><strong>www/conf/_basic_config.php</strong> (no need to rewrite that one)</li>
  92      </ul>
  93      <p><strong>Warning: if the user has installed into the root folder, you may not want to delete &quot;all files &amp; folders&quot;!</strong> In this case, the folders you should delete are:</p>
  94      <ul>
  95          <li>www/cron/</li>
  96          <li>www/htsrv/</li>
  97          <li>www/inc/</li>
  98          <li>www/install/ (if it's still there)</li>
  99          <li>www/locales/ (if requested)</li>
 100          <li>www/plugins/ (if requested)</li>
 101          <li>www/rsc/</li>
 102          <li>www/skins/ (if requested)</li>
 103          <li>www/skins_adm/</li>
 104          <li>www/xmlsrv/</li>
 105      </ul>
 106      <p>After than copy all files from the new b2evolution's /blogs/ folder, <strong>except /blogs/media/ and /blogs/conf/_basic_config.php </strong>.</p>
 107      <h2>3. Upgrading the database</h2>
 108      <p>At this point you can call b2evolution's install script through an HTTP GET request (wget, cURL, etc..) of this form:</p>
 109      <pre>http://example.com/myblogs/install/index.php?locale=en-US&amp;action=evoupgrade
 110  </pre>
 111      <h2>4. Delete the install folder</h2>
 112      <p>At this point, the www/myblog/install/ folder is no longer needed. We recommend you delete it, both to save space and improve security.</p>
 113      <p>Note: when upgrading again, you will need a <strong>new</strong> install folder. So there is really no point in keeping it.</p>
 114      <h1></h1>
 115  </body>
 116  </html>