Features / Usability

Posted by Torsten Fabricius 23 Nov 2014 13:05 GMT-0000 posts: 1563

Ouch, CKE did eat my long description args.

Now I am kind of busy, so I just rewrite in very brief, based on the assumption that you work on a Linux shell and used svn to checkout the code.

$: sh setup.sh
message: ~ which option you want to choose?
$: c
this runs the composer - a script that gets and installes the missing vendor files.

After that stay in the setup or run it again and choose one of the file permission fixing options - details when you use the permission check (see docs or ask here again) - default would be the option f, which is not the safest, but necessary on most shared hosting. should work mostly.

This is because the webapplication (Tiki) needs read/write permission to certain subdirectories as for example the cache directoiries.

When you later store files in the directory (not in tikiroot/files for security reason), you have to create and chmod the ../files/gallery ../files/whatelseyouneed etc. aswell - in worst case to 777.

So after the composer has downloaded and installed the vendor files:

code.

$: sh setup.sh
if it was closed)
$: f
and follow the procedure of installation - any more question you can answer by simply accepting empty - all options you can later configure in Tiki - just click through.
Important, that you at some time receive a message like ~ "fixing dirs permissions" ... "done" or so (I do not recall the exact wording, as I just use to click though and it is an obvious dialogue)
$: x
(exit)

Then run the installer in the browser again.

Regards,
Torsten