Get code

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 28 in a folder named tiki28 without all the history, which is also called a shallow clone

git clone --depth=1 --branch=28.x https://gitlab.com/tikiwiki/tiki.git tiki28

More examples:

git clone --depth=1 --branch=27.x https://gitlab.com/tikiwiki/tiki.git tiki27

git clone --depth=1 --branch=24.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

This is a good approach for developers needing to have the full Tiki history since it saves network bandwidth and disk space. Git is able to borrow information from other local clones when creating a new clone. This reduces the network usage while cloning and reduces disk usage of maintaining 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=28.x --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tiki28

git clone --branch=27.x --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tiki27

git clone --branch=24.x --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tiki24

Trimming git history

Another way to reduce disk and network usage is the --depth= , where is the number of history entries desired to bring. This approach may not be ideal for Tiki development since the change history is not available. But it is a good way to keep track of the file state when installing Tiki in a server.

git clone --branch=28.x --depth=1 https://gitlab.com/tikiwiki/tiki.git tiki28

git clone --branch=28.x --depth=2 https://gitlab.com/tikiwiki/tiki.git tiki28

For the examples above, just the last commits of branch 27.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)

• Daily Build

Bit of History

• Tiki Version control history

Converting an FTP install

• Convert a site installed via FTP to now use SVN

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

Errors

If you encounter errors while trying the above, see Composer

Download | Check out | Checkout | Get Tiki | GetTiki