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

RFC: path forward re: frontend #125

Open
mtbentley opened this issue Jun 9, 2018 · 0 comments
Open

RFC: path forward re: frontend #125

mtbentley opened this issue Jun 9, 2018 · 0 comments
Assignees

Comments

@mtbentley
Copy link
Member

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants