README

   1 ReadMe for Dev-Editor 3.x.x
   2 ===========================
   3
   4 Description
   5 -----------
   6
   7 Dev-Editor is a simple CGI based editor written in Perl and licensed under the
   8 terms of the Artistic License, which allows remote changes to files and
   9 directory structures on a web server. That's useful if you aren't able to access
  10 the files on your homepage directly, for example if you are on holiday.
  11
  12 Installation
  13 ------------
  14
  15 First, you have to copy the files into a directory on your web server where you
  16 are able to execute scripts (in most cases, this is "cgi-bin"). I suggest to
  17 create a sub directory for Dev-Editor.
  18 Then, you have to change the first line of devedit.pl: Just replace
  19 /usr/bin/perl by the path to your Perl interpreter.
  20 If you are on a UNIX based system, you have to set devedit.pl as executable
  21 (chmod 755 in most cases).
  22 You will also need to configure Dev-Editor. See the next section for details.
  23
  24 Note, that the directory where you installed Dev-Editor should be protected by
  25 HTTP Authentication. If you don't do that, everybody will be able to access
  26 Dev-Editor and use it for evil purposes.
  27
  28 Configuration
  29 -------------
  30
  31 Open the file devedit.conf. This file contains keys and values separated by a
  32 "=" sign. Lines beginning with a "#" sign are ignored.
  33 Here is a list of the configuration options currently available:
  34
  35 Option                   Description
  36 ------                   -----------
  37
  38 fileroot                 The root directory Dev-Editor is allowed to access.
  39                          Nobody is allowed to access the files and directories
  40                          above this directory. Dev-Editor needs write access to
  41                          this directory and to the sub directories.
  42
  43 httproot                 This is the equivalent HTTP URL to the root directory.
  44                          It's just used for visual output, so it doesn't need to
  45                          be correct.
  46
  47 max_file_size            Here you may define a maximum size for files (Bytes).
  48                          If the user wants to view or edit a file larger than
  49                          this defined size, Dev-Editor denies file access (but
  50                          the file can still be copied, renamed or removed).
  51                          If this is empty or 0, any file can be viewed or
  52                          edited.
  53
  54 timeformat               The format of the time shown in directory listings.
  55                          These are the most important placeholders:
  56
  57                          %a - short day name (Sun to Sat)
  58                          %A - long day name (Sunday to Saturday)
  59                          %b - short month name (Jan to Dec)
  60                          %B - long month name (January to December)
  61                          %d - day of the month (01 to 31)
  62                          %H - hour in 24 hour clock (00 to 23)
  63                          %I - hour in 12 hour clock (01 to 12)
  64                          %m - month of the year (01 to 12)
  65                          %M - minutes (00 to 59)
  66                          %p - AM or PM
  67                          %S - seconds (00 to 59)
  68                          %y - two digit year (03)
  69                          %Y - four digit year (2003)
  70                          %% - percent sign
  71
  72                          There are a lot of other placeholders. A complete list
  73                          is found at:
  74                          http://www.opengroup.org/onlinepubs/7908799/xsh/strftime.html
  75                          Note that some systems don't support some of the
  76                          placeholders (for example %T on Windows).
  77
  78                          This format is also used to format the system time in
  79                          the About dialogue.
  80
  81 use_gmt                  Set this option to 1 if you want to use Greenwich Mean
  82                          Time (GMT/UTC) in directory listing and in the About
  83                          dialogue instead of the local time.
  84
  85 hide_dot_files           Set this option to 1 if you want to hide files or
  86                          directories beginning with a dot (e.g. ".htaccess") in
  87                          directory listing.
  88                          The files are just hidden in the directory listing,
  89                          you can still access them typing the name into the
  90                          "Go to directory/file" box.
  91
  92 forbidden                Specify a list of filenames the user is not allowed to
  93                          access. The filenames have to be relative to the
  94                          virtual root directory (they must also begin with a
  95                          slash) and have to be separated by space characters. If
  96                          a filename contains space characters, you have to put
  97                          it into double quotation marks ("/filename").
  98
  99 userconf_file            Specifies the path to a file which contains
 100                          user-dependent configuration options (see next section
 101                          for details).
 102
 103 error_file               The path to the file which defines the error messages.
 104                          The file has the same format as this one.
 105
 106 template_file            The path to the file which defines the paths to the
 107                          template files. The file has the same format as this
 108                          one.
 109
 110 User-dependent configuration
 111 ----------------------------
 112
 113 If you have placed Dev-Editor inside a directory protected using HTTP
 114 authentication, you may override some default configuration values for a defined
 115 list of users. You may override the values for the following configuration
 116 options:
 117
 118 - fileroot
 119 - httproot
 120 - hide_dot_files
 121 - forbidden
 122
 123 For overriding configuration values you need a special configuration file. The
 124 path to this file is defined using the "userconf_file" configuration option in
 125 the main configuration file (add the option if necessary). This file consists of
 126 key-value-pairs and sections, marked by a string encapsulated in square brackets
 127 (perhaps you know this format, it is nearly the same as the Windows INI files).
 128 Each section in this file describes an individual configuration, whereby the
 129 name of the section is the username for whom this configuration should be used.
 130 Here is an example:
 131
 132 [homer]
 133 fileroot = /var/www/homer/htdocs
 134 httproot = /
 135
 136 This sets the physical file root directory to "/var/www/homer/htdocs" and the
 137 virtual HTTP root to "/" - but only for the user whose HTTP authentication
 138 username is "homer".
 139
 140 Using the "aliases" option, you may also define some other usernames for whom
 141 this configuration should be used:
 142
 143 [homer]
 144 fileroot = /var/www/homer/htdocs
 145 httproot = /
 146 aliases = marge bart
 147
 148 Using this, the users whose usernames are "marge" and "bart" use the same
 149 configuration as "homer". Place any number of username seperated by whitespaces
 150 here.
 151 Note: If one of the users mentioned as an alias and an individual configuration
 152 section for this user exists too, the one mentioned as an alias is ignored.
 153
 154 If there are some files marked as inaccessible using the "forbidden"
 155 configuration option in the main configuration file, but some users should have
 156 access to these files, you may clear the default value of "forbidden":
 157
 158 [homer]
 159 fileroot = /var/www/homer/htdocs
 160 httproot = /
 161 forbidden =
 162
 163 Using this, "homer" has access to all files in "/var/www/homer/htdocs".
 164
 165 Notes
 166 -----
 167
 168 Symbolic links are treated as files, no matter where they point to. The user is
 169 just allowed to see the path where the link points to, he is allowed to delete
 170 the link, to rename it and to overwrite it by renaming an other file. Nothing
 171 else is allowed.
 172 Accessing a symbolic link pointing to a directory also caused a very strange
 173 effect: It was possible to access this directory, but you could not access the
 174 objects in it.
 175 I had to do it in this way because of the very stupid behaviour of abs_path()
 176 from the Cwd module: This function is just able to detect the absolute path of
 177 directories.
 178 Hard links are not affected by this.
 179
 180 ------------------------------------------------
 181
 182 (C) 1999-2000 Roland Bluethgen, Frank Schoenmann
 183 (C) 2003-2009 Patrick Canterino
 184
 185 E-Mail: patrick@patshaping.de
 186 WWW:    http://devedit.sourceforge.net/