Here we have some step-by-step instructions for installing Tiki on Ubuntu Server with Apache2, MySQL5, and PHP5/PHP7.
I would recommend installing only SSH Server as part of the initial install.
sudo apt-get update sudo apt-get upgrade
You can install Linux, Apache, Mysql and PHP (plus a few other helper utils such as subversion, etc) with:
sudo apt install mysql-server mysql-client apache2 php php-tidy php-pear memcached php-gd php-xmlrpc phpmyadmin php-mbstring libapache2-mod-php php-mysql php-apcu php-curl php-intl php-sqlite3 php-zip postfix subversion php-memcache php-gettext php-pspell php-zip poppler-utils php-memcached bsdmainutils catdoc elinks man-db odt2txt php-pear pstotext php-common php-intl php7.1-opcache php7.1-mcrypt php7.1-xml php7.1-zip
Then you can enable the modules
sudo phpenmod mcrypt sudo phpenmod mbstring
Extra packages for Media Alchemyst:
sudo add-apt-repository ppa:libreoffice/libreoffice-6-0 sudo apt install libreoffice ffmpeg unoconv ghostscript php-imagick imagemagick
Enable the Apache rewrite rules:
sudo a2enmod rewrite sudo service apache2 restart
And you can enable the self-signed ssl certificates to allow connections with https:
sudo a2enmod ssl sudo a2ensite default-ssl sudo service apache2 restart
And add this section between the VirtualHost tags the to this file /etc/apache2/sites-enabled/000-default.conf (or equivalent for your configuration; in this case, the doc. root where tiki is installed is /var/www/html/, which is where ubuntu 16.04 comes pre-configured for the base doc root):
sudo nano /etc/apache2/sites-enabled/000-default.conf
Section to add (just after the Document root line):
<Directory /var/www/html/> Options Indexes FollowSymLinks MultiViews AllowOverride All ## The following lines to allow connections have changed syntax ## between apache 2.2 and apache 2.4 ## See: http://httpd.apache.org/docs/2.4/upgrading.html > Run-Time Configuration Changes > Access control #Order allow,deny #Allow from all Require all granted </Directory>
Do the same type of edit into the equivalent config file for https:
sudo nano /etc/apache2/sites-enabled/default-ssl.conf
After the change, they should look like:
<VirtualHost *:80> # The ServerName directive sets the request scheme, hostname and port that # the server uses to identify itself. This is used when creating # redirection URLs. In the context of virtual hosts, the ServerName # specifies what hostname must appear in the request's Host: header to # match this virtual host. For the default virtual host (this file) this # value is not decisive as it is used as a last resort host regardless. # However, you must set it for any further virtual host explicitly. #ServerName www.example.com ServerAdmin webmaster@localhost DocumentRoot /var/www/html <Directory /var/www/html/> Options Indexes FollowSymLinks MultiViews AllowOverride All #Order allow,deny #Allow from all Require all granted </Directory> # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf </VirtualHost> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
<IfModule mod_ssl.c> <VirtualHost _default_:443> ServerAdmin webmaster@localhost DocumentRoot /var/www/html <Directory /var/www/html/> Options Indexes FollowSymLinks MultiViews AllowOverride All ## The following lines to allow connections have changed syntax ## between apache 2.2 and apache 2.4 ## See: http://httpd.apache.org/docs/2.4/upgrading.html > Run-Time Configuration Changes > Access control #Order allow,deny #Allow from all Require all granted </Directory> # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on # A self-signed (snakeoil) certificate can be created by installing # the ssl-cert package. See # /usr/share/doc/apache2/README.Debian.gz for more info. # If both key and certificate are stored in the same file, only the # SSLCertificateFile directive is needed. SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key # Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile # when the CA certificates are directly appended to the server # certificate for convinience. #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt # Certificate Authority (CA): # Set the CA certificate verification path where to find CA # certificates for client authentication or alternatively one # huge file containing all of them (file must be PEM encoded) # Note: Inside SSLCACertificatePath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCACertificatePath /etc/ssl/certs/ #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt # Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded) # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath /etc/apache2/ssl.crl/ #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl # Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10 # SSL Engine Options: # Set various options for the SSL engine. # o FakeBasicAuth: # Translate the client X.509 into a Basic Authorisation. This means that # the standard Auth/DBMAuth methods can be used for access control. The # user name is the `one line' version of the client's X.509 certificate. # Note that no password is obtained from the user. Every entry in the user # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CERT and # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the # server (always existing) and the client (only existing when client # authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory /usr/lib/cgi-bin> SSLOptions +StdEnvVars </Directory> # SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is send or allowed to received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and # "force-response-1.0" for this. # BrowserMatch "MSIE [2-6]" \ # nokeepalive ssl-unclean-shutdown \ # downgrade-1.0 force-response-1.0 </VirtualHost> </IfModule> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
Use your PhpMyAdmin install:
http://example.com/phpmyadmin/
If you can't login with your mysql root password, you can use the debian-sys-maint
crdentials that you will find here:
/etc/mysql/debian.cnf
And that's all. Then you will need to tell tiki that we have created:
Alternatively, if we don't use control panel we can create a database and user for tiki.
# mysql -p # mysql> CREATE DATABASE youraccountname_tiki; # mysql> GRANT ALL PRIVILEGES ON youraccountname_tiki.* TO 'youraccountname_yourusername'@'localhost' IDENTIFIED BY 'yourpassword'; # mysql> \q
If it's a brand new server, you are encouraged to secure your mysql installation with the provided script, and do the recommended setup steps indicated here:
https://vitux.com/how-to-install-and-configure-mysql-in-ubuntu-18-04-lts/
Ubuntu 18.04 comes with dash as the default shell interpreter. And Tiki shell scripts expect bash instead of dash. Therefore, one easy solution is to setup bash for your user with sudo perms in the server to use bash by default. You can do so with the command (for user username):
usermod --shell /bin/bash yourusername
More information:
(url's taken from http://dev.tiki.org/Get+code )
Create a new folder
Create folder /var/www/html/18.x and change directory to that new folder:
sudo mkdir /var/www/html/18.x cd /var/www/html/18.x
We fetch tiki18 through subversion to this folder:
svn checkout https://svn.code.sf.net/p/tikiwiki/code/branches/18.x .
Then we run the Tiki setup script through console:
bash setup.sh
You can have a look at what the script does here:
http://doc.tiki.org/setup.sh
This script manages all Tiki dependencies through a program called "Composer" (it downloads and updated them when needed)
Then you can proceed with the standard Tiki installation thorugh the web browser (replace example.com with your domain name):
http://example.com/18.x/
and this will take us to tiki-install.php:
http://example.com/18.x/tiki-install.php
Tip for Spanish speakers: see the video from a course on Tiki:
At the screen to Setup the database connection, we provide the database name, db user and password that we previosuly created and we follow instructions on screen.
At the new installation, the first user is admin, with password admin. We replace the password and continue to log in for the first time.
You have your tiki installed, ready for you to continue using the Wizards
It seems that you need to create a folder for h5p to work as expected (in case you have H5P enabled in your site); otherwise, when you attempt to upload a file to a file gallery, you get an error message saying that Tiki cannot write to the corresponding folder from h5p.
You can run these commands, from the tiki root folder in the server:
sudo mkdir storage/public/h5p sudo chmod 775 storage/public/h5p
Install a repository to get updated version of packages that will just work:
sudo add-apt-repository ppa:certbot/certbot sudo apt update sudo apt install python-certbot-apache
Before we can start to create the SSL cert, set the domain name in the vhost configuration file. Open the default vhost file with an editor:
nano /etc/apache2/sites-available/000-default.conf
and add the line:
ServerName example.com
Replace example.com with your fully qualified domain name.
Then create the SSL Certificate with this command:
sudo certbot --apache
The command will start a wizard that asks you several questions.
If you want further customization, use other options as described or linked from here:
https://certbot.eff.org/lets-encrypt/ubuntubionic-apache
If you want, you can add some packages through console
sudo su cd /var/www/html/ composer require --update-no-dev --prefer-dist mpdf/mpdf composer require --update-no-dev --prefer-dist fullcalendar/fullcalendar-scheduler #composer require --update-no-dev --prefer-dist xorti/mxgraph-editor # deprecated for Tiki 21.x composer require --update-no-dev --prefer-dist tikiwiki/diagram # updated for Tiki 21.x instead of mxgraph-editor composer require --update-no-dev --prefer-dist onelogin/php-saml composer require --update-no-dev --prefer-dist thiagoalessio/tesseract_ocr composer require --update-no-dev --prefer-dist npm-asset/pdfjs-dist-viewer-min #composer require --update-no-dev --prefer-dist media-alchemyst/media-alchemyst #composer require --update-no-dev --prefer-dist php-ffmpeg/php-ffmpeg composer require --update-no-dev --prefer-dist npm-asset/dexie composer require --update-no-dev --prefer-dist npm-asset/lozad composer require --update-no-dev --prefer-dist google/apiclient service apache2 restart exit
You can install Linux, Apache, Mysql and PHP (plus a few other helper utils such as subversion, etc) with:
sudo apt install mysql-server mysql-client apache2 php php-tidy php-pear memcached php-gd php-xmlrpc php-xml-parser phpmyadmin php-mbstring php-mcrypt libapache2-mod-php php-mysql php-opcache php-apcu php-curl php-intl php-sqlite3 postfix subversion php-memcache php-gettext php-pspell php-zip poppler-utils php-memcached bsdmainutils catdoc elinks man-db odt2txt php-pear pstotext php-common
Then you can enable the modules
sudo phpenmod mcrypt sudo phpenmod mbstring
Extra packages for Media Alchemyst:
sudo add-apt-repository ppa:libreoffice/libreoffice-5-1 sudo apt install libreoffice sudo apt-get install ffmpeg sudo apt-get install unoconv sudo apt-get install ghostscript sudo apt-get install php-imagick sudo apt-get install imagemagick
Enable the Apache rewrite rules:
sudo a2enmod rewrite sudo service apache2 restart
And you can enable the self-signed ssl certificates to allow connections with https:
sudo a2enmod ssl sudo a2ensite default-ssl sudo service apache2 restart
And add this section between the VirtualHost tags the to this file /etc/apache2/sites-enabled/000-default.conf (or equivalent for your configuration; in this case, the doc. root where tiki is installed is /var/www/html/, which is where ubuntu 16.04 comes pre-configured for the base doc root):
sudo nano /etc/apache2/sites-enabled/000-default.conf
Section to add (just after the Document root line):
<Directory /var/www/html/> Options Indexes FollowSymLinks MultiViews AllowOverride All ## The following lines to allow connections have changed syntax ## between apache 2.2 and apache 2.4 ## See: http://httpd.apache.org/docs/2.4/upgrading.html > Run-Time Configuration Changes > Access control #Order allow,deny #Allow from all Require all granted </Directory>
Do the same type of edit into the equivalent config file for https:
sudo nano /etc/apache2/sites-enabled/default-ssl.conf
After the change, they should look like:
<VirtualHost *:80> # The ServerName directive sets the request scheme, hostname and port that # the server uses to identify itself. This is used when creating # redirection URLs. In the context of virtual hosts, the ServerName # specifies what hostname must appear in the request's Host: header to # match this virtual host. For the default virtual host (this file) this # value is not decisive as it is used as a last resort host regardless. # However, you must set it for any further virtual host explicitly. #ServerName www.example.com ServerAdmin webmaster@localhost DocumentRoot /var/www/html <Directory /var/www/html/> Options Indexes FollowSymLinks MultiViews AllowOverride All #Order allow,deny #Allow from all Require all granted </Directory> # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf </VirtualHost> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
<IfModule mod_ssl.c> <VirtualHost _default_:443> ServerAdmin webmaster@localhost DocumentRoot /var/www/html <Directory /var/www/html/> Options Indexes FollowSymLinks MultiViews AllowOverride All ## The following lines to allow connections have changed syntax ## between apache 2.2 and apache 2.4 ## See: http://httpd.apache.org/docs/2.4/upgrading.html > Run-Time Configuration Changes > Access control #Order allow,deny #Allow from all Require all granted </Directory> # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on # A self-signed (snakeoil) certificate can be created by installing # the ssl-cert package. See # /usr/share/doc/apache2/README.Debian.gz for more info. # If both key and certificate are stored in the same file, only the # SSLCertificateFile directive is needed. SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key # Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile # when the CA certificates are directly appended to the server # certificate for convinience. #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt # Certificate Authority (CA): # Set the CA certificate verification path where to find CA # certificates for client authentication or alternatively one # huge file containing all of them (file must be PEM encoded) # Note: Inside SSLCACertificatePath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCACertificatePath /etc/ssl/certs/ #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt # Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded) # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath /etc/apache2/ssl.crl/ #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl # Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10 # SSL Engine Options: # Set various options for the SSL engine. # o FakeBasicAuth: # Translate the client X.509 into a Basic Authorisation. This means that # the standard Auth/DBMAuth methods can be used for access control. The # user name is the `one line' version of the client's X.509 certificate. # Note that no password is obtained from the user. Every entry in the user # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CERT and # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the # server (always existing) and the client (only existing when client # authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory /usr/lib/cgi-bin> SSLOptions +StdEnvVars </Directory> # SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is send or allowed to received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and # "force-response-1.0" for this. # BrowserMatch "MSIE [2-6]" \ # nokeepalive ssl-unclean-shutdown \ # downgrade-1.0 force-response-1.0 </VirtualHost> </IfModule> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
Use your PhpMyAdmin install:
http://example.com/phpmyadmin/
If you can't login with your mysql root password, you can use the debian-sys-maint
crdentials that you will find here:
/etc/mysql/debian.cnf
And that's all. Then you will need to tell tiki that we have created:
Alternatively, if we don't use control panel we can create a database and user for tiki.
# mysql -p # mysql> CREATE DATABASE youraccountname_tiki; # mysql> GRANT ALL PRIVILEGES ON youraccountname_tiki.* TO 'youraccountname_yourusername'@'localhost' IDENTIFIED BY 'yourpassword'; # mysql> \q
(url's taken from http://dev.tiki.org/Get+code )
Create a new folder
Create folder /var/www/html/18.x and change directory to that new folder:
sudo mkdir /var/www/html/18.x cd /var/www/html/18.x
We fetch tiki18 through subversion to this folder:
svn checkout https://svn.code.sf.net/p/tikiwiki/code/branches/18.x .
Then we run the Tiki setup script through console:
sh setup.sh
You can have a look at what the script does here:
http://doc.tiki.org/setup.sh
This script manages all Tiki dependencies through a program called "Composer" (it downloads and updated them when needed)
Then you can proceed with the standard Tiki installation thorugh the web browser (replace example.com with your domain name):
http://example.com/18.x/
and this will take us to tiki-install.php:
http://example.com/18.x/tiki-install.php
Tip for Spanish speakers: see the video from a course on Tiki:
At the screen to Setup the database connection, we provide the database name, db user and password that we previosuly created and we follow instructions on screen.
At the new installation, the first user is admin, with password admin. We replace the password and continue to log in for the first time.
You have your tiki installed, ready for you to continue using the Wizards
Install a repository to get updated version of packages that will just work:
sudo add-apt-repository ppa:certbot/certbot sudo apt update sudo apt install python-certbot-apache
Before we can start to create the SSL cert, set the domain name in the vhost configuration file. Open the default vhost file with an editor:
nano /etc/apache2/sites-available/000-default.conf
and add the line:
ServerName example.com
Replace example.com with your fully qualified domain name.
Then create the SSL Certificate with this command:
sudo certbot --apache
The command will start a wizard that asks you several questions.
If you want further customization, use other options as described or linked from here:
https://certbot.eff.org/lets-encrypt/ubuntuxenial-apache
You can choose to install it through tasksel (tested with Ubuntu 14.04 LTS) plus a few other handy packages, just in case they do not come along with the lamp-server itself:
sudo apt-get install tasksel sudo tasksel install lamp-server sudo apt-get install mysql-server mysql-client apache2 php5 php5-tidy php-pear memcached php5-xcache php5-gd php5-xmlrpc php-xml-parser phpmyadmin sendmail
sudo apt-get install libapache2-mod-php php-mysql
Then you can enable the module
sudo php5enmod mcrypt
Enable the Apache rewrite rules:
sudo a2enmod rewrite sudo service apache2 restart
And add this section between the VirtualHost tags the to this file /etc/apache2/sites-enabled/000-default.conf (or equivalent for your configuration; in this case, the doc. root where tiki is installed is /var/www/html/, which is where ubuntu 14.04 comes pre-configured for the base doc root):
sudo nano /etc/apache2/sites-enabled/000-default.conf
Section to add (just after the Document root line):
<Directory /var/www/html/> Options Indexes FollowSymLinks MultiViews AllowOverride All ## The following lines to allow connections have changed syntax ## between apache 2.2 and apache 2.4 ## See: http://httpd.apache.org/docs/2.4/upgrading.html > Run-Time Configuration Changes > Access control #Order allow,deny #Allow from all Require all granted </Directory>
After the change, it should look like:
<VirtualHost *:80> # The ServerName directive sets the request scheme, hostname and port that # the server uses to identify itself. This is used when creating # redirection URLs. In the context of virtual hosts, the ServerName # specifies what hostname must appear in the request's Host: header to # match this virtual host. For the default virtual host (this file) this # value is not decisive as it is used as a last resort host regardless. # However, you must set it for any further virtual host explicitly. #ServerName www.example.com ServerAdmin webmaster@localhost DocumentRoot /var/www/html <Directory /var/www/html/> Options Indexes FollowSymLinks MultiViews AllowOverride All #Order allow,deny #Allow from all Require all granted </Directory> # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf </VirtualHost> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
You may need to do this, even if in previous ubuntu versions it didn't seem to be needed:
sudo cp /etc/phpmyadmin/apache.conf /etc/apache2/conf-available/phpmyadmin.conf sudo ln -s /etc/apache2/conf-available/phpmyadmin.conf /etc/apache2/conf-enabled/phpmyadmin.conf service apache2 restart
Then you can reach your mysql ddbb to manage them through PhpMyAdmin at (replace example.com with your domain name):
http://example.com/phpmyadmin/
Use your PhpMyAdmin install:
And that's all. Then you will need to tell tiki that we have created:
(url's taken from http://dev.tiki.org/Get+code )
Create a new folder
Create folder /var/www/html/12.x and change directory to that new folder:
sudo mkdir /var/www/html/12.x cd /var/www/html/12.x
We fetch tiki12 through subversion to this folder:
svn checkout https://svn.code.sf.net/p/tikiwiki/code/branches/12.x .
Then we run the Tiki setup script through console:
sh setup.sh
You can have a look at what the script does here:
http://doc.tiki.org/setup.sh
This script manages all Tiki dependencies through a program called "Composer" (it downloads and updated them when needed)
Then you can proceed with the standard Tiki installation thorugh the web browser (replace example.com with your domain name):
http://example.com/12.x/
and this will take us to tiki-install.php:
http://example.com/12.x/tiki-install.php
Tip for Spanish speakers: see the video from a course on Tiki:
At the screen to Setup the database connection, we provide the database name, db user and password that we previosuly created and we follow instructions on screen.
At the new installation, the first user is admin, with password admin. We replace the password and continue to log in for the first time.
You have your tiki installed, ready for you to continue using the Wizards
You can choose to install it through tasksel (untested in Ubuntu 12.04 LTS):
sudo apt-get install tasksel sudo tasksel install lamp-server
Or alternatively to a tasksel-based installation of lamp, you can install the required packages by hand as usual (and their dependencies) automagically, which has been tested on Ubuntu 12.04 and works fine:
sudo apt-get install mysql-server mysql-client apache2 php5 php5-tidy php-pear memcached php5-xcache php5-gd php5-xmlrpc php-xml-parser phpmyadmin sendmail
sudo apt-get install imagemagick php5-imagick php5-gd graphviz
These are hosted on SourceForge, if you want to grab the most current stable version directly:
Tiki 9.x (LTS) or the latest stable at each moment in time.
Alternatively, you can also Get code from SVN.
sudo apt-get install subversion
Get the latest tarball from http://info.tiki.org/Download
As an example, it's described here with Tiki 9.2.:
sudo mv tikiwiki-9.2.tar.gz /var/www/html/
cd /var/www/html sudo tar -xvzf tikiwiki-9.2.tar.gz
cd /var/www/html/tikiwiki-9.2 sudo sh setup.sh
User [www-data]: Group [www-data]: Multi []: Checking dirs : backups ... ok. db ... ok. dump ... ok. img/wiki ... ok. img/wiki_up ... ok. img/trackers ... ok. modules/cache ... ok. temp ... ok. temp/cache ... ok. templates_c ... ok. templates ... ok. styles ... ok. maps ... ok. whelp ... ok. mods ... ok. files ... ok. tiki_tests/tests ... ok. lib/Galaxia/processes ... ok. Fix global perms ... chowned ... done. Fix special dirs ... done.
We'll create the database and create a user with rights to the Tiki database. In the following example, the database name is tiki, the username is tiki, and the password for tiki is tikipassword. You'll need this information later when we configure Tiki, so make sure you write this stuff down. Replace names as you see fit.
mysql -u root -p
You'll be prompted for your mysql root password you entered earlier, then are met with the mysql prompt. Type the following commands exactly as shown.
mysql>CREATE DATABASE tikiwiki default character set 'UTF8'; mysql>GRANT ALL ON tikiwiki.* TO 'tiki'@'localhost' IDENTIFIED BY 'tikipassword'; mysql>QUIT
sudo nano -w /etc/apache2/apache2.conf
Add the following line to the end of the <Directory /var/www> section (just above the ending </Directory>)
RedirectMatch ^/$ /tikiwiki-9.2/
It's not clear that this step might interfere with latest behavior or rewrite rules found in .htaccess file distributed (as _htaccess) by Tiki. If you experience any issues, don't do this step, and just use your tiki from your subfolder (add the subfolder to the path in the browser). Or adapt the base path in your /etc/apache2/sites-available/default (or equivalent) file, etc.
If you keep accessing your tiki from a subfolder, adapt the corresponding part of the .htaccess file in the tiki root file tree:
# You may need to uncomment and fix the RewriteBase value below to suit your installation. e.g. if your Tiki is not installed directly in the web root. RewriteBase /tikiwiki-9.2
sudo a2enmod rewrite sudo service apache2 restart
And add this section between the VirtualHost tags the to this file /etc/apache2/sites-enabled/000-default.conf (or equivalent for your configuration; in this case, the doc. root where tiki is installed is /var/www/ ):
sudo nano /etc/apache2/sites-enabled/000-default.conf
Section to add (just after the Documen root line):
<Directory /var/www/> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </Directory>
Note it may not be necessary as the default is now 128M, but just in case:
sudo nano -w /etc/php5/apache2/php.ini
change
memory_limit = 16M ; Maximum amount of memory a script may consume (16MB)
to memory_limit = 128M
To get it working in the end I had to:
sudo apt-get install sendmail
Check its working
ps -aux | grep sendmail
Edit your php.ini to uncomment sendmail:
located insudo nano -w /etc/php5/apache2/php.ini
;sendmail_path =
to
sendmail_path = /usr/sbin/sendmail -t -i
[mail function] ; For Win32 only. ;SMTP = localhost ;smtp_port = 25 ; For Win32 only. ;sendmail_from = me@example.com ; For Unix only. You may supply arguments as well (default: "sendmail -t -i"). sendmail_path = /usr/sbin/sendmail -t -i ; Force the addition of the specified parameters to be passed as extra parameters ; to the sendmail binary. These parameters will always replace the value of ; the 5th parameter to mail(), even in safe mode. ;mail.force_extra_parameters =
sudo apt-get install postfix
No extra configuration is of either Postfix or PHP is required, beyond choosing which sort of mail system you're setting up, which is explained during Postfix installation. It just works, at least in my virgin 6.x Tiki install on a virgin Ubuntu Lucid. Tiki can send mail.
sudo /etc/init.d/apache2 restart
Point a browser to http://hostname/tikiwiki-9.2/tiki-install.php
Replace "hostname" above with actual hostname or IP address
Database type is MySQL Improved
Database name is tikiwiki
Database User is tiki
Password is tikipassword
You can also see the standard documentation about the installation
http://doc.tiki.org/Installation
and see how to apply a configuration profile to adapt your tiki to your own use ase with just a few clicks:
Starting in Tiki4, the interface has been improved and streamlined. No more profiles at install time, but a nicer profile manager anytime
Profiles can also be applied at any time after Tiki is installed by following these steps:
Note: sendmail still needs some work. I suspect the email is being send to the server but is going no where. I suspect that if you setting up Tiki with professional hosting you won't need to worry about sendmail?
Alias names for this page:
UbuntuInstall | Install Ubuntu | InstallUbuntu