Skip to content
This repository has been archived by the owner on Apr 4, 2022. It is now read-only.

Provide separate settings for MongoDb #3

Open
mmoayyed opened this issue Aug 7, 2016 · 1 comment
Open

Provide separate settings for MongoDb #3

mmoayyed opened this issue Aug 7, 2016 · 1 comment

Comments

@mmoayyed
Copy link

mmoayyed commented Aug 7, 2016

If the application is already using a MongoDb instance for other purposes, the auto-wiring capability of this module will have "the same" mongo-db instance be used for managing properties. This is impractical. Instances should be defined separately.

@venilnoronha venilnoronha self-assigned this Nov 1, 2016
@venilnoronha venilnoronha removed their assignment Aug 31, 2017
@johara13
Copy link

I am in the same situation. I want to use a mongoldb to hold the properties file but have a different database that the application sues for actually running and storing and reading data. Is there a way to have it point to mongodb specifically for the config and not have it affect the mongoldb being used for that actual application?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants