Currently the Map and Tools frontend code is linked to the test instance of frontend-mongodb. This means that local dev testing can result in entries being created in the test frontend-mongodb and test-index, which is not ideal.
The aim is to spin up a local instance of mongodb that can be used for frontend code testing in development, and that is coordinated with the local dev version of the index, library, etc. Thus when a local dev instance of Services is instantiated, the local instance of frontend-mongodb will be instantiated with it and all local testing of Map and Tools will write to the local frontend-mongodb and the local index, and it will fetch schemas from the local library.
[ ] Setup local instance of front-end mongo
[ ] Enable front-end mongo to talk to local instance of Services (index, library, etc.)
[ ] Enable local Tools/Map instance to talk to front-end mongo and Services (index, etc.)
[ ] Setup seed data import so front-end mongo and index can be loaded with test data
Currently the Map and Tools frontend code is linked to the test instance of frontend-mongodb. This means that local dev testing can result in entries being created in the test frontend-mongodb and test-index, which is not ideal.
The aim is to spin up a local instance of mongodb that can be used for frontend code testing in development, and that is coordinated with the local dev version of the index, library, etc. Thus when a local dev instance of Services is instantiated, the local instance of frontend-mongodb will be instantiated with it and all local testing of Map and Tools will write to the local frontend-mongodb and the local index, and it will fetch schemas from the local library.