These sites:
<ul>
<li><a href="http://chess.eecs.berkeley.edu"><code>http://chess.eecs.berkeley.edu</code></a>
<li><a href="http://www.e3s-center.org"><code>http://www.e3s-center.org</code></a>
<li><a href="http://embedded.eecs.berkeley.edu"><code>http://embedded.eecs.berkeley.edu</code></a>
<li><a href="http://www.icyphy.org"><code>http://www.icphy.org</code></a>
<li><a href="http://www.terraswarm.org"><code>http://www.terraswarm.org</code></a>
<li><a href="http://www.truststc.org"><code>http://www.truststc.org</code></a>

</ul>
are all served from <code>moog.eecs.berkeley.edu</code>.
These sites use are Apache virtual hosts.


<p>We used to use <code>carson.eecs.berkeley.edu</code> as a test
server for <code>moog</code>.  The corresponding
development websites were:
<ul>
<li><a href="https://chesstst.eecs.berkeley.edu:444/"><code>https://chesstst.eecs.berkeley.edu:444/</code></a>
<li><a href="http://embeddedtst.eecs.berkeley.edu"><code>https://embeddedtst.eecs.berkeley.edu:448/</code></a>
<li><a href="https://trustt.eecs.berkeley.edu:446/"><code>https://trustt.eecs.berkeley.edu:446/</code></a>
</ul>
The development websites all share a common IP address
and use Apache's virtual host facility.  Each of the 
development websites use SSL on a different port.
<p>The source for the website is on <code>repo.eecs.berkeley.edu</code>.
<p>moog is a Red Hat machine
managed by Mary Stewart and Christopher Brooks.


<h2>PhP</h2>
The websites use PhP.

<h2>Log Files</h2>
<h3>PhP Log Files</h3>
On moog, the PhP logs can be found in
<code>/export/home1/tmp/php.err</code>.  If you 
run into problems such as a blank page, this is
the place to look for error messages

<h3>Apache Log Files</h3>
On moog, the Apache logs files can
be found in <code>/usr/local/apache/logs</code>.
Note that we run cronolog, which rotates the logs
every night.

<h3>JSP logs</h3>
On moog, the JSP log files can be
found in <code>/usr/local/tomcat/logs</code>.
We use JSP for changing passwords and managing calendars.

<h2>MySQL</h2>
The easiest way to administer MySQL is via the web:
<menu>
<li><a href="http://chess.eecs.berkeley.edu/mysql">http://chess.eecs.berkeley.edu/mysql</a>
- For the production servers: chess, embedded and trust
<li><a href="http://chesstst.eecs.berkeley.edu/mysql">http://chesstst.eecs.berkeley.edu/mysql</a>
- For the test servers: chesstst, embeddedtst, trustt
</menu>
For this to work, you must have a website account in
the <code>webmaster</code> workgroup.

<h2>Accounts</h2>
To work on the website, you will need these accounts
<ul>
<li> Unix account on moog.eecs.berkeley.edu.
To get an account, ask root@moog.eecs.berkeley.edu,
who will run <code>adduser</code>.  Note that
we actually do our work as the <code>www</code>
user, so you will need the <code>www</code> password
as well.  Carson mounts the eecs file system, so
it when the account is created, send email to
<code>help@eecs</code> asking that the user's home
directory be exported to <code>eal-c</code>.
<li> Unix account on andrews.eecs.berkeley.edu.
To get this account, ask root@andrews.eecs.berkeley.edu,
who will run something like:
<pre>
 useradd -u 16879 -g staff -G webmastr,cvs,mailman -s /usr/local/bin/tcsh bira
</pre>
and then edit <code>/etc/passwd</code> and add the
user's name.
<br>You will also need the root and www passwords.
<li>Website accounts in the webmaster group on
all six sites (3 production, 3 development).
</ul>

<h2>General Development Procedure</h2>
Since development involves multiple windows, you might
find it easier to use Windows remote desktop on 
hermes or newton and set up ssh windows there.
<ol>
<li>Log on to <code>carson.eecs.berkeley.edu</code> using
ssh and then su to www:
<pre>
su - www
</pre>
<li>As <code>www</code> on <code>carson</code>, update
the tree:
<pre>
cd ~www/php
svn update
</pre>
Note that there will be some <code>config.php</code>
files that will be locally modified.  These files are
used to differentiate between the development websites
and the production websites.

<li>Make your changes on <code>carson</code>, checking
the results on the development servers:
<ul>
<li><a href="http://chesstst.eecs.berkeley.edu"><code>http://chesstst.eecs.berkeley.edu</code></a>
<li><a href="http://embeddedtst.eecs.berkeley.edu"><code>http://embeddedtst.eecs.berkeley.edu</code></a>
<li><a href="http://trustt.eecs.berkeley.edu"><code>http://trustt.eecs.berkeley.edu</code></a>
</ul>
<li>When everything looks good, check in your changes
as the <code>www</code> user:
<pre>
cvs commit -m "Fix security problem surrounding globals" foo.php
</pre>
<b>NOTE</b>: the log messages should be clear and describe
what was done.  A blank message or a "fixed bug" message
will not do.
<li>Log on to andrews using ssh and the su to www:
<pre>
su - www
</pre>
<li>To be safe, you might want to check that the
websites are working <b>before</b> you make your changes:
<ul>
<li><a href="http://chess.eecs.berkeley.edu"><code>http://chess.eecs.berkeley.edu</code></a>
<li><a href="http://embedded.eecs.berkeley.edu"><code>http://embedded.eecs.berkeley.edu</code></a>
<li><a href="http://www.truststc.org"><code>http://www.truststc.org</code></a>
</ul>
<li>Once you are convinced the sites are working,
as <code>www</code>, update the php and check your changes:
<pre>
cd ~www/php
cvs update
</pre>
</ol>