I have to preface this by saying I've spent the last 5 years in a budget shared hosting enviroment using a CMS (content management system
) on most of my sites. I became very accustomed to several enviromental variables that seem to be lacking in the default DA world. I'm hoping someone(s) can tell me if there is an official "best way" or most reliable way to do the following:
1. Change the fact that I have to chmod directories to 777 for my CMS to work. It seems very unsafe that I have to do this but, 755 doesn't work. Not to mention the fact that I have to chmod everything.
2. Along the same lines, correct the file ownership issues with apache/nobody and the site user.
3. Give users the ability to add their own php.ini (and remove the need to restart apache when changes have been made to php.ini)
I have found several HOW-TOs but, I'd rather know what the best way was before I started changing things again (I've already followed two tuts that didn't leave me any better off).
I'm on CentOS 4
Thanks for any advice!
) on most of my sites. I became very accustomed to several enviromental variables that seem to be lacking in the default DA world. I'm hoping someone(s) can tell me if there is an official "best way" or most reliable way to do the following:1. Change the fact that I have to chmod directories to 777 for my CMS to work. It seems very unsafe that I have to do this but, 755 doesn't work. Not to mention the fact that I have to chmod everything.
2. Along the same lines, correct the file ownership issues with apache/nobody and the site user.
3. Give users the ability to add their own php.ini (and remove the need to restart apache when changes have been made to php.ini)
I have found several HOW-TOs but, I'd rather know what the best way was before I started changing things again (I've already followed two tuts that didn't leave me any better off).
I'm on CentOS 4
Thanks for any advice!
Last edited: