Material Dashboard Flask
Material Dashboard Flask is a free Bootstrap 4 Admin Template for Flask - Features:
- UI Kit: Material Dashboard (Free Version)
- Codebase - provided by AppSeed
- SQLite, PostgreSQL, SQLAlchemy ORM
- Alembic (DB schema migrations)
- Modular design with Blueprints
- Session-Based authentication (via flask_login)
- Forms validation
- Deployment scripts: Docker, Gunicorn / Nginx, Heroku
Links
- Material Dashboard Flask - product page
- Material Dashboard Flask Demo - LIVE App, default login credentials ** test / pass **
- Material Dashboard Flask Sources - MIT License, released on Github
- Tutorials
What is Flask
Flask is a lightweight WSGI web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications. Classified as a microframework, Flask is written in Python and it does not require particular tools or libraries. It has no database abstraction layer, form validation, or any other components where pre-existing third-party libraries provide common functions.
Flask Links
- Flask - the official website
- Flask Documentation
Environment
To use the stater, Python3 should be installed properly in the workstation. If you are not sure if Python is properly installed, please open a terminal and type python --version
. The full-list with dependencies and tools required to build the app:
- Python3 - the programming language used to code the app
- GIT - used to clone the source code from the Github repository
- Basic development tools (g++ compiler, python development libraries ..etc) used by Python to compile the app dependencies in your environment.
Check Python version (using the terminal)
Check GIT command tool (using the terminal)
For more information on how to set up your environment please access the resources listed below. In case we’ve missed something, contact us on Discord.
Build the app
To built and start the app locally, follow the steps:
Get the source code
- Download the ZIP from Github Repository
- Using GIT tool in the terminal to clone the source code
Change the current directory to
source code
directory
At this point, we can visit the app in the browser http://127.0.0.1:5000/
.
By default, the app will redirect guest users to the login page. To access the private pages:
- Create a new user using the registration page
- Authenticate using the login page
App Codebase (simplified)
Starter uses a simple codebase (no Blueprints) with a structure presented bellow:
The bootstrap flow
run.py
loads the.env
file- Initialize the app using the specified profile: Debug or Production
- If env.DEBUG is set to True the SQLite storage is used
- If env.DEBUG is set to False the specified DB driver is used (MySql, PostgreSQL)
- Call the app factory method
create_app
defined in app/init.py - Redirect the guest users to Login page
- Unlock the pages served by home blueprint for authenticated users
.env
(saved in the root of the project)
run.py
(simplified version)
# File: run.py
DEBUG = config('DEBUG', default=True)
# Create the WSGI app, using the app factory pattern
app = create_app( app_config )
# Migrate automaticaly the app using Flask Migrate library
Migrate(app, db)
app/__init__.py
(simplified version)
# File: app/__init__.py
db = SQLAlchemy() # Invoke SQLAlchemy
login_manager = LoginManager() # Invoke Login Manager
def register_extensions(app):
db.init_app(app) # Inject SQLAlchemy magic
login_manager.init_app(app) # Add Login Manager to the app
# Register app blueprints: `base`, `home`
def register_blueprints(app):
for module_name in ('base', 'home'):
module = import_module('app.{}.routes'.format(module_name))
app.register_blueprint(module.blueprint)
# Create the tables (automaticaly)
def configure_database(app):
@app.before_first_request
def initialize_database():
db.create_all()
# Create the WSGI app using the factory pattern
def create_app(config):
app = Flask(__name__, static_folder='base/static')
app.config.from_object(config)
register_extensions(app)
register_blueprints(app)
configure_database(app)
return app
The app/__init__.py
constructs the app by putting together a short-list of things:
- Invoke SQLAlchemy
- Invoke and inject the
Login Manager
into the app - Load the configuration from
config.py
file - Register the app blueprints
- Check if the database tables are created
- return the WSGI app
App Codebase
The starter defines two blueprints:
- Base blueprint - handles the authentication (routes and forms) and assets management
- Home blueprint - serve HTML pages for authenticated users
App / Base Blueprint structure
App / Home Blueprint structure
App Configuration
The configuration file config.py
(in the root of the project) define a dual configuration controlled via the .env
file ( DEBUG
variable)
DebugConfig - default configuration used for development
This configuration becomes active if .env
file has the DEBUG
file set to True
# Development/Debug configuration
# Set up the App SECRET_KEY
SECRET_KEY = config('SECRET_KEY', default='S#perS3crEt_007')
# This will create a file in <app> FOLDER
SQLALCHEMY_DATABASE_URI = 'sqlite:///' + os.path.join(basedir, 'db.sqlite3')
SQLALCHEMY_TRACK_MODIFICATIONS = False
During the first request, the SQLite database and tables are automatically created in the root in the project.
Hint: to visualize the SQLite database content an external tool should be installed: DB Browser for SQLite it might be a good choice.
ProductionConfig - production configuration
This configuration becomes active if .env
file has the DEBUG
file set to False
# Production configuration
SESSION_COOKIE_HTTPONLY = True
REMEMBER_COOKIE_HTTPONLY = True
REMEMBER_COOKIE_DURATION = 3600
# PostgreSQL database
SQLALCHEMY_DATABASE_URI = '{}://{}:{}@{}:{}/{}'.format(
config( 'DB_ENGINE' , default='postgresql' ),
config( 'DB_USERNAME' , default='appseed' ),
config( 'DB_PASS' , default='pass' ),
config( 'DB_HOST' , default='localhost' ),
config( 'DB_PORT' , default=5432 ),
config( 'DB_NAME' , default='appseed-flask' )
)
In this configuration profile, the database defaults to a PostgreSQL DBMS. Make sure the .env
has the right credentials to access the database.
App Tables
The file app/base/models.py
(Base Blueprint) defines the table(s) used by the application. Being a simple starter, by default the following tabes are defined:
- Table #1 - User with fields:
- Id - Primary key, unique
- user - Store the username
- email - The email address
- password - Hashed password
App Forms
The file app/base/forms.py
(Base Blueprint) defines the table(s) used by the application. Being a simple starter, by default the following forms are defined:
- Form #1 - LoginForm with fields:
- username
- password
- Form #2 - RegisterForm with fields:
- username - used to authenticate
- email - email address
- password - used to authenticate
App Routing
The routing rules are defined by Base and Home blueprints as specified below. This is the public zone of the app.
Base Blueprint - routing file
app/base/routes.py
/login
route is resolved bylogin()
method/register
route is resolved byregister()
method/logout
route calls thelogout_user()
defined in flask_login
Registered ERROR handlers
- 404 Error - Page not found
- 403 Error - Access Forbidden
- 500 Error - Internal Error
Home Blueprint - routing file
app/home/routes.py
This blueprint will serve requested pages from app/home/templates
directory to authenticated users.
The authentication status is checked by @login_required
decorator.
/<template>
route resolved byroute_template()
.- If a requested page is not found a default 404 page is returned to the user
Pages & Assets
Pages and all assets defined in the UI Kits are served by the app using both blueprints:
- Home Blueprint manage the static assets -
app/base/static/assets
-
Home Blueprint store the layout
master pages
, HTML chunks (footer. header, scripts) andlogin, registration
pages - Base Blueprint serve the HTML pages (index, page-404, etc) and the rest of the pages defined in the UI kit.
Data Structures
The Flask starter exposes a short-list with data structures used globally across the app:
current_user
object
Constructed by Flask-Login can be used to detect if the current request is executed by an authenticated user or not. The object has global visibility and can be used in all app controllers and handlers but also in views.
How it works
app/base/models.py
define the callback functions required by Flask-Login library:
# File: app/base/models.py
@login_manager.user_loader
def user_loader(id):
return User.query.filter_by(id=id).first()
@login_manager.request_loader
def request_loader(request):
username = request.form.get('username')
user = User.query.filter_by(username=username).first()
return user if user else None
Usage in contoler (Sample file)
def sample_method(path):
# Redirect guests users to login page
if not current_user.is_authenticated:
return redirect(url_for('login'))
Usage in view
<div class="collapse navbar-collapse" id="navigation">
<ul class="navbar-nav ml-auto">
<!-- The Usage of <current_user> object -->
<!-- Html chunk rendered for guests users-->
<li class="nav-item ">
<a href="" class="nav-link">
<i class="tim-icons icon-laptop"></i> Register
</a>
</li>
<li class="nav-item ">
<a href="" class="nav-link">
<i class="tim-icons icon-single-02"></i> Login
</a>
</li>
</ul>
</div>
Flask resources
- Flask - the official website
- Flask Templates - index provided by Creative-Tim