Table of contents
Anonymous SF Login
Getting the code
What do I need to do first?
Keeping up to date
To keep up-to-date with the latest bug-fixes, you can update the code with the following.
alias tikicvslogin="cvs -d:pserver:email@example.com:/cvsroot/tikiwiki login"
If i upgrade my development environment, first I make a copy of tiki/db/tiki_1.5to1.6.sql to tiki/db/tiki_1.5to1.6.sql.old
tikicvslogin (if necessary)
after that I make a
diff tiki_1.5to1.6.sql tiki_1.5to1.6.sql.old
to see what's changed in the DB. In most cases you can make a script to upgrade your DB with:
diff tiki_1.5to1.6.sql.old tiki_1.5to1.6.sql | egrep "^>" | cut -b 3-
The brave pipe this into mysql
Another suggestion from Dennis H
I have included below, the script I use on Linux to update my sites from
1) After the initial run, create a tar file from the tiki directory called
2) The updates are always cumulative since the last generation of the
3) If the files in the db directory change (get picked up in the update
Here's the script:
cvs -d:pserver:firstname.lastname@example.org:/cvsroot/tikiwiki login ||
followed by Flo
Nice, but why not use the cvs update? I have subscribed to the cvs-list, and as soon as there are some new mails i do a cvs update -d. For easier use, i have 2 (or more) directories of tiki checked out (all accessing the same DB). With this i can always compare to the last cvs update. If the DB-structure didn't change, i can compare how tiki works, just by changing a small part of the browser line! For comparing with older versions i use cvs diff. cvs is easier
With SF Login
Getting the code
Once you're ready for the big time you'll need to learn the ssh cvs so you can commit to tiki... that can be a lot of fun!
I've tried to capture some of this in my blog: http://tikiwiki.org/tiki-view_blog.php?blogId=14
edit user id for database in myql to give perms to the database
So that I didn't have to start with a virgin database I just copied the existing database in mysql\data to a new name...
ok, here's my command-line version:
first save all existing data in simple sql format:
mysqldump -uMysqlUsername -pMysqlPassword TikiDBName > ~/TikiSave.sql
check that your ))TikiSave.sql(( exists in your home directory:
This is YOUR data, so love it. Name it with the version of your tiki, a date, whatever.
edit tikidb.php to reflect a valid set of perms for the database
Check the db directory for a .sql file that would update the database schema from the one I copied it from to the version of the cvs pull.
update the database using that file
Are there any command line statements that make your life easier?
Tiki CVS with Eclipse
Now you have to check out Tiki into the DOCROOT (or maybe subdir /tiki ) of your webserver.
More to come soon - UserPageohertel
Tiki CVS with Tortoise CVS
(I'd love to see a simple tutorial to handle commits to Tiki CVS with some GUI program under GNU/Linux. I didn't succeed with LinCVS, nor gCVS, (and neither from WinCVS for M$ Windows). But I did with TortoiseCVS, and here I drop some lines and screenshots, in case they may be of any use for other newbies like me committing changes to Tiki: language files, small bug fixes, etc. - xavi )
To get phplayersmenu
go to your tiki directory