app-generator / flask-material-dashboard

Flask Dashboard - Material Design | AppSeed

Flask Dashboard Material

Open-source Flask Dashboard generated by AppSeed op top of a modern design. Designed for those who like bold elements and beautiful websites, Material Dashboard is ready to help you create stunning websites and web apps. Material Dashboard is built with over 70 frontend individual elements, like buttons, inputs, navbars, nav tabs, cards, or alerts, giving you the freedom of choosing and combining.

• 👉 Flask Dashboard Material - product page
• 👉 Flask Dashboard Material - LIVE deployment

Features

Have questions? Contact Support (Email & Discord) provided by AppSeed

Free Version	PRO Version	Custom Development
✓ Up-to-date dependencies	Everything in Free, plus:	Everything in PRO, plus:
✓ Best Practices	✅ Premium Bootstrap 5 Design	✅ 1 Week Custom Development
✓ DB: SQLite, MySql	✅ PRO Support - Email & Discord	✅ Team: PM, Developer, Tester
✓ DB Tools: ORM, Flask-Migrate	✅ Private REPO Access	✅ Weekly Sprints
✓ Session-Based authentication	-	✅ Technical SPECS
✓ Docker	-	✅ Documentation
✓ CI/CD Flow via Render	-	✅ 30 days Delivery Warranty
✓ Free Support	-	✅ CI/CD for AWS, DO (Extra)
---------------------------------	---------------------------------	---------------------------------
✓ LIVE Demo	🚀 LIVE Demo PRO	Get in Touch ➡️

✅ Start in Docker

👉 Step 1 - Download the code from the GH repository (using GIT)

$ git clone https://github.com/app-generator/flask-material-dashboard.git
$ cd flask-material-dashboard

👉 Step 2 - Start the APP in Docker

$ docker-compose up --build 

Visit http://localhost:5085 in your browser. The app should be up & running.

✅ Manual Build

Download the code

$ git clone https://github.com/app-generator/flask-material-dashboard.git
$ cd flask-material-dashboard

👉 Set Up for Unix, MacOS

Install modules via VENV

$ virtualenv env
$ source env/bin/activate
$ pip3 install -r requirements.txt

Set Up Flask Environment

$ export FLASK_APP=run.py
$ export FLASK_ENV=development

Start the app

$ flask run

At this point, the app runs at http://127.0.0.1:5000/.

👉 Set Up for Windows

Install modules via VENV (windows)

$ virtualenv env
$ .\env\Scripts\activate
$ pip3 install -r requirements.txt

Set Up Flask Environment

$ # CMD 
$ set FLASK_APP=run.py
$ set FLASK_ENV=development
$
$ # Powershell
$ $env:FLASK_APP = ".\run.py"
$ $env:FLASK_ENV = "development"

Start the app

$ flask run

At this point, the app runs at http://127.0.0.1:5000/.

👉 Create Users

By default, the app redirects guest users to authenticate. In order to access the private pages, follow this set up:

• Start the app via flask run
• Access the registration page and create a new user:
  • http://127.0.0.1:5000/register
• Access the sign in page and authenticate
  • http://127.0.0.1:5000/login

✅ Codebase

The project is coded using blueprints, app factory pattern, dual configuration profile (development and production) and an intuitive structure presented bellow:

< PROJECT ROOT >
   |
   |-- apps/
   |    |
   |    |-- home/                           # A simple app that serve HTML files
   |    |    |-- routes.py                  # Define app routes
   |    |
   |    |-- authentication/                 # Handles auth routes (login and register)
   |    |    |-- routes.py                  # Define authentication routes  
   |    |    |-- models.py                  # Defines models  
   |    |    |-- forms.py                   # Define auth forms (login and register) 
   |    |
   |    |-- static/
   |    |    |-- <css, JS, images>          # CSS files, Javascripts files
   |    |
   |    |-- templates/                      # Templates used to render pages
   |    |    |-- includes/                  # HTML chunks and components
   |    |    |    |-- navigation.html       # Top menu component
   |    |    |    |-- sidebar.html          # Sidebar component
   |    |    |    |-- footer.html           # App Footer
   |    |    |    |-- scripts.html          # Scripts common to all pages
   |    |    |
   |    |    |-- layouts/                   # Master pages
   |    |    |    |-- base-fullscreen.html  # Used by Authentication pages
   |    |    |    |-- base.html             # Used by common pages
   |    |    |
   |    |    |-- accounts/                  # Authentication pages
   |    |    |    |-- login.html            # Login page
   |    |    |    |-- register.html         # Register page
   |    |    |
   |    |    |-- home/                      # UI Kit Pages
   |    |         |-- index.html            # Index page
   |    |         |-- 404-page.html         # 404 page
   |    |         |-- *.html                # All other pages
   |    |    
   |  config.py                             # Set up the app
   |    __init__.py                         # Initialize the app
   |
   |-- requirements.txt                     # App Dependencies
   |
   |-- .env                                 # Inject Configuration via Environment
   |-- run.py                               # Start the app - WSGI gateway
   |
   |-- ************************************************************************

✅ PRO Version

For more components, pages, and priority on support, feel free to take a look at this amazing starter:

Flask starter styled with Material Dashboard PRO, a premium Bootstrap 5 KIT from Creative-Tim. The product is designed to deliver the best possible user experience with highly customizable feature-rich pages.

• 👉 Flask Material 2 PRO - Product page
• 👉 Flask Material 2 PRO - LIVE Demo

---

Flask Dashboard Material - Free starter generated by App Generator.

flask-material-dashboard's Issues

Jinja2 inheritance ???

Thank you for the great work combining creative tim's templates with Jinja2.
I have a question regarding how you handle those templates. Why do you use embedded render_template functions in the return statements like

flask-material-dashboard/app/views.py

Line 79 in 3b9af39

content=render_template( 'pages/register.html', form=form, msg=msg) )

instead of using Jinja's inheritance function using the extend keyword in the templates?

Menu "active" status not switching

Hi - I notice that the development-server sidebar menus are not switching to "active" when a new page is selected - as the original template does ...

Select sidebar menus at ... https://demos.creative-tim.com/material-dashboard/examples/icons.html

and then at the flask admin panel to see this ...