Welcome to the future web site of the Open Source project for ShareLive.

NOTE: You are looking at an archived page; it is no longer updated, so much of this information is probably inaccurate. For up-to-date news, see the home page.

Brief Menu

• ShareLive main site (the mothersite)
• SourceForge project info (with links to other pages that SF generates)
• temporary forum (on sharelive.com board)
• Nightly CVS Respiritory Tarball (Really only useful for backups, or if you need access to the whole respiritory w/o an internet conection.)
• Stats

Attention all ShareLive.com refugees!

Please see my informational page on the closing

Summary: sharelive is closing on June 4th, but OpenShareLive will remain

Update: or maybe not. see the page for details.

News/Updates

• 2005-05-30: last update that is done this way, i think. backing up....
• 2005-05-26: seperate refugee page
• 2005-05-26: Added SL.com refugee info above
• 2005-05-26: Database structure publically released. HOWTO:run (below) updated accordingly.

Be sure to see the SF news as well.

HOWTO: Run

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.

1. cd path/to/place/you/want/to/install
2. cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/opensharelive export -Dtomorrow F3
3. mv F3/* .
4. mv sharelive/* .
5. rm -r F3 sharelive
6. cd backend
7. ln -s . backend
8. cd ..
9. vim Connections/Default.php
10. (of course you may substitute with your favorite editor)-set the blank values to the correct ones for your MySQL server
11. OK. Now you need to get the DB structure and put it on your MySQL server.
12. You may need to initialize the DB with some rows/records.
13. 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.

HOWTO: Contribute

20050423

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):

1. cvs -d:pserver:anonymous@cvs.sf.net:/cvsroot/opensharelive checkout F3
2. cd F3
3. 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)
4. If you spend alot of time (more than 5 hours) doing this, you should probably run "cvs update -dP" periodically.
5. When you are done, run "cvs diff -u > ../patch_file"
6. Goto our patch place, and Submit New, attaching the aformentioned patch_file.
7. Someone will look it over and possibly commit it to CVS for all to enjoy.

Temporary (2005-04-17) home page by Chris Engel (ctenet/chris52389)

Hosting for this open source project is provided for free by: