Game plan: integrating infrastructure

[kbuffardi]

As discussed in our Sprint 1 retrospective, we need a deliberate approach to integrating all the independent parts to the infrastructure. In this discussion, please decide the best approach to integrating:

• new postgres database
• docker compose container(s)
• ReactJS-based front-end
• Actions CI
• Jest testing (including coverage reporting)

Once the strategy to integrating these parts together is agreed upon, it would be appropriate to create new issues for each major step of the integration process.

[jayrevolinskyjr]

As a comment in this discussion, I believe that each integration team (as mentioned in Dr. Buffardi's bullet points) should report on their progress, making sure to include where their work overlaps with other parts of the project infrastructure. After that, we continue the discussion and clear up where we take the project infrastructure.

AFAIK, it seems that much of the integration is finished.

[reembot]

I agree that this would help guide a consecutive approach. Without sight on progress for the teams, my best (non-expert) guess at how to tackle these would be in this order:

1. new postgres database
2. ReactJS-based front-end
3. docker compose container(s)
4. Jest testing (including coverage reporting)
5. Actions CI - updated below

Our front-end will need a finalized database to plug into, at which point having Docker will allow everyone to build and contribute. From there, integrating testing into our Actions CI seems like a good way to ensure future PRs are clean.

[jayrevolinskyjr]

CI Team:

• The Build workflow is implemented and runs automatically on pull requests, it is currently configured to work with TypeScript.
• The Linter is implemented and runs automatically on pull requests, we had some blockers with making sure the linter's configuration did not cause the project to fail to build but those have been resolved.
• I know the build and linter workflows function on their own but I am unaware if they work inside the docker container or if it is even necessary. What does the docker team think?

Please feel free to add something if I missed it.

[briswells]

Database Team:

• New DB is up and running
• Most routes have been updated to work with new DB and old views
• Routes will need to be minority updated to work with React front end.

I think next step would be getting the new backend working with the new front end. This will require the Node docker container to run the React site instead of the current views. After this is done we can update routes to post JSON data instead of rendering, but this shouldn't be a big change.