Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide the tech stack and design ideas #5

Closed
1 of 2 tasks
Tracked by #4
pbiology opened this issue Oct 18, 2023 · 1 comment
Closed
1 of 2 tasks
Tracked by #4

Decide the tech stack and design ideas #5

pbiology opened this issue Oct 18, 2023 · 1 comment
Labels
project planning Non code related issues

Comments

@pbiology
Copy link
Contributor

pbiology commented Oct 18, 2023

Description

The tool needs to have an established and agreed upon tech stack and design ideas so we all can think about how to implement functionality.

Suggested solution

Have lead developers suggest and decide upon a tech stack

This can be closed when

  • A tech stack and design ideas exist for this project
  • Documented somewhere in this repo

Blocked by

@pbiology pbiology added the project planning Non code related issues label Oct 18, 2023
@pbiology pbiology added this to the MVP milestone Oct 18, 2023
@pbiology
Copy link
Contributor Author

We have decided to go with a split frontend/backend and to use a mongoDB solution for keeping data in the backend.
Endpoints needed will be built using FastAPI or equivalent.

As for frontend this is yet to be fully decided due to not having any frontend resources at the moment.

At some point it would be nice to have the design/architecture documented, but this will be created at a later stage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project planning Non code related issues
Projects
None yet
Development

No branches or pull requests

1 participant