
Knowledge Base - FAQ
To list the permissions for a directory telnet into your site and use the command:
ls -l <directory>
You will see a list of the files in the directory. The first column of the list gives you information about the permissions on each file, such as:
-rwxrwxr-x
The ten-character string above can be interpreted as follows:
- 1st character: Indicates the nature of the thing being listed (- means an ordinary file, d means directory, l means symbolic link).
- Characters 2-4: Specify the owner's permissions. For example, rwx means that the owner of the file has read, write and execute access, while rw- would mean that the owner has read and write access but not execute access.
- Characters 5-7: Specify the group's permissions. In the above example, the group has read, write and execute access.
- Characters 8-10: Specify the permissions for people other than the owner and group (such as world wide web surfers). In the example above, such users have read and execute access to the file but not write access.
To change permissions on a file or directory use the chmod command. The chmod command is of the form:
chmod xyz <filename>
Where x indicates the type of permission to be given to the owner, y indicates the type of permission to be given to the group, and z indicates the type of permission to be given to other users. x, y and z are digits which are calculated as described below.
Each type of permission has a numeric code:
- Read permission = 4
- Write permission = 2
- Execute permission = 1
You add up the relevant codes to figure out what number to use in your chmod command. For example:
- Read plus execute access = 5
- Read plus write plus execute access = 7
- No access = 0
So to give the owner rwx access, the group r-x access and other people no access to the file test.cgi, you would use the command:
chmod 750 test.cgi
For more information please refer to the Linux manual page:
man chmod
Since Kattare has not yet made the jump to Apache 2, we recommend granting access to your subversion repository via the subversion server, svnserve. If you have not yet setup your repository, we'll leave that to a Google search. "subversion setup" or "subversion howto" should result in many, many hits.
Specific to the Kattare servers though, we can assist with the svnserve setup:
- change to your repository's configuration directory:
cd <my_homedirectory>/<svn_root>/conf/ - vi/pico passwd, it should look something like:
<users> harry = harryspassword sally = sallyspassword - change permissions on the passwd file:
chmod 600 passwd - vi/pico svnserve.conf, it should look something like:
<general> anon-access = none auth-access = write password-db = passwd - Pick a port to run it on. If you have a private tomcat or apache instance,
it's probably safe to snag the port it's running on and increment it by one
or two. If not, just about anything in the 20000 - 21000 range should be good.
Note: You will need to let support@kattare.com know the port you assigned so the webserver firewall can be opened up on that port.
- run svnserve:
svnserve -d --listen-port=<port> -r <my_homedirectory>/<svn_root> - Email support@kattare.com and ask them to setup the boot scripts to
start your subversion instance at boot time. Please include the line you
used above to start it up.
Keeping in mind that you'll have to specify the username and password as well, your subversion URL for checkout would then be something like:
svn://www.mydomain.com:<port>/repository/path
Additional Resources:
The O'Reilly Subversion Book
Basic Subversion setup and usage
For additional information, see the subversion website and the subversion book.
You can checkout a repository over the local filesystem or via SSH.
svn co file:///var/svn/repos/kattare/trunk kattare
svn co svn+ssh://me@hostname/var/svn/repos/kattare/trunk kattare
Within a repository, you can:
Update the repository to the latest version
svn update
See a summary of any local changes
svn status
Put files (or directories) under revision control
svn add
Commit any changes you have made
svn commit
If, for some reason, you want to throw away changes you have made:
svn revert
For additional command-line help
svn help
svn help checkin
svn help status
svn help ...
The site uses Linux/Apache web servers which runs a variation of Unix. All Unix machines are case sensitive. This means that if you upload your files with upper case letters in them, then your HTML's references must also match the case. The easiest way would be to keep everything in lower case. Spaces and special control characters are generally not a good idea.
[Submit a Question]
Comments or feedback? Email: support@kattare.com
Legal: Terms of Service | Privacy Policy | DMCA Procedure | Trademarks



