Closed jj0hns0n closed 11 years ago
This needs to include the suite importer as well which is not currently included when built using the instructions above.
There are a couple more jobs on the LMN jenkins server. One that builds the importer extension, and another that combines the outputs of the geoserver with geogit, importer, and geonode ext jobs.
The final .war ends up at http://jenkins.rogue.lmnsolutions.com/userContent/geoserver.war
Reopening ... switching to a mvn based approach here. pom.xml will go in https://github.com/ROGUE-JCTD/rogue_geonode/
@mweisman we need the following
geogit (should build against the nightlies) suite importer (including the required restlet jar) gsr (in geoserver-exts) kml (in geotools) geoserver-geonode-ext mapfish (think that the geoserver-geonode-ext builds this) wps (from suite?) printng (from geoserver-exts) gdal/ogr
Closing this and moving further work to rogue-devops repo.
We currently have 2 build jobs in the ROGUE Jenkins, one that builds GeoServer with the GeoGit extensions and one that builds the geoserver-geonode-ext against the 2.3.x branch. Beyond that, a developer must first deploy the geoserver war into a servlet container and then drop the geonode jars in. It would be great to have another job that builds out a complete war that includes both of these and to update the paver task to use this one. Kevins instructions are pasted below.
Here's what we're doing currently to get up and running right now just in case:
We're building GeoGit from the ROGUE-JCTD/GeoGit master branch. Then we're building GeoServer from the groldan/geoserver geogit branch w/ the geogit dependency in src/web/app/pom.xml as 0.2-SNAPSHOT
After deploying that to tomcat7, we're building the geonode-geoserver-ext-0.3.jar from the GeoNode/geoserver-geonode-ext fork. We merged in the user-details branch into the 2.3.x and built from there.
After building that, we drop that jar along with gt-process-9.0.jar into the geoserver WEB-INF/lib directory, make sure that they're owned by tomcat7 and at least 600 permissions, and then restart.
The version of GeoNode that we're using right now is from the ROGUE-JCTD/GeoNode salamati branch.
For our set up, we're cloning that into a python virtualenv at /var/lib/geonode, installing it, running python manage.py collectstatic, setting up a symlink for nginx to reach the static files:
cd /usr/share/nginx/geonode ln -s /var/lib/geonode/geonode/geonode/static_root/ static
setting the following permissions:
chmod 755 /var/lib/geonode /var/lib/geonode/geonode /var/lib/geonode/geonode/geonode chmod 755 -R /var/lib/geonode/geonode/geonode/static_root/
and modifying the settings.py file with the appropriate urls (ex. geoserver.rogue.lmnsolutions.com) and geoserver credentials.