Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update GeoGig bundle links and remove BerkeleyDB plugin #12

Merged
merged 2 commits into from
Sep 15, 2017
Merged

Update GeoGig bundle links and remove BerkeleyDB plugin #12

merged 2 commits into from
Sep 15, 2017

Conversation

emerkle826
Copy link
Contributor

The links to GeoGig bundles are stale as the build jobs have
moved to a new server. Also, since the 1.0 release of GeoGig,
the BerkeleyDB plugin has been mostly abandoned. It has been
replaced by RocksDB, which is included in the GeoGig bundle.

Signed-off-by: Erik Merkle emerkle@boundlessgeo.com

  The links to GeoGig bundles are stale as the build jobs have
  moved to a new server. Also, since the 1.0 release of GeoGig,
  the BerkeleyDB plugin has been mostly abandoned. It has been
  replaced by RocksDB, which is included in the GeoGig bundle.

Signed-off-by: Erik Merkle <emerkle@boundlessgeo.com>
@emerkle826
Copy link
Contributor Author

This PR should address issues #10 and #11.

NOTE: BerkeleyDB support in GeoGig has been abandoned and replaced with RocksDB. There isn't an easy way to convert an existing GeoGig repository using a BerkeleyDB backend to RocksDB.

The only way to do so is to use an old version of GeoGig (1.0-RC3 would be the best to try: https://github.com/locationtech/geogig/releases/tag/1.0-RC3) an export your repository into a shapefile, geopackage or postgis database, then create a new RocksDB backed repository, then import the data from the export.

This process has not been tested very much and may not completely preserve your BDB backed repository. Please consider this before merging.

Copy link
Contributor

@luipir luipir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/geogig/lib should be /geogig/libexec in case of dev version

setup.sh Outdated
@@ -19,16 +19,17 @@ fi
# install plugins
if [ -d /geogig/lib ]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should update /geogig/lib to libexec in case of dev version

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch again

Signed-off-by: Erik Merkle <emerkle@boundlessgeo.com>
@luipir
Copy link
Contributor

luipir commented Aug 29, 2017

@timlinux this is a GeoGig Bioundless team contribution. I checked it and it works. It has been adapted to also install dev version. For me it can be merged.

For no dev version, e.g. latest 1.1.1 you can use directly docker pull from
https://hub.docker.com/r/boundlessgeodesktop/geogig/
In any case this images are build from the kartooza dockerfile.

Copy link
Contributor

@luipir luipir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because of:
wget http://build.geoserver.org/geogig/master/geogig-master-latest.zip
--2017-08-29 18:09:29-- http://build.geoserver.org/geogig/master/geogig-master-latest.zip
Resolving build.geoserver.org (build.geoserver.org)... 34.204.115.146
Connecting to build.geoserver.org (build.geoserver.org)|34.204.115.146|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://build.geoserver.org/geogig/master/geogig-master-latest.zip [following]
--2017-08-29 18:09:33-- https://build.geoserver.org/geogig/master/geogig-master-latest.zip
Connecting to build.geoserver.org (build.geoserver.org)|34.204.115.146|:443... connected.
ERROR: cannot verify build.geoserver.org's certificate, issued by ‘CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US’:
Unable to locally verify the issuer's authority.
To connect to build.geoserver.org insecurely, use `--no-check-certificate'.

probably is better to revert this change. It give a stablñe link, but only after we can solve this certificate problem

@emerkle826
Copy link
Contributor Author

I reverted that last commit. Not sure what the certificate issues are with wget as web browsers seem to be fine. For now, you can still use the slave backend URL.

@luipir
Copy link
Contributor

luipir commented Aug 29, 2017

tnx... @emerkle826 . @timlinux PR ready for merge.

@NyakudyaA NyakudyaA merged commit 91903e9 into kartoza:master Sep 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants