Currently it's best to have GeoNode in its own Apache virtualhost; it does not support well the use case of having other directory paths on the same server used for other services. You could probably get it to work with a little digging.
The Ubuntu installer currently assumes that it's being used on a dedicated machine - so the VirtualHost configuration in /etc/apache2/sites-available/geonode specifies a hostname of '*'. It also disables the "default" site that's configured by Ubuntu's apache2 package. If you disable the geonode site and re-enable the default one: $ sudo a2dissite geonode && sudo a2ensite default && sudo > /etc/init.d/apache2 restart You should be back to the same server configuration you started with. You can then use the apache configuration in /etc/apache2/sites-available/geonode as a basis for integrating GeoNode into your existing service. One easy way to get it working would be to set up an additional domain name for your server (perhaps just a "geonode" subdomain of your existing hostname) and to specify that instead of "*" in the VirtualHost header. Hope it helps. -- David Winslow OpenGeo - http://opengeo.org/ On Tue, Feb 7, 2012 at 8:54 AM, Ragnvald Larsen <[email protected]>wrote: > Just did a clean install of Geonode starting with Ubuntu 10.4.3 > > * Did the Ubuntu install > * All upgrades > * Webmin > * Wordpress in folder 10.10.4.10/wp > * Geonode (sudo apt-get install geonode) > > Conclusion: The Geonode is exactly delicate about it's handling of the > apache setup. Now the wordpress address defaults to geonode. Not at all > humble... > > Since I am not too conversant with the apache setup I would rather > Geonode set itself up in a dedicated folder(s) and kept away from other > services. I also tried setting up geonode on a server serving two > domains. It didn't go too well... :-) > > Integrating geonode with Wordpress or other CMSes is something which I > believe can be a great combination! > > Thanks! > > Ragnvald >
