Re: Linux uninstall / reinstall

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 46910
interpreted = N
texte = Hi JohnThanks for your detailed help that you have offered, I am becoming a lot more familiar with my httpd.conf file since when I first started posting on this list so am not too scared of having a go at modifying it. I ended up using the uninstall script that you suggested and then re-installed WC on a sub domain with managed to irradiate the problem that I was having. Some of the suggestions you have made are interesting though so I may go on to implement some of them once I have completed testing on our new site.I have some deadlines that I need to do my best to stick to so once I have overcome my time deadlines I may look into a more secure installation of WC. Oh yeah... just out of interest, how do I go about using `service httpd configtest`? If it is my friend I would like to become familiar with it....Thanks once again.Alan White ------------------------------ http://www.streethreds.comon 15/1/03 4:58 pm, John Peacock at jpeacock@rowman.com wrote:> 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.tpl > > instead of the usual (with the default script install): > > http://localhost/cgi-bin/WebCatalogEngine/Admin/index.tpl > > The 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 ------------------------------------------------------------- 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:

    
  1. Re: Linux uninstall / reinstall (Alan White 2003)
  2. Re: Linux uninstall / reinstall (John Peacock 2003)
  3. Re: Linux uninstall / reinstall (Alan White 2003)
  4. Re: Linux uninstall / reinstall (John Peacock 2003)
  5. Linux uninstall / reinstall (Alan White 2003)
Hi JohnThanks for your detailed help that you have offered, I am becoming a lot more familiar with my httpd.conf file since when I first started posting on this list so am not too scared of having a go at modifying it. I ended up using the uninstall script that you suggested and then re-installed WC on a sub domain with managed to irradiate the problem that I was having. Some of the suggestions you have made are interesting though so I may go on to implement some of them once I have completed testing on our new site.I have some deadlines that I need to do my best to stick to so once I have overcome my time deadlines I may look into a more secure installation of WC. Oh yeah... just out of interest, how do I go about using `service httpd configtest`? If it is my friend I would like to become familiar with it....Thanks once again.Alan White ------------------------------ http://www.streethreds.comon 15/1/03 4:58 pm, John Peacock at jpeacock@rowman.com wrote:> 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.tpl > > instead of the usual (with the default script install): > > http://localhost/cgi-bin/WebCatalogEngine/Admin/index.tpl > > The 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 ------------------------------------------------------------- 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/ Alan White

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:

faxing orders (2000) WC2.0 Memory Requirements (1997) shipcost (1997) problems with 2 tags (1997) The beginning (1997) Problems getting parameters passed into email. (1997) Cancel Subscription (1996) Running _every_ page through WebCat ? (1997) searching with groups (1997) Stumpted Again (1997) [WriteFile] problems (1997) Add a field to the error log? (1997) [WebDNA] Encryptng a password (2016) MacAuthorize Problem (1998) emailer error type 103 (1997) install on redhat (2004) Running 2 two WebCatalog.acgi's (1996) Photo Album (2000) Safari browser and WebDNA set-cookies (2003) Server replication (1998)