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

MongoDBManager ignores webprotege.properties #65

Merged
merged 1 commit into from
Nov 1, 2013

Conversation

mever
Copy link
Contributor

@mever mever commented Oct 26, 2013

Hello,

When installing Webprotege, I used a MongoDB server that was not installed locally. I changed the settings in webprotege.properties and expected Webprotege to use the remote MongoDB server. However, I still saw Webprotege trying to connect locally.

After some exploring I found the MongoDBManager not getting the settings I had entered in the webprotege.properties file. To resolve that issue I made some changes in the MongoDBManager.

I have tested it, and it works for me on a remote and locally installed MongoDB server.

Kind regards,
Martijn Evers

matthewhorridge added a commit that referenced this pull request Nov 1, 2013
MongoDBManager ignores webprotege.properties
@matthewhorridge matthewhorridge merged commit 12ff117 into protegeproject:master Nov 1, 2013
@robvandort
Copy link

I think you solved most, but not all of the problems.
Please look at application.host and data.directory properties (I had problems in local / devmode).

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