Conversation
Coverage Report
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Sorry @samhuestis there is absolutely no need for you to actually review all of the changes here (they are drastic, and there are a lot). I am mainly just tagging you so you are aware of the breaking changes I am proposing here. Essentially, I am bringing Crucially, this involves splitting the application into 2 "services" ("database" and "API"), and using docker-compose to orchestrate those services. To do that, I swapped out the static |
|
I will probably force-merge this in the next few days, but please let me know if you have any major questions here. |
jdhoffa
changed the title
Given the latest approved version of the PRD for this project, it was determined that the database and API services that we had originally envisioned won't be necessary until a later version of the application. To keep things stream-lined, @AlexAxthelm @cjyetman and myself have decided to focus solely on the React front-end in this repository. Shortly, we will enable continuous deployment of this React application directly to production, based on the GitFlow branching strategy. This also benefits from us reducing technical debt and overhead that is not immediately useful or required for the deployment or serving of the application. With that said, given that we do anticipate a future need for a database and API, we have kept the scaffolding of this available in the [web-api-poc](https://github.com/RMI/web-api-poc) repository. Specifially, an identical version of the `api` and `db` services, all relevant actions, tests, integration tests, `docker` and `.env` set-up and other related goodies have been preserved in that repository. Relates to RMI/web-api-poc#56 --------- Co-authored-by: CJ Yetman <cj@cjyetman.com>
2 participants
This PR begins a large overhauling process to merge in many changes to this repository. Needless to say these are breaking changes.
Primarily, this is being done to back-merge in changes that were gained in the pbtar repository, in both the
databaseandapiservices.These are still generic demonstrations of how we can integrate a DB and API while implementing best practices.