Hi All,

I would like to utilise extra security on our raq by putting some admin features on it (namely myPhPadmin and some other DB admin tool) so it works the same as when u goto www.yourserver.com:81/admin to setup the domains etc.

Can this be done and if so where is the directory to store them in?

TIA

Simon Malings

You need to create another virtual site and in its configuration directives you have to tell it to only listen on the port you choose. In the VirtualHost directive just specify the port.
xxx.xxx.xxx.xxx:port number


Or you could create another instance of apache and use a seperate configuration file. This would be reccommended so that the cobalt control panel does not overwrite your changes to the main web server.

Take a look at the admserv conf file in /etc/admserv/conf/httpd.conf as an example. You could just clone this script making the appropriate changes to it and the start up script in /etc/rc.d/init.d

Also, make sure that you pick a good port number. I think the control panel may use port 81 -- check the conf file.

Lastly, if you want to get to the admin section without specifying the port number you will have to do some re-write work in your machine http server so that it will automatically forward people over to the alternate server on the other port.

And unless you do some fancy footwork in the httpd.conf, I don't think you can name the directory http://yourdomain:port/admin The redirect rules will send any /admin request to the control panel.

Frank

i was hoping i could just copy up a page to wherever the port 81 points too and call it from browser eg http://ns1.mydomain.com:81/myphpadmin.php

can i not do this easily then?

I want to change the httpd.conf - to change the AllowOverides to All

Do I have to edit the httpd.conf.master file to ensure that this change is not regressed by the cobalt control panel?

Can someone explain whether I can edit httpd.conf without losing changes?

Hello - anyone out there?

Pilot,

Do a search on this board, but the proper file to edit is the srm.conf. There is an AllowOverride directive set to None in it. I can't remember the exact line so do a search on AllowOverride and you will find the answer.

On second thought that may be in the access.conf file.

AllowOverride works fine in httpd.conf - the actual feature works now.

My question was whether my edit of that file would be regressed by subsequent updates made by the Cobalt control panel interface.

Probably, that is why you should do it in access.conf. It is on the line just before the line that says

#ignore .ht*

Change line that says

AllowOverride None

to

AllowOverride All