How kailash105/agro-aura works
Main Components
• Frontend: This is where users vibe with the app. It’s powered by the HTML in templates (index.html) and styled with CSS from static/style.css. Don’t forget the static/images that spice up the UI.
• Backend: Run by app.py, this is the heart of the operation where all the magic happens. It handles routing, user requests, and communicates with the brain of the project.
• Machine Learning Model: Our sick ML model (WheatDiseaseDetection.h5) is key – it’s the wizard that analyzes wheat diseases. Also, check out the WheatDiseasePrediction.ipynb – that’s where experimentation and model magic took place.
• Data Source: The Data Source for the Wheat Disease Prediction.rtf file tells you where the dataset came from. It’s the starting point for all our model’s insights.
• CI/CD & Deployment: With all the GitHub actions (.github/workflows/python-package.yml), you know we’re keeping our code super fresh and automated.
How They Interact
• Users hit the frontend, send in requests, and then app.py processes these calls.
• The backend communicates with the ML model to get predictions and then serves back results.
• There’s a flow from raw data (Data Source file) to model training (notebook) to a production-ready model (.h5 file).
• GitHub workflows are doing their thing in the back, automating our deployment and ensuring everything’s up-to-date.
Architectural Vibes
• This is a full-stack app with a chill separation between frontend and backend.
• The ML component is a separate powerhouse that integrates directly with app.py.
• Modular design: Each folder (static, templates, etc.) has its own role, making the structure as sleek as your playlist.