Requirements[edit | edit source]
First, make sure you meet all the requirements in the previous chapter.
Unzip the .tar.gz file[edit | edit source]
You can unzip the tarball in a temporary directory. In this example we'll use /tmp and assume your downloaded Zoph version 0.9 into /home/user/Downloads
$ cd /tmp $ cp /home/user/Downloads/zoph-0.9.tar.gz . $ tar -xvzf zoph-0.9.tar.gz $ cd zoph-0.9
Creating the database[edit | edit source]
Create a database and import the tables[edit | edit source]
$ mysql -u root -p -e "CREATE DATABASE zoph CHARACTER SET utf8 COLLATE utf8_general_ci" $ mysql -u root -p zoph < sql/zoph.sql
Create users for zoph[edit | edit source]
I created two users: zoph_rw is used by the application and zoph_admin is used when I work directly in mysql so I don't have to use root.
$ mysql -u root -p mysql> grant select, insert, update, delete on zoph.* to zoph_rw@localhost identified by 'PASSWORD';
mysql> grant all on zoph.* to zoph_admin identified by 'PASSWORD';
Install the templates[edit | edit source]
Pick a location to put Zoph[edit | edit source]
Create a zoph/ directory off the doc root of your web server, or create a Virtual Host with a new doc root.
$ mkdir /var/www/html/zoph
Copy the templates[edit | edit source]
$ cp -r php/* /var/www/html/zoph/
Set accessrights[edit | edit source]
For better security, you probably want to set accessrights on your Zoph files. (You may want to do this after testing whether Zoph works, in that case you know what caused it when it seizes working after this change)
First, you need to figure out which user Apache is running under. Usually this is apache for both user and group. To determine this, check httpd.conf or use
ps -ef | grep httpd
You should probably make all files owned by the user apache and the group apache. You can do than with
chown -R apache:apache /var/www/html/zoph
You can either make them only readable by this user/group (more security): 440, readable by all users: 444, or readable and writable by all users: 666. The last case means that you don't need root access to edit config.inc.php or to make changes to the other php files (such as upgrades to a new version). Keep in mind that giving write access to the .php files effectively gives control over Zoph. If you have other users on your system, you should choose the first option. Also, your mysql password is in /etc/zoph.ini, so if you've users on your system that are not allowed to know it, you should protect it against reading as well.The directories should have execute rights: 550 for max security or 777 for access for all users.
To do this, first go to the directory directly above your Zoph directory, in this example /var/www/html
cd /var/www/html chmod [dir] zoph cd zoph find -type f | xargs chmod [file] find -type d | xargs chmod [dir]
replace [dir] with the accesspattern you've chosen for directories above and replace [file] with the one for files.
Access rights for your photos[edit | edit source]
In many cases you can simply leave the access rights on you photo directories on default. However, if you use both the CLI and the webinterface to access your photos, you may want to change to a more advanced way of managing accessrights, using the setgid feature in Linux and most other POSIX Operating Systems.
- Create a new Unix group (in example "photo")
- Add all users that use the CLI and/or are allowed to modify the photos on disk to this group (in this example, the user is called 'jeroen')
useradd -g photo jeroen
- Additionally, the apache user is added to this group, on my system, this user is called 'apache', but 'www-data' is also often used.
useradd -g photo apache
- Change the ownership of the photo directory to your user and the group photo
chown jeroen:photo /data/images
- Set the permissions on this directory as you wish, for example 775 (full rights for user and group, read rights for other) or 770 (full rights for user and group, no access for others).
chmod 775 /data/images
Now set 'setgid' on the dir, this causes new files and directories to be created with the group 'photo'.
chmod g+s /data/images
Configure the PHP templates[edit | edit source]
Please see the chapter on configuration for details.
zoph.ini[edit | edit source]
You will need to create a zoph.ini file, usually in /etc/zoph.ini is where you define database settings. A simple example:
[zoph] db_host = "localhost" db_name = "zoph" db_user = "zoph_rw" db_pass = "pass" db_prefix = "zoph_" php_location = /var/www/html/zoph
For more details, see zoph.ini.
Test it[edit | edit source]
Try hitting http://localhost/zoph/logon.php. You should be presented with the logon screen. Log in using "admin" for user and "admin" for password.
If you get a 404 error...
- make sure the zoph/ folder and templates can be seen by the web server.
If you see a bunch of code...
- make sure Apache is configured to handle PHP
- The Apache configuration needs to contain this:
LoadModule php5_module /usr/lib/apache2/modules/libphp5.so AddType application/x-httpd-php .php
If you see a MySQL access denied error...
- make sure the database user you specified in zoph.ini actually has access to the database. If your database is not on localhost, you will need to grant permissions to zoph_rw@hostname for that host.