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
It can be cumbersome to spin up resources in AWS accounts and run cartography.
Instead we should have a way to run the proxy, frontend, backend, neo4j, and postgres containers. There should be options of datasets to load into Neo4j. Security rules should run on this data and everything should show up in the frontend appropriately.
One possible way to do this:
Look at all instances where the backend container makes calls to cartography
Have some environmental variable setting where backend container can run without making those calls
Create some way of mocking the neo4j. Maybe this is a script with manual inserts? Maybe we have some neo4j data files that we commit to repo?
Create another docker-compose dev setup where the backend container is run with the appropriate env variable, the cartography container is not run, and the neo4j data is hardcoded
The text was updated successfully, but these errors were encountered:
It can be cumbersome to spin up resources in AWS accounts and run cartography.
Instead we should have a way to run the proxy, frontend, backend, neo4j, and postgres containers. There should be options of datasets to load into Neo4j. Security rules should run on this data and everything should show up in the frontend appropriately.
One possible way to do this:
The text was updated successfully, but these errors were encountered: