Permission Check | |
|
Tiki Permission Check (TPC): An additional source of information if Tiki install fails.
| |
1. Introduction | |
What is Tiki Permission Check? | |
|
If Tiki installer and tiki-check.php fail, Tiki Permission Check can be used to figure out some details about filesystem permissions needed by the webserver to make those ones work. Permissions for Tiki Permission Check can be fixed manually (only a few files via FTP or SSH or other shell access) or by an included script. Then Tiki Permission Check can be used to figure out which filesystem permissions are needed to run Tiki on the webserver. This permission setting needn't be unique, so you may choose more or less restrictions depending on the security level you want and/or need. Tiki Permission Check can be used to figure out file permission problems independent from Tiki itself. In those cases file permissions have to be adjusted manually or by whatsoever method appropriate to that alien project. A convenient way to use the information for installing Tiki is by setup.sh modification (upcoming soon). | |
Predefined Permission Models | |
|
Due to several webserver settings und use cases TPC offers several predefined models to check whether an installation will work with them or not. Once the correct model(s) is (are) known, they can be used to run the setup script
| |
Where is it available? | |
|
Tiki Permission Check is available in trunk and as standalone download. It will be available in Tiki10 (Effective 2012-10-22). Standalone version will (at least: should) work with any version of Tiki. At the bottom of this page there is an alpha version attached. Bleeding edge code is at:
| |
2. Enable and Disable Tiki Permission Check | |
|
An important issue is to enable and disable Tiki Permission Check. Once you've got the information you need it is strongly recommended to disable it, because some subdirectories are set world writable for testing purposes and ownership (user/group) of files is exposed to the public (but you may use htaccess protection if possible, this depends on webserver's settings). | |
2.1. Usage of Tiki Permission Check with Shell | |
|
Use a shell like sh (or bash, dash) to run the script | |
2.1.1. Set Script Permissions | |
|
In Tiki's document root:
| |
2.1.2. Set htaccess Permissions | |
|
If you need htaccess protection, copy In Tiki's document root:
This is done each time Tiki Permission Check is enabled or disabled by shell script. So in most cases you needn't do this manually. You cannot use htaccess password protection when TPC is enabled, because TPC uses http requests to figure out the possible models. You need htaccess password protection only if you are beyond paranoia. In this case, you may delete the complete folder | |
2.1.3. Enable via Shell | |
|
In Tiki's document root:
| |
2.1.4. Disable via Shell | |
|
In Tiki's document root:
| |
2.2. Usage of Tiki Permission Check with FTP | |
|
Setting permissions without shell access is kind of annoying. You may set local file permissions and upload them or you set file permissions via FTP (in both cases: enable/disable). In addition, you need to copy | |
2.2.1. General Settings via FTP chmod | |
|
Set htaccess Permissions
| |
2.2.2. Enable via FTP chmod | |
|
create | |
2.2.3. Disable via FTP chmod | |
|
copy | |
3. Permission Overview: Examples | |
|
http://example.org/permissioncheck/
| |
3.1. Use Tiki Permission Check | |
|
Visit your own Tiki installation's path /permissioncheck/ and you will see the TPC main page. You can replace the domain example.com with your own domain in the example above. When the page tells you it's disabled, you need to enable it. You should see all permission models, user, group and file permissions for those models and a hint whether this model works or not. Note the model names which seem to work, you'll need them. | |
4. Use Information From Tiki Permission Check | |
4.1. Shell Access | |
|
| |
5. Commands of setup.sh | |
5.1. General Commands | |
| |
5.1.1. Composer | |
| |
5.2. Classic Commands | |
| |
5.3. Predefined Models | |
| |
5.4. Fine Grained Permission Bits | |
5.4.1. Complete Tiki Tree | |
| |
5.4.2. Special Directories (Webserver Write Access) | |
| |
6. Customized Use Cases | |
|
Warning: not recommended for beginners Arbitrary use cases can be added, this is quickly and easily done by three steps:
| |
7. Related Content | |