This is going to just briefly overview what is needed to experiment with a CVS version of FreeMED. For those who are hungry for a new feature, crippled by a particular bug, or just helping to test FreeMED, this document is for you.
Currently we keep CVS versions at sourceforge. Jeff is thinking of switching to the more powerful "subversion" program, which would mean that we would be moving the development version off sourceforge.
--- The first thing to do is to backup both your database and your orginal versions of FreeMED and PHPwebtools.
this command will make a directory called freemed_backup in your home directory. (You do not want to do this as root...)
and then the same for phpwebtools
Now you are ready to backup the database...
Usually the freemed database is named "freemed"... This will ask for the root mysql password.
Now just to check that this all worked do a
This should display the contents of the sql file... dont be concerned if you do not understand this. Be concerned if there is nothing there...
Once you have safely backed up the old system and database you are ready to download the CVS version
Then enter the root password... you will need to do the following as root
move to the share directory
remove the current freemed directory
remove the current phpwebtools... now the magic starts...
login anonymously to the cvs server using the above command
checkout the freemed directory. if you are in /usr/share this will automatically checkout freemed to /usr/share/freemed now we do the same thing with phpwebtools.
Now you need to edit the /usr/share/freemed/lib/settings.php to match your settings. To show the new javascript top menu, change in lib/settings.php define ('TEMPLATE', "newskin");
Now type cd /usr/share
chown -R apache:apache freemed/ phpwebtools/
Once this is done you can test out the new version
Sometimes a CVS version changes the way that the underlying database works, if this happens, we will usually work through the issue on the support list. There we can identify the problem and create a "fixer script" or something. For minor number updates this should not happen.
