Topic: XOOPS: installation int Primary ibay

[micronator]

I tried to install XOOPS in Primary ibay n an 6.0.1. I would like to know the permissions and group:owner inside Primary. It installed well but the index.php didn't change size or date after installation so now I think something is missing write permission. I have a blank page on my url.
Any tips appreciated.

Thank you all

[micronator]

After many trials:

Permissions inside Primary ibay: (drwxr-s---) for all directories.
owner:group inside Primary: (chown -R root:www *)

Permissions inside html: (chmod -R 777 uploads/  cache/  templates_c/) and (chmod 666 mainfile.php)

[CharlieBrady]

After many trials:

Permissions inside Primary ibay: (drwxr-s---) for all directories.
owner:group inside Primary: (chown -R root:www *)

Permissions inside html: (chmod -R 777 uploads/  cache/  templates_c/) and (chmod 666 mainfile.php)

Don't ever set permissions on a directory to 777. It's *always* wrong, and means that you haven't worked out what you really want.

[boss_hog]

Hey micronator,
for what it's worth, I have a Xoops site. It is running in an ibay, but if it helps, here goes:
1) Setup a Xoops "database" in MySQL;
2) Give a "xoops DB user" enough MySQL permissions for Xoops DB;
3) Install Xoops;
(I have the 3 dirs cache, templates_c, & upload, set at 770 the rest of the dirs are set 750 and all files are 644) This appears to work for me.
When the install is done set the mainfile.php to 444, this is critical.
Also, i use a small php script with all the "secret info", db_name, db_user and db_password, for the mainfile.php. Then move the secret_info file outside of the web root, and point the mainfile.php to the secret_info file. Prevents php from freaking out and leaving all the info readable from the clients browser.
Good luck
Joe

[micronator]

Thank you Charlie for your remark.
I changed them to 770, it should be OK now. But I still doubted the (root:www) ownership. Is that the best way???

Thank you boss_hog.
I did replace the $db_*. I wanted to place the secure file on top of Primary but it did not worked. The reason to put it on top of Primary been if I ever use FTP, the FTP-client might see the file (correct me If I am wrong)

I place it inside Primary and it was OK. Permission for the file is now 440 and ownership is (root:www).

I tried to use relative path to the file in the include in mainfile.php i.e. (../secure_file.php) as if I ever move the site it will be easier. It worked to see the home page with no problem. However when I logged into the site as webmaster I recieved an error that it cannot login to the database. So I put back the full path.

Am I missing something here.

Any help appreciated.

[boss_hog]

Hey micronator,
here is the link to the security guide that I used for my set-up: http://xoops-tips.com/news-article.storyid-1.htm

Whatever dir you put the secure_file in needs to be accessible by the www.
my secure_file is in /home/e-smith/files/ibays/<mysitebay>/secure-dir/secure_file.php
It is is 640 & admin.www

MySQL has a user with the following privileges:
 SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER.
These are NOT global, they are only for the Xoops DB.
I hope this helps, Xoops has been very friendly for my needs, and has an excellent community (like Contribs!).
Joe