I didn't really like the Flask starter projects I found searching the web. I really like Flask and I use it for quite a few projects so I decided to make a clean, readable, documented starter project. I didn't include any makefile or fabric as I feel it imposes a choice to the user of this project, I rather keep things simple (even though the word is subject to interpretation).
- User account sign up, sign in, password reset, all through asynchronous email confirmation.
- Form generation.
- Error handling.
- HTML macros and layout file.
- "Functional" file structure.
- Python 3.x compliant.
- Asynchronous AJAX calls.
- Application factory.
- Online administration.
- Static file bundling, automatic SCSS to CSS conversion and automatic minifying.
- Websockets (for example for live chatting)
- Virtual environment example.
- Heroku deployment example.
- Digital Ocean deployment example.
- Tests.
- Logging.
- Language selection.
If you have any suggestions or want to help, feel free to drop me a line at [email protected] or to create an issue.
- Flask, obviously.
- Flask-Login for the user accounts.
- Flask-SQLAlchemy interacting with the database.
- Flask-WTF and WTForms for the form handling.
- Flask-Mail for sending mails.
- itsdangerous for generating random tokens for the confirmation emails.
- Flask-Bcrypt for generating secret user passwords.
- Flask-Admin for building an administration interface.
- Semantic UI for the global style. Very similar to Bootstrap.
- Leaflet JS for the map. I only added for the sake of the example.
I did what most people recommend for the application's structure. Basically, everything is contained in the app/
folder.
- There you have the classic
static/
andtemplates/
folders. Thetemplates/
folder contains macros, error views and a common layout. - I added a
views/
folder to separate the user and the website logic, which could be extended to the the admin views. - The same goes for the
forms/
folder, as the project grows it will be useful to split the WTForms code into separate files. - The
models.py
script contains the SQLAlchemy code, for the while it only contains the logic for ausers
table. - The
toolbox/
folder is a personal choice, in it I keep all the other code the application will need.
-
Install the required libraries.
pip install -r requirements.txt
-
Create the database.
python createdb.py
-
Run the application.
python run.py
-
Navigate to
localhost:5000
.
pip install virtualenv
virtualenv venv
venv/bin/activate (venv\scripts\activate on Windows)
pip install -r requirements.txt
python createdb.py
python run.py
- Heroku
- Digital Ocean
The goal is to keep most of the application's configuration in a single file called config.py
. The one I have included is basic and yet it covers most of the important stuff.
I have included a working Gmail account to confirm user email addresses and reset user passwords, although in production you should't include the file if you push to GitHub because people can see it. The same goes for API keys, you should keep them secret. You can read more about secret configuration files here.
Read this for information on the possible configuration options.