ADR: Static Dashboards - Preserve MMGIS Features#96
Open
CarsonDavis wants to merge 4 commits into
Open
Conversation
CarsonDavis
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This ADR examines how we can keep the existing MMGIS features in a split deployment scenario, with an admin portal and deployed static dashboards. It preserves the python side cars, on server data processing, etc.
When reading over these files, I would suggesting starting with the overview and then moving on to the two ADRs. The implementation plan is not meant for review and is provided to ground LLM interactions.
Important
Many of the open questions in this ADR are resolved and much of the deployment infrastructure is irrelevant if we instead go the path of removing those features and only using existing external services #95.