zadarum wrote:
I'm new at setting up a web app
using WAR files, but as I understand it, I have to have a separate
instance of the BD directories in each of my virtual host root
directories, so that each one can be configured for the purposes of
that app (as opposed to CF8 in Windows, where a single instance of the
server app can be used across multiple virtual hosts).  If I'm wrong
about that, I'd appreciate any guidance on that aspect of
configuration.

Short answer, yes. You *can* configure things in such a way that all your apps would leverage a single instance of OpenBD (in fact if I'm not mistaken that's how Jordan's Linux installer works), but I just include the OpenBD runtime libraries on a per-project basis.

However, that's not my problem at the moment.  With the separate
instances of BD in the virtual hosts, things are working properly, but
I was concerned with allowing open access to the admin interface, and
thought I'd fix that by setting the allowedip value in the admin
interface.  For the ip address host, it worked fine to use my internal
ip address range (192.168.1.*).  However, for the named host, using
that range (and even adding in the public ip address) results in a
blank screen.  I have to reset the values in bluedragon.xml and
restart jetty to get back to that admin interface.

Just want to make sure I'm understanding. So you set the IP address range, and that works. But when you use the hostname in your browser, even if that hostname resolves to an IP address in the range you've specified, it doesn't work.

My first point of confusion is that you have to reset the values in bluedragon.xml. You aren't putting the hostname in the admin as opposed to an IP address are you?

I'm happy to help troubleshoot to see if there's something up with the admin console code.

--
Matt Woodward
[email protected]
http://www.mattwoodward.com/blog

Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to