[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

http daemon suggestion/proposal



Hi developers,

I would like to suggest some about a file structure related to http 
daemons. At this moment apache and cern-httpd define their own directories
where to store their cgi-bin / webspace stuff etc. 

For packages depending on this structure (not so many right now but some
nice cgi-bin scripts provided via packages might be very usefull: debian
man/info/??? 2 html documentation daemon) it is required that some fixed
file structure is provided. 

Putting cgi-bin etc. in /usr/lib/cern-httpd like cern-httpd does isn't good
IMO because this might be a readonly if /usr is mounted readonly. Putting
cgi-bin etc. in /var/web/ isn't what I think /var should be used for, I
think that the best place (but who am I to say) is a user named www, or 
perhaps a user named apache or a user named cern-httpd. 

I would like to suggest the following:

The packages should provide the following subdirectories:

/home/www/cgi-bin
/home/www/icons
/home/www/http or /home/www/data

The package specific files which come with the package should come in
other directories for example:

/home/apache/cgi-bin
/home/apache/icons
/home/apache/http or /home/apache/data

in which /home/apache is a symbolic link to /home/www

/home/cern-httpd/cgi-bin
/home/cern-httpd/icons
/home/cern-httpd/http or /home/cern-httpd/data

in which /home/cern-httpd is a symbolic link to /home/www

Script providing packages (not depending on a specific package) will 
provide their stuff from the /home/www (and sub) directories.

Erick







Hi developers,

I would like to suggest some about a file structure related to http 
daemons. At this moment apache and cern-httpd define their own directories
where to store their cgi-bin / webspace stuff etc. 

For packages depending on this structure (not so many right now but some
nice cgi-bin scripts provided via packages might be very usefull: debian
man/info/??? 2 html documentation daemon) it is required that some fixed
file structure is provided. 

Putting cgi-bin etc. in /usr/lib/cern-httpd like cern-httpd does isn't good
IMO because this might be a readonly if /usr is mounted readonly. Putting
cgi-bin etc. in /var/web/ isn't what I think /var should be used for, I
think that the best place (but who am I to say) is a user named www, or 
perhaps a user named apache or a user named cern-httpd. 

I would like to suggest the following:

/home/www/cgi-bin
/home/www/icons
/home/www/http






--
Erick Branderhorst@heel.fgg.eur.nl +31-10-4635142
Department of General Surgery (Intensive Care) University Hospital Rotterdam NL


Reply to: