1 ReadMe for Dev-Editor 3.2
2 =========================
7 Dev-Editor is a simple web based file manager written in Perl and licensed
8 under the terms of the Artistic License 2.0, allowing you to access a file
9 system on a server using a web browser. That's useful if you aren't able to
10 access the files directly or using FTP or SSH.
15 - Browsing through directory structures
18 - Removing files and directories
19 - Moving/renaming files and directories
20 - Copying files and directories
21 - Creating new files and directories
22 - Executing a HTTP download of a file
23 - Uploading files to the server via HTTP
24 - Changing permissions (chmod) and group (chgrp) of files and directories (on
26 - Unpacking some types of archive files (Perl module Archive::Extract is
27 required - core module since Perl 5.10, I guess)
32 First, you have to copy the files into a directory on your web server where you
33 are able to execute CGI scripts (in most cases, this is "cgi-bin"). I suggest
34 to create a sub directory for Dev-Editor.
35 Then you have to change the first line of devedit.pl: Just replace
36 /usr/bin/perl by the path to your Perl interpreter.
37 If you are on a Unix based system, you have to make devedit.pl executable
38 (chmod 755 in most cases).
39 You also have to edit Dev-Editor's configuration file (see next section for
42 If you install Dev-Editor on a public web server, you should protect its
43 directory using HTTP authentication or everybody in the world will be able to
44 access the configured directory structure!
49 Open devedit.conf. This file contains keys and values separated by a "=" sign.
50 Lines beginning with a "#" sign are comments and will be ignored.
51 Here is a list of the configuration options currently available:
56 fileroot The root directory Dev-Editor is allowed to access.
57 Nobody is allowed to access the files and directories
58 above this directory. Dev-Editor needs write access to
59 this directory and its sub directories.
61 httproot This is the equivalent HTTP URL to the root directory.
62 It's just used for visual output, so it doesn't need to
65 startdir Here you may define the default directory Dev-Editor
68 max_file_size Here you may define a maximum size for files (Bytes).
69 If the user wants to view or edit a file larger than
70 this defined size, Dev-Editor denies file access (but
71 the file can still be copied, renamed or removed).
72 If this is empty or 0, any file can be viewed or
75 timeformat The format of the time shown in directory listings.
76 These are the most important placeholders:
78 %a - short day name (Sun to Sat)
79 %A - long day name (Sunday to Saturday)
80 %b - short month name (Jan to Dec)
81 %B - long month name (January to December)
82 %d - day of the month (01 to 31)
83 %H - hour in 24 hour clock (00 to 23)
84 %I - hour in 12 hour clock (01 to 12)
85 %m - month of the year (01 to 12)
86 %M - minutes (00 to 59)
88 %S - seconds (00 to 59)
89 %y - two digit year (03)
90 %Y - four digit year (2003)
93 There are a lot of other placeholders. A complete list
95 http://pubs.opengroup.org/onlinepubs/007908799/xsh/strftime.html
96 Note that some systems don't support some of the
97 placeholders (for example %T on Windows).
99 This format is also used to format the system time in
102 use_gmt Set this option to 1 if you want to use Greenwich Mean
103 Time (GMT/UTC) in directory listing and in the About
104 dialogue instead of the local time.
106 hide_dot_files Set this option to 1 if you want to hide files or
107 directories beginning with a dot (e.g. ".htaccess") in
109 The files are just hidden in the directory listing,
110 you can still access them using the "Go to
113 forbidden Specify a list of filenames the user is not allowed to
114 access. The filenames have to be relative to the
115 virtual root directory (they must also begin with a
116 slash) and have to be separated by space characters. If
117 a filename contains space characters, you have to put
118 it into double quotation marks ("/file name").
120 disable_commands Specify a list of commands the user is not allowed to
121 execute. The commands have to be separated by space
123 If you add "@write" to the list, all writing commands
124 (for example edit, copy, rename etc.) will be
127 userconf_file Specifies the path to a file which contains
128 user-dependent configuration options (see next section
131 error_file The path to the file which defines the error messages.
132 The file has the same format as the main configuration
135 template_file The path to the file which defines the paths to the
136 template files. The file has the same format as the
137 main configuration file.
139 User-dependent configuration
140 ----------------------------
142 If you have placed Dev-Editor inside a directory protected using HTTP
143 authentication, you may override some default configuration values for a defined
144 list of users. You may override the values for the following configuration
154 For overriding configuration values you need a special configuration file. The
155 path to this file is defined using the "userconf_file" configuration option in
156 the main configuration file (add the option if necessary). This file consists of
157 key-value-pairs and sections, marked by a string encapsulated in square brackets
158 (perhaps you know this format, it is nearly the same as Windows' INI files).
159 Each section in this file describes an individual configuration, whereby the
160 name of the section is the username for whom this configuration should be used.
164 fileroot = /var/www/homer/htdocs
167 This sets the physical file root directory to "/var/www/homer/htdocs" and the
168 virtual HTTP root to "/" - but only for the user whose HTTP authentication
171 Using the "aliases" option, you may also define some other usernames for whom
172 this configuration should be used:
175 fileroot = /var/www/homer/htdocs
179 Using this, the users whose usernames are "marge" and "bart" use the same
180 configuration as "homer". You can place an arbitrary number of usernames
181 seperated by whitespaces here.
182 Note: If one of the users is defined as an alias and there is an individual
183 configuration section for this user too, the one defined as an alias is
186 If there are some files marked as inaccessible using the "forbidden"
187 configuration option in the main configuration file, but some users should have
188 access to these files, you may clear the default value of "forbidden":
191 fileroot = /var/www/homer/htdocs
195 Using this, "homer" has access to all files in "/var/www/homer/htdocs".
200 Symbolic links are treated as files, no matter where they point to. The user is
201 just allowed to see the path where the link points to, he is allowed to delete
202 the link, to rename it and to overwrite it by renaming an other file. Nothing
204 Accessing a symbolic link pointing to a directory also caused a very strange
205 effect: It was possible to access this directory, but you could not access the
207 I had to do it in this way because of the very stupid behaviour of abs_path()
208 from the Cwd module: This function is just able to detect the absolute path of
210 Hard links are not affected by this.
212 ------------------------------------------------
214 (C) 1999-2000 Roland Bluethgen, Frank Schoenmann
215 (C) 2003-2011 Patrick Canterino
217 E-Mail: patrick@patshaping.de
218 WWW: http://devedit.sourceforge.net/