Originally written 20050423
Keep in mind that this is very untested/developmental code. I haven't even tried to run it. This is mostly just a reminder to us, I guess.
Note that you can now download fairly recent snapshot tarballs. (instead of steps 1-8) Please note that these may be buggier than the latest code in CVS (so don't file a bug report until you've tried the latest CVS code), which you can get by doing steps 1-8.
- cd path/to/place/you/want/to/install
- cvs -d:pserver:firstname.lastname@example.org:/cvsroot/opensharelive export -Dtomorrow F3
- mv F3/* .
- mv sharelive/* .
- rm -r F3 sharelive
- cd backend
- ln -s . backend
- cd ..
- vim Connections/Default.php
- (of course you may substitute with your favorite editor)-set the blank values to the correct ones for your MySQL server
- OK. Now you need to get the DB structure and put it on your MySQL server.
- You may need to initialize the DB with some rows/records.
- If I have foreseen all potential problems, you should have something that does something, at least. One of my goals is to get it runnable anyplace.
If you know some PHP and want to improve/fix/whatever code, you can help us out by submitting a patch. here's how (does not assume CVS knowledge):
- cvs -d:pserver:email@example.com:/cvsroot/opensharelive checkout F3
- cd F3
- Now you can edit the code just as you would any other code (leave the directories named CVS alone unless you know what you are doing)
- If you spend alot of time (more than 5 hours) doing this, you should probably run "cvs update -dP" periodically.
- When you are done, run "cvs diff -u > ../patch_file"
- Goto our patch place, and Submit New, attaching the aformentioned patch_file.
- Someone will look it over and possibly commit it to CVS for all to enjoy.