feat: split backend and frontend service #215
Draft
Conversation
This file contains 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
Johannes-Andersen
added
type/feature
Johannes-Andersen
force-pushed
the
feat/splitBackendAndFrontend
branch
from
b0f7cfb
to
0da1894
Compare
Johannes-Andersen
force-pushed
the
feat/splitBackendAndFrontend
branch
2 times, most recently
from
41a830a
to
0d85289
Compare
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR is a part of a project to split up the Python WAAS API and the Frontend into two separate services
The end goal is to be able to deploy the Astro frontend and Python backend on their own.
Also choosing a more suitable frontend framework (in this case we chose Astro) should make it easier to contribute to the frontend codebase
Bonus goals:
Long term this will also make it easier for us to switch out the backend service with something else. Whisper c++, WhisperX, etc...