Author: buildbot
Date: Mon Oct 15 15:15:00 2012
New Revision: 835127
Log:
Staging update by buildbot for vcl
Modified:
websites/staging/vcl/trunk/content/ (props changed)
websites/staging/vcl/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.html
Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Oct 15 15:15:00 2012
@@ -1 +1 @@
-1398323
+1398328
Modified:
websites/staging/vcl/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.html
==============================================================================
---
websites/staging/vcl/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.html
(original)
+++
websites/staging/vcl/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.html
Mon Oct 15 15:15:00 2012
@@ -115,16 +115,13 @@
</li>
<li>
-<p>This step updates the mysql schema.</p>
+<p>This step <strong>updates the mysql schema</strong>. <em>Note</em>: A new
resource group is added in update-vcl.sql - <strong>all profiles</strong>.
Access to manage the group is added to the VCL->admin node in the privilege
tree if that node exists. If not, you will need to add it manually after
starting httpd again. To add it manually, pick a node in the privilege tree,
scroll to Resources, click Add Resource Group, select serverprofile/all
profiles from the drop-down box, check available, administer, manageGroup, and
manageMapping, and click Submit New Resource Group.</p>
<div class="codehilite"><pre><span class="n">cd</span> <span
class="sr">/root/</span><span class="n">apache</span><span
class="o">-</span><span class="n">VCL</span><span class="o">-</span><span
class="mf">2.3</span>
<span class="n">mysql</span> <span class="n">vcl</span> <span
class="o"><</span> <span class="n">mysql</span><span class="o">/</span><span
class="n">update</span><span class="o">-</span><span class="n">vcl</span><span
class="o">.</span><span class="n">sql</span>
</pre></div>
</li>
-</ol>
-<p><strong>Note</strong>: A new resource group is added in update-vcl.sql -
<strong>all profiles</strong>. Access to manage the group is added to the
VCL->admin node in the privilege tree if that node exists. If not, you will
need to add it manually after starting httpd again. To add it manually, pick a
node in the privilege tree, scroll to Resources, click Add Resource Group,
select serverprofile/all profiles from the drop-down box, check available,
administer, manageGroup, and manageMapping, and click Submit New Resource
Group.</p>
-<ol>
<li>
<p>Update the web code. This step we will move the 2.2.1 web directory out of
the way, so we can copy in the new web code base. After copying in the new
code, we will migrate your configuration changes. These instructions assume
that you installed the vcl web code at /var/www/html/vcl. If you installed it
elsewhere, replace /var/www/html/vcl with your vcl web root.</p>
<div class="codehilite"><pre><span class="n">cd</span> <span
class="sr">/var/</span><span class="n">www</span><span class="o">/</span><span
class="n">html</span>
@@ -148,21 +145,14 @@ cd ~/vcl_2.2.1_web/.ht-inc
cp conf.php secrets.php pubkey.pem keys.pem /var/www/html/vcl/.ht-inc</p>
</li>
<li>
-<p>Make the maintenance directory writable by the web server user. You will
need to know what user httpd runs as on your server. This can be found with</p>
-<div class="codehilite"><pre><span class="n">ps</span> <span
class="n">aux</span> <span class="o">|</span> <span class="nb">grep</span>
<span class="n">httpd</span>
+<p>Make the maintenance directory writable by the web server user. Normally
this is the apache user, if using a different user change below cmd
accordingly.</p>
+<div class="codehilite"><pre><span class="nb">chown</span> <span
class="n">apache</span> <span class="sr">/var/</span><span
class="n">www</span><span class="sr">/html/</span><span
class="n">vcl</span><span class="sr">/.ht-inc/m</span><span
class="n">aintenance</span>
</pre></div>
</li>
-</ol>
-<p>Look at the first column. One process will be owned by root. The remaining
processes will be owned by the web server user. Now, own
/var/www/html/vcl/.ht-inc/maintenance to that user (replacing 'apache' with
your web server user if different):</p>
-<div class="codehilite"><pre> <span class="nb">chown</span> <span
class="n">apache</span> <span class="sr">/var/</span><span
class="n">www</span><span class="sr">/html/</span><span
class="n">vcl</span><span class="sr">/.ht-inc/m</span><span
class="n">aintenance</span>
-</pre></div>
-
-
-<ol>
<li>
-<p>Make some changes to conf.php:</p>
+<p>Make changes to conf.php:</p>
<p>a. A new user group permission that controls who can manage block
allocations globally or for a specific affiliation has been added. It can be
granted to any user group under Privileges->Additional User
Permissions->Manage Block Allocations. Users with this permission are
notified of new block allocation requests. Remove</p>
<div class="codehilite"><pre> <span class="nv">$blockNotifyUsers</span>
</pre></div>
@@ -170,7 +160,7 @@ cp conf.php secrets.php pubkey.pem keys.
</li>
</ol>
-<p>rom conf.php.</p>
+<p>from conf.php.</p>
<div class="codehilite"><pre><span class="n">b</span><span class="o">.</span>
<span class="n">A</span> <span class="k">new</span> <span class="n">user</span>
<span class="n">group</span> <span class="n">permission</span> <span
class="n">that</span> <span class="n">controls</span> <span
class="n">who</span> <span class="n">can</span> <span class="n">look</span>
<span class="n">up</span> <span class="n">users</span> <span
class="n">globally</span> <span class="ow">or</span> <span class="k">for</span>
<span class="n">a</span> <span class="n">specific</span> <span
class="n">affiliation</span> <span class="n">has</span> <span
class="n">been</span> <span class="n">added</span><span class="o">.</span>
<span class="n">It</span> <span class="n">can</span> <span class="n">be</span>
<span class="n">granted</span> <span class="n">to</span> <span
class="n">any</span> <span class="n">user</span> <span class="n">group</span>
<span class="n">under</span> <span class="n">Privileges</span><sp
an class="o">-></span><span class="n">Additional</span> <span
class="n">User</span> <span class="n">Permissions</span><span
class="o">-></span><span class="n">User</span> <span
class="n">Lookup</span><span class="o">.</span> <span class="n">Users</span>
<span class="n">with</span> <span class="n">this</span> <span
class="n">permission</span> <span class="n">can</span> <span
class="n">look</span> <span class="n">up</span> <span
class="n">information</span> <span class="n">about</span> <span
class="n">other</span> <span class="n">users</span><span class="o">.</span>
<span class="n">Remove</span>
<span class="o">::</span><span class="p">:</span><span
class="n">BashLexer</span>
