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

Integration Guide - General Rules #1

Open
app-generator opened this issue Dec 13, 2022 · 0 comments
Open

Integration Guide - General Rules #1

app-generator opened this issue Dec 13, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@app-generator
Copy link
Owner

app-generator commented Dec 13, 2022

Hello guys,

As a general rule, the goal is to reuse the Django work with minimal effort WITHOUT adding anything functional (DB, login, logout, registration). Here, only the pages should be served without issues.

this is the one and only evolution required.

Here is the migration/integration guide:

  • assets should remain untouched
  • all pages preserved (no deletion)
  • assets loaded via the static tag
    • only adapted for flask
    • No more hardcoded /static/assets usage
  • No dependencies added
  • No database

Basically, all pages should be updated to be rendered by Flask without any functional code for:

  • sign in
  • sign up
  • reset pass
  • other actions

Only the pages should be linked

signIN <-> registration <-> reset password and other linked
Logout link for instance is linked to signIN in order to simulate the action

Let me know here or via UpW if something is now clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants