41 lines
1.5 KiB
HTML
41 lines
1.5 KiB
HTML
<html>
|
|
<body>
|
|
<h1>Repository usage</h1>
|
|
|
|
<h2>SVN update</h2>
|
|
<p>
|
|
When doing an SVN update watch for changes in the following files:
|
|
<ul>
|
|
<li>code/config/*</li>
|
|
<li>code/htdocs/config2/settings-dist.inc.php</li>
|
|
<li>code/htdocs/doc/sql/*</li>
|
|
<li>code/htdocs/lib/settings-dist.inc.php</li>
|
|
<li>code/htdocs/documentation/*</li>
|
|
</ul>
|
|
In most cases you have to review the changes and update your configuration
|
|
or database. The update is done manually.
|
|
<ul>
|
|
<li>Changes in the setting files may have to be modified in the local config file.</li>
|
|
<li>
|
|
Changes in SQL table definitions have to be installed in the database via
|
|
phpmyadmin. If there is a new table SQL file, you can create the new column
|
|
or modify the existing column.<br />
|
|
<br />
|
|
If data.sql changes, you have to execute it with mysql binary
|
|
<pre>cat data.sql | mysql -uroot -p <database></pre>
|
|
If maintain.php changes, you have to execute it with you webbrowser.<br />
|
|
<br />
|
|
</li>
|
|
<li>
|
|
Changes in the documentation should be reviewed, of course.
|
|
</li>
|
|
</ul>
|
|
</p>
|
|
|
|
<h2>SVN commit</h2>
|
|
<p>
|
|
Commit your changes to the dev branch when you have finished the developlment.<br />
|
|
When these changes have been tested, they will be merged into the trunk.
|
|
</p>
|
|
</body>
|
|
</html> |