On Fri, Aug 20, 2004 at 10:54:17AM +0300, Kai Hendry wrote: > On Fri, Aug 20, 2004 at 04:48:35PM +1000, Matthew Palmer wrote: > > > /web/mywebapp.example.com > > And the first package that goes over whatever I've got installed at > > /web/mywebapp.example.com, unless there's FHS approval for it, gets a HEOE. > > What does HEOE mean? I tried looking it up. Acronyms slow down readers > and I don't think we desperately need to save space. There is enough > acronyms as it is. IMO. ;) Hot Enema Of Enlightenment. One of the many tools in the good BOFH toolkit. I keep mine next to the Wire Brush of Knowledge (which is best applied to the Foreskin of Ignorance). > > > Just got served from http://mywebapp.example.com > > But I want my shiny new webapp to be at example.com/mywebapp -- no, wait, > > make that vhost12.com/preproduction/mywebapp. > > Then use for example on the file system: > /web/example.com/mywebapp > /web/vhost12.com/preproduction/mywebapp > What's the problem? The fact that there then has to be (at least) two places to install the package's files. Remember we're talking about placement of files in the filesystem to make them visible in webspace. Basically I'm railing against webservers which don't have an alias method -- if I want my files to appear somewhere else in such a system, I have to move them. That makes it nigh-on impossible to get a decent default config. I would certainly not recommend a subdomain default policy, because that requires DNS cooperation. > > > Web apps should not be dependent on apache, but just httpd. > > Riiiight. Is there any requirement for a package providing httpd to even > > *have* CGI capabilities? Once you give a complete API for managing the > > configuration of every httpd-providing package in the archive, let me know. > > Can't we assume web apps use CGI? Yes, but we can't assume that httpd provides it. > So what's the point of the virtual package httpd? To speak the HTTP protocol -- hence the name 'httpd' for HTTP Daemon. CGI is only ephemerally related to HTTP in the sense that HTTP is the usual way that CGI scripts end up being executed. - Matt
Attachment:
signature.asc
Description: Digital signature