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

Supporting GeoServer integration using multi-machine Vagrant configuration #7

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

jrgriffiniii
Copy link

Dear @drh-stanford @eliotjordan and @johnhuck

This should pull the release of geoserver-vagrant from Atlas, and deploy this into a multi-machine environment. I have also attempted to update the README accordingly.

As a brief warning, please note that one can encounter resource consumption issues which would lead to errors such as https://www.virtualbox.org/ticket/11127. I could only resolve this by deleting any number of downloaded/cached Vagrant Boxes (vagrant box list; vagrant box remove [BOX_NAME]). After removing some critical threshold, the error could not be reproduced.

…cating the usage of a 32-bit Ubuntu Base Box for the demo build BASH script; Ensuring that the Puma server does not run as a daemon when invoked using the demo:servers Rake task; Avoid setting the VM name to "geoconcerns", as Vagrant overrides the "localhost" /etc/hosts entry for 127.0.0.1
…tegrating the GeoServer machine into a multi-machine environment
@drh-stanford
Copy link

I think we need geoserver to run on the same VM as the geoconcerns rails server. The GeoServer engine needs http access to the rails server directly. Maybe I'm misunderstanding the port forwarding scheme?

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.

2 participants