Disable setup of per-cluster featureService #123
It takes a few hours to setup the database in hosted postgres which makes our deployments too long, so for now using a central database and featureService deployment.
Leaving the original code commented out because we need to move away from the central database sooner rather than later...
The text was updated successfully, but these errors were encountered:
* Fixed admin setting integration issues * A variety of bug fixes to support pulling fortis events from the cassandra table into the news feed. * A variety of fixes to support showing fortis events in the news feed. * Fixing linting errors * Reverting executeQuery change * Fixing lint errors * Messages byBbox schema changes round II * Consolidating mainEdge and filteredEdges as conjunctivetopics field * Addressing clemens PR review comments * rebasing * Adding avgsentiment calc * Refactoring topSources GQL service * Reorganizing aggregation logic * Reorganizing aggregation logic * Adding heatmap by tileid service * Adding fetchTileIdsByPlaceId endpoint for tiles schema * Fixing linting errors * Fixing linting errors