CcHost File Access - Revision history

Fourstones: /* What ccHost Requires (IMPORTANT) */

2009-05-03T20:13:42Z

‎What ccHost Requires (IMPORTANT)

Fourstones at 20:12, 3 May 2009

2009-05-03T20:12:10Z

Fourstones: /* ccHost Permissions Policy */

2009-05-03T20:10:13Z

‎ccHost Permissions Policy

Fourstones: brought this page up to date to represent more current installs

2009-05-03T20:08:46Z

brought this page up to date to represent more current installs

Jon Phillips: despam

2007-08-13T03:42:30Z

despam

HSAENZL: /* ccHost Permissions Policy */

2007-08-06T22:16:44Z

‎ccHost Permissions Policy

Jon Phillips: /* Case 2: You and ccHost are in the same group */

2007-04-30T23:23:18Z

‎Case 2: You and ccHost are in the same group

Jon Phillips: /* Case 2: You and ccHost are in the same group */

2007-04-30T23:21:19Z

‎Case 2: You and ccHost are in the same group

Jon Phillips: /* You are not nobody */

2007-04-30T23:19:48Z

‎You are not nobody

Fourstones: /* Case 3: You and ccHost are not in the same group */

2006-10-17T00:25:19Z

‎Case 3: You and ccHost are not in the same group

@@ Line 61: / Line 61: @@
 For 3.1 installations and later: The path configuration screen ('''admin/paths''') will let you know exactly which directories require write access from script. These include 'content' and your 'local_files' directory.
-{{InfoBox|NOTE: Your installation will not work properly until local_files and all directories under it are writable to script.}}
+{{Infobox|NOTE: Your installation will not work properly until local_files and and directories under it are writable to script.}}
 === Case 1: You and ccHost are the same user===

← Older revision		Revision as of 20:12, 3 May 2009
Line 1:		Line 1:
		+	[[Category:ccHost]]
		+	[[Category:ccMixter]]
		+	[[Category:Developer]]
		+	[[Category:Software]]
		+	[[Category:Technology]]
		+	{{cchost_head}}
		+	{{lowercase}}
	== Information regarding UNIX file permission and ccHost==		== Information regarding UNIX file permission and ccHost==

← Older revision		Revision as of 20:10, 3 May 2009
Line 107:		Line 107:

	== ccHost Permissions Policy==		== ccHost Permissions Policy==
−	ccHost 3.0 will use 0777 as the default for creating files. This is so new installations can get quickly off the ground and running. If you wish to change this policy go to 'Manage Site' and then 'Global Settings.'	+	ccHost 3.0 will use 0777 as the default for creating files. This is so new installations can get quickly off the ground and running. If you wish to change this policy go to 'Manage Site' and then 'Global Settings' or browse to the '''admin/setup''' command.

@@ Line 1: / Line 1: @@
 == Information regarding UNIX file permission and ccHost==
-Setting file permissions in the most efficient and secure way can be tricky with
+Setting file permissions in the most efficient and secure way can be tricky with a content management system such as ccHost on a UNIX system.
 There are many (i.e. many, many) UNIX configurations for running Apache and PHP
@@ Line 13: / Line 12: @@
 If you 'own' the server and have super-user (root) access then these problems
 are probably moot because you have the rights to do whatever you want with the
-directories and files created by ccHost. However, depending on whether you run PHP
+directories and files created by ccHost. However, depending on whether you run PHP in CGI mode or not, these issues could very well be a big problem.
-On the other hand if you are using a company server or a
+On the other hand if you are using a company server or a web hosting service, especially on a 'shared server', then chances are you do not have such
 access rights and that's where the issues begin.
@@ Line 48: / Line 44: @@
 installation:
 <pre>
-drwxrwxr-x   5 victor wgroup  4096 Jul 15 01:41 cctools
+drwxrwxr-x   5 victor wgroup  4096 Jul 15 01:41 icons
-drwxrwxr-x   5 nobody wgroup  4096 Jul 17 02:09 contests
+drwxrwxr-x   5 nobody wgroup  4096 Jul 17 02:09 content
 </pre>
-The first directory 'cctools' created by me during FTP install. The second directory 'contests' was created by ccHost when I said 'Create Contest' and is therefore owned by another user.
+The first directory 'icons' created by me during FTP install. The second directory 'content' was created by ccHost when I installed ccHost and is therefore owned by another user.
 === What ccHost Requires (IMPORTANT)===
-For 3.1 installations and later: The path configuration screen (Global Settings/Paths) will let you know exactly which directories require write access from script. These include 'people', 'constests', your log directory and my_files/temp. These last two depend on where you specified their locations during installation. NOTE: ''Your installation will not work properly until my_files/temp is writable to script.''
+For 3.1 installations and later: The path configuration screen ('''admin/paths''') will let you know exactly which directories require write access from script. These include 'content' and your 'local_files' directory.
-For installations previous to 3.1: In order to install properly, ccHost (or more precisely the PHP account ccHost is running as) must have write permissions in the root directory of the ccHost installation, in a directory under it called '''cclib/phptal/phptal_cache''' and where ever you told the installation to put log files to. Specifically and in UNIX parlance this means full permission: Read, Write and Execute. The '''people''' directory is normally created by ccHost the first time something is uploaded and the '''contests''' directory is normally created the first time something is uploaded into a contest. If these directories already exist then ccHost will only need permissions in them, '''cclib/phptal/phptal_cache''' and your logfile directory -- not the root. Instructions for how to set these up (and whether you even have to) are covered below.
+{{InfoBox|NOTE: Your installation will not work properly until local_files and all directories under it are writable to script.}}
 === Case 1: You and ccHost are the same user===
 In the best case scenario, some web hosters make all of this go away by
-simply having PHP applications run under the same account as your login account.
+simply having PHP applications run under the same account as your login account. There is no 'nobody' account to contend with and ccHost is, in fact, running as you so permission to create directories in the main directory or write files to the phptal_cache directory is given. So if you ask your system administrator 'Do PHP apps run under my user's account?' and if the answer is 'Yes' then you can skip down the ccHost policy section because none of
 this applies to your ccHost installation.

@@ Line 115: / Line 115: @@
 If your personal UNIX login account and your PHP account are not in the same group and you haven't a secure web interface, then your system administrator or web hosting service has left you with no choice to make the necessary directories available for writing to global users (a.k.a. other). You should keep the ccHost default access permission at 777.
 == ccHost Permissions Policy==
 ccHost 3.0 will use 0777 as the default for creating files. This is so new installations can get quickly off the ground and running. If you wish to change this policy go to 'Manage Site' and then 'Global Settings.'

@@ Line 84: / Line 84: @@
 getting to the global space (the rest of the world).
 If this is the case then you should consider restricting the directories that need writing access to only owner and group.
 === Case 3: You and ccHost are not in the same group===

@@ Line 77: / Line 77: @@
 above that this is case:
 <pre>
-drwxrwxr-x   5 victor wgroup</b>  4096 ....
+drwxrwxr-x   5 victor wgroup  4096 ....
-drwxrwxr-x   5 nobody wgroup</b>  4096 ....
+drwxrwxr-x   5 nobody wgroup  4096 ....
 </pre>
 This is important because while you may not be the same user as

@@ Line 87: / Line 87: @@
 === Case 3: You and ccHost are not in the same group===
-If your login account and your PHP account are not even in the
+If your personal UNIX login account and your PHP account are not even in the
 same group then you may still have an out:
@@ Line 101: / Line 101: @@
 you can make the needed change.
-If your login account and your PHP account are not in the
+If your personal UNIX login account and your PHP account are not in the same group and you haven't a secure web interface, then your system administrator or web hosting service has left you with no choice to make the necessary directories available for writing to global users (a.k.a. other). You should keep the ccHost default access permission at 777.
 == ccHost Permissions Policy==
 ccHost 3.0 will use 0777 as the default for creating files. This is so new installations can get quickly off the ground and running. If you wish to change this policy go to 'Manage Site' and then 'Global Settings.'