Skip to content

RFC: path forward re: frontend #125

@mtbentley

Description

@mtbentley

Here are some of the idea's we've discussed regrading how to better integrate the frontend with the backend:

  • Create a "frontend" lib in the backend, and all frontend communication just calls those functions. The frontend then imports the backend, and calls those functions. In this option, either:
    • The frontend also starts the backend, and is the "main" project people clone/download to use syncr
    • The frontend and backend have to be started separately, and some metaproject is created to start both
  • Copy the frontend into the backend (and archive the frontend repo), and have the backend directly start the frontend. In this option, the frontend can just call backend functions. We can use the quart library as a drop in replacement to flask so the frontend is just another coroutine

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions