Skip to content

backend migration setup: Initialize Flask project structure with MongoDB connection #1529

Closed

Description

@the404packet

Describe your issue

Create the base Flask backend inside website4.0/backend/.

Tasks:

  • Setup Flask app with create_app() factory pattern
  • Connect MongoDB using pymongo + .env
  • Add flask-cors for frontend communication
  • Create base folder structure (routes/, models/, utils/)
  • Add requirements.txt and run.py

Files to create :
website4.0/backend/
├── app/init.py
├── app/utils/db.py
├── requirements.txt
├── .env.example
└── run.py

Expected behavior

No response

Steps to reproduce

No response

Environment

No response

GSSoC Participation

Activity

  1. github-actions commented on May 27, 2026

    @github-actions
    Contributor

    Hello the404packet, Thanks for opening an issue in HelpOps-Hub! 🚀

    • Please make sure to follow our Contributing Guidelines.

    • Hope you star our Repo.

    • Join our official Discord server, where we can collaborate and discuss how to make HelpOps-Hub even better and more professional.

    • Don’t forget to follow us on LinkedIn!

  2. the404packet commented on May 27, 2026

    @the404packet
    ContributorAuthor

    @mdazfar2 I will start the backend migration from file to file. Pls assign me this issue.

  3. SaumyaSngh323 commented on May 31, 2026

    @SaumyaSngh323

    Hi i would like to work on this issue please assign me i would give PR in 4-5 days

  4. mdazfar2 commented on May 31, 2026

    @mdazfar2
    Owner

    Hey @the404packet, the issue you created is actually really good.

    But have you checked issue #1521, the pinned one? Actually, I want someone to completely migrate the frontend Next.js project to TypeScript, and then your issue about migrating the backend and converting it to Flask is also a great idea.

    • What I’m thinking is that it would be even better if both migrations could happen together. If you know someone who might be interested, you guys can discuss it together and work on it collaboratively.
      You can also join the WhatsApp group for easier discussion.

    • And I wanted to ask one more thing right now our Next.js website is in .js format and it’s serverless, right? So if we migrate the backend to Flask, will we need to keep the backend and frontend in separate folders/projects, or can it still stay like it is now, where both the backend server and frontend server run from the same root folder? Would it work the same way with a Flask Python backend too?

  5. the404packet commented on Jun 5, 2026

    @the404packet
    ContributorAuthor

    Hi @mdazfar2, sorry for the late reply. Been busy past days.

    Next.js and Flask will run separately. We can make it run together by dockerizing them.

    We can go ahead with frontend migration first,
    I suggest this workflow for migrations

    1. Migrate individual pages first.

    2. Integrate those pages means linking the pages

    3. We can start with backend migration then

    But before this we need to setup a proper CI/CD for this so that all pushes are monitored.

    Should I proceed with this, I will create the respective issues.

  6. mdazfar2 commented on Jun 6, 2026

    @mdazfar2
    Owner

    Okay @the404packet create issue accordingly
    And do it in root folder website 4.0 production ready website

  7. github-actions commented on Jul 7, 2026

    @github-actions
    Contributor

    This issue has been automatically closed because it has been inactive for more than 30 days. If you believe this is still relevant, feel free to reopen it or create a new one. Thank you!

  8. alexandra272003 commented on Jul 7, 2026

    @alexandra272003

    Is this issue still going? if yes, please assign it to me as Gssoc 26 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions