This page includes information for obtaining the latest Tiki source code.
- The current released Tiki version can be downloaded from SourceForge.net.
- Pre-release code can be downloaded from the Git repository.
- You can view the code here: https://gitlab.com/tikiwiki/tiki/
There are several methods to download the latest Tiki code.
1.1. Option 1: Using Git
New to Git?
See here: Git
or here: Pro Git Book (CC ND SA 3.0) by Scott Chacon and Ben Straub
Using the clone command (taken from Git clone Tiki)
After a decade of contributions, Tiki history sizes 3GB when decompressed locally. That is too big when several Tiki instances is needed. As of now, two approaches were tested to deal with this problem:
- Share git objects with other clones
git clone --shared --reference=
- Trim history size
git clone --depth=1
For example to create a clone of branch 24 in a folder named tiki24 without all the history, which is also called a shallow clone
git clone --depth=1 --branch=24.x https://gitlab.com/tikiwiki/tiki.git tiki24
git clone --depth=1 --branch=21.x https://gitlab.com/tikiwiki/tiki.git tiki21
git clone --depth=1 --branch=21.x https://gitlab.com/tikiwiki/tiki.git .
Use master (previously called trunk):
git clone --depth=1 --branch=master https://gitlab.com/tikiwiki/tiki.git .
Sharing git history
That is a good approach to developers needing to have the full Tiki history, but without waste network bandwidth or disk space. Git is capable to borrow information from other local clone when creating a new clone. This reduces the network usage while cloning and reduces disk usage to maintain several Tiki instances.
Information sharing is set by using the option
--reference= and the option
--shared , where
is another clone made before.
The first step is to create a standard Tiki clone, like the example below.
git clone https://gitlab.com/tikiwiki/tiki.git tikiwiki
Then, other clones can be created by borrowing the information from the clone above.
git clone --branch=master --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tikimaster
git clone --branch=21.x --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tiki21
git clone --branch=18.x --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tiki18
git clone --branch=15.x --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tiki15
Trimming git history
Another available to reduce disk and network usage is the
is the number of history entries desired to bring. This approach may not be so good to Tiki development, because the change history is not available. But it is good to keep track of file state when installing Tiki in a server.
git clone --branch=18.x --depth=1 https://gitlab.com/tikiwiki/tiki.git tiki18
git clone --branch=18.x --depth=2 https://gitlab.com/tikiwiki/tiki.git tiki18
On the examples above, just the last
commits of branch 18.x will be available on local repository. All other information about branches and tags will not exist on local repository.
It is possible to have a cloned repository with the last
commits of each branch available. This is done by passing
--no-single-branch to clone command.
For more information about the clone command see Git clone Tiki.
Commit your code
- See How to get commit access for information on contributing code and joining the Tiki developer community.
- You can also see full instructions on how to commit.
Pre-release packages (zip files)
Bit of History
Converting an FTP install
Tiki Manager (formerly known as TRIM)
For managing multiple, independent Tiki installations. Please see TRIM
Amazon Machine Image (AMI) for EC2
Amazon Elastic Compute Cloud - Amazon Web Services. Please see: EC2
If you encounter errors while trying the above, see Composer