Chuck, I don't think the op was along to change the port of the management gui. I think he meant to change the port which apache listens on for normal hosted sites.
Regards, James Darbyshire Sent from my Samsung Droid™ On 04/12/2010 11:41 AM, "Chuck Tetlow" <[email protected]> wrote: The BlueOnyx management GUI is already on a different port - TCP 444. Guess you haven't built or used a BX yet - you probably would have noticed that right off the bat. No, there is no way in the GUI to change the port the webserver listens on. That's such a odd and uncommon request that I'd bet the design guys never thought someone would ask for it, and so they didn't provide it. Of course, you could always manually edit the vhost conf files. (Don't know that you could do it on a per-site basis in the vhosts file. You might have to do it in the httpd.conf file for the whole server) But the BlueOnyx management scripts have a bad habit of overwriting manually edited config files. I used to keep my /etc/sysconfig/iptables file locked (set to immutable) - until I figured out how to edit the management scripts and have it build that file with my unique modifications. Just a warning - you might have to lock the file after modification or be ready to change it again. Chuck ---------- Original Message ----------- From: Jeffrey Garruba <[email protected]> To: "Blue... *------- End of Original Message -------* _______________________________________________ Blueonyx mailing list [email protected] http://www.blueonyx.it/mailman/listinfo/blueonyx
_______________________________________________ Blueonyx mailing list [email protected] http://www.blueonyx.it/mailman/listinfo/blueonyx
