I fixed the issue of the "broken" server referred to in my email, but
was really a bit surprised that Geonode was that "straightforward" in
it's install, so this is what I want:
The geonode install accepts a setup.cfg-file in which special parameters
and options are indicated. It should contain:
* default ip/address
* contact email
* Apache choices
* Current alternative
* Polite alternative:
* Installs under default domain
* Leaves other domains untouced
* Does not interfere with other folders (allows wordpress
or other CMS installs)
So why have more than one system on a server...? Well, the way geonode
ties things together on the spatial data side is fantastic! Integrating
Geonode with a CMS is effectively making something very close to a
clearinghouse, in this case for environmental information. Being able to
combine the Geonode data from within a cms-system on the same server is
both practical and cheaper than having two separate servers running.
I will probably move forward with a process similar to the one me and
Reinier Battenberg was involved in in Uganda in a different country
later this month. In that case we will demo Geonode and some data we had
the oportunity to harvest at an earlier stage. I will look forward to
being able to embed geonode-made maps with services from geoserver and
geonetwork and datase information from PostGIS or MySQL on a stand-alone
server. Wether that system is Wordpress, Tikiwiki, Drupal or other is
not important.
For solving the problems on apache I have back-office capacity
available. But it deserves a better resolution and documentation so that
the install can easier be combined "out of the box".
Lastly a BIG thankyou to the Geonode team, Opengeo, Worldbank, GFDRR,
AIFDR and others for providing us with Geonode!
Ragnvald
http://www.mindland.com
On 07.02.2012 15:55, David Winslow wrote:
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]
<mailto:[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 <http://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
