You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: