Get code

This page includes information for obtaining the latest Tiki code.


There are several methods to download the latest Tiki code.

1.1. Option 1: Using Git

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 21 in a folder named tiki21 without all the history:

Clone and set 21.x into tiki21 folder
git clone --depth=1 --branch=21.x https://gitlab.com/tikiwiki/tiki.git tiki21

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.

Clone into tikiwiki folder
git clone https://gitlab.com/tikiwiki/tiki.git tikiwiki


Then, other clones can be created by borrowing the information from the clone above.

Clone and set master into tikimaster folder
git clone --branch=master --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tikimaster

Clone and set 21.x into tiki21 folder
git clone --branch=21.x --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tiki21

Clone and set 18.x into tiki18 folder
git clone --branch=18.x --reference=./tikiwiki --shared https://gitlab.com/tikiwiki/tiki.git tiki18

Clone and set 15.x into tiki15 folder
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 --depth= , where 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.

Clone into tiki18 folder with 1 commit in history
git clone --branch=18.x --depth=1 https://gitlab.com/tikiwiki/tiki.git tiki18

Clone into tiki18 folder with 2 commits in history
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.



1.2. Option 2: Using SVN (read only)

Please note: SVN updates (for all versions of Tiki) will stop in January 2023 when Tiki18 reaches end of life, so you should get your updates from Git
Use these steps to download the latest version from SVN:

  1. Checkout the code.
    • Method 1
      Checking out Tiki branches into new folders (e.g. trunk, tiki21 etc.)
      svn checkout https://svn.code.sf.net/p/tikiwiki/code/trunk trunk
      svn checkout https://svn.code.sf.net/p/tikiwiki/code/branches/21.x tiki21
      svn checkout https://svn.code.sf.net/p/tikiwiki/code/branches/18.x tiki18
      svn checkout https://svn.code.sf.net/p/tikiwiki/code/branches/15.x tiki15
    • Method 2
      Checking out to the current folder
      svn checkout https://svn.code.sf.net/p/tikiwiki/code/trunk .

      The dot "." means the current folder from where you run the command.
  2. Update from SVN.
    See Update

Commit your code

Bit of History

SVN

Before promoting git usage, Tki used mainly Subversion for many years.

CVS

Before migrating to Subversion, Tiki used CVS: http://tikiwiki.cvs.sourceforge.net/viewvc/tikiwiki/

Using Mods (deprecated)

If you want to checkout the deprecated Mods system, then you have to separately use:

Checking out Mods with SVN
svn checkout https://svn.code.sf.net/p/tikiwiki/code/mods/trunk

Things in Tiki are changing rapidly. You may need to pick up your mod from https://tikiwiki.svn.sourceforge.net/ and navigate down to mods > wiki-plugins. If you install the mod by hand like this, you need to put the .php file in ./lib/wiki-plugins/ (see also the sh setup.sh fix step herein).

Pre-release packages (zip files)

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

Errors

If you encounter errors while trying the above, see Composer

alias

Download | Check out | Checkout | Get Tiki | GetTiki