Re: Linux uninstall / reinstall
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 46895
interpreted = N
texte = Alan White wrote: > Hi John > > Does that mean that I could move my webcatalogengine and WebCatalog folder > to another domain and then alter the following entry (just and example as > there are lots more entries to change also) to specify a different domain? > > LoadModule webcatalog2_module > /home/domain/domain1/web/cgi-bin/WebCatalogEngine/mod_webcatalog2.so > AddModule mod_webcatalog.cpp > Those aren't the only lines, nor are they the most important ones to enabling webcat for a given domain. I'll give you my experts-only advice, so you can see the flexibility of Apache configurations. Don't do this unless you know what you are doing; your server will be hosed if you mess up your Apache configuration files. `service httpd configtest` is your friend!I move the WebCatalogEngine directory completely outside of the domain hierarchy; it can be anywhere on the drive and the LoadModule line adjusted accordingly. The mod_webcatalog2.so is always available sitewide, since it loads directly into the Apache application, so there is really no point in associating it with a given domain's files. Worst case schenario (like if you are using the script install), install the WebCatalogEngine directory under the default Apache location (which is rarely the actual public server anyways). I'll talk about the admin files later.To enable a given subdomain to handle Webcatalog files, add the proper line to the applicable
section: # all your other VirtualHost parameters AddHandler webcatalog2-handler .tpl So, even though you have mod_webcatalog file loaded, it is only mapped to the .tpl files for _that_ identity. If you want to map all .html or .shtml files to WebCatalog, adjust the AddHandler line accordingly.For the Admin files, it is generally recommended that they not be available on any publically accessible domain, even though they are password protected. For example, you could limit their use to localhost only (or some other limitation, say by IP address block). In any case, you can do something like this: # any other things, like ServerName Alias /WebCatAdmin/ /path/to/WebCatalogEngine/Admin And you could now log into the WebCatalog admin only from the local machine as: http://localhost/WebCatAdmin/index.tplinstead of the usual (with the default script install): http://localhost/cgi-bin/WebCatalogEngine/Admin/index.tplThe important thing to realize is that the cgi-bin directory is itself not special; you can put these files where you want them and change the mapping accordingly. And in fact, the Admin files do not have to be in the cgi-bin directory at all, since they are actually processed by the handler, not directly as if they were CGI scripts.HTH and remember, I said not to do this without understanding what you are doing!John-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Alan White wrote: > Hi John > > Does that mean that I could move my webcatalogengine and WebCatalog folder > to another domain and then alter the following entry (just and example as > there are lots more entries to change also) to specify a different domain? > > LoadModule webcatalog2_module > /home/domain/domain1/web/cgi-bin/WebCatalogEngine/mod_webcatalog2.so > AddModule mod_webcatalog.cpp > Those aren't the only lines, nor are they the most important ones to enabling webcat for a given domain. I'll give you my experts-only advice, so you can see the flexibility of Apache configurations. Don't do this unless you know what you are doing; your server will be hosed if you mess up your Apache configuration files. `service httpd configtest` is your friend!I move the WebCatalogEngine directory completely outside of the domain hierarchy; it can be anywhere on the drive and the LoadModule line adjusted accordingly. The mod_webcatalog2.so is always available sitewide, since it loads directly into the Apache application, so there is really no point in associating it with a given domain's files. Worst case schenario (like if you are using the script install), install the WebCatalogEngine directory under the default Apache location (which is rarely the actual public server anyways). I'll talk about the admin files later.To enable a given subdomain to handle Webcatalog files, add the proper line to the applicable section: # all your other VirtualHost parameters AddHandler webcatalog2-handler .tpl So, even though you have mod_webcatalog file loaded, it is only mapped to the .tpl files for _that_ identity. If you want to map all .html or .shtml files to WebCatalog, adjust the AddHandler line accordingly.For the Admin files, it is generally recommended that they not be available on any publically accessible domain, even though they are password protected. For example, you could limit their use to localhost only (or some other limitation, say by IP address block). In any case, you can do something like this: # any other things, like ServerName Alias /WebCatAdmin/ /path/to/WebCatalogEngine/Admin And you could now log into the WebCatalog admin only from the local machine as: http://localhost/WebCatAdmin/index.tplinstead of the usual (with the default script install): http://localhost/cgi-bin/WebCatalogEngine/Admin/index.tplThe important thing to realize is that the cgi-bin directory is itself not special; you can put these files where you want them and change the mapping accordingly. And in fact, the Admin files do not have to be in the cgi-bin directory at all, since they are actually processed by the handler, not directly as if they were CGI scripts.HTH and remember, I said not to do this without understanding what you are doing!John-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
John Peacock
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[WebDNA] Crashing again (2008)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
[shownext max=?] armed (1997)
How flexible is Shipping? (1997)
[OT] Test - THE ANSWER (2003)
Strange intermittent WebDNA problems (2008)
Retirement (2000)
Searching for all records (1998)
creator code (1997)
creative use of webcatalog (1998)
FORMS: Returning a specific page (1997)
Re:FYI: Error message (1996)
emailer error 103 part ii (1997)
HELP!? (2002)
Problems with [Applescript] (1997)
Anyone using [sendmail] for HTML encoded mail? (2000)
Problems passing [SKU] with $Replace in 2.0 (1997)
how to check for no value while using [URL] to prevent cr (1999)
[authenticate] (1999)
Problem with [isFile] [isFolder] (wc 3.0.4, iis 4) (1999)