Flask Boilerplate utilizando Semantic-UI, docker, nginx y gunicorn

Max Halford 1f7592f6e8 - Corrected the port details 10 năm trước cách đây
app 1f7592f6e8 - Corrected the port details 10 năm trước cách đây
screenshots ede0ceb2c8 Init 10 năm trước cách đây
.gitignore e8697f71e0 Updated .gitignore 10 năm trước cách đây
README.md 640e772531 Updated todo list 10 năm trước cách đây
config.py 1f7592f6e8 - Corrected the port details 10 năm trước cách đây
createdb.py ede0ceb2c8 Init 10 năm trước cách đây
requirements.txt ede0ceb2c8 Init 10 năm trước cách đây
run.py ede0ceb2c8 Init 10 năm trước cách đây

README.md

Flask boilerplate code

License

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).

Features

  • User account sign up, sign in, password reset, all through email confirmation.
  • Form generation.
  • Error handling.
  • HTML macros.
  • HTML layout file.
  • "Functional" file structure.
  • Python 3.x compliant.
  • Application factory.
  • Flask admin.
  • Static file bundling, automatic SCSS to CSS conversion and automatic minifying.
  • Websockets (for example for live chatting)
  • Virtual environment.
  • Easy Heroky deployment.
  • Easy Digital Ocean deployment.
  • Tests.
  • Logging.

If you have any suggestions or want to help, feel free to drop me a line at maxhalford25@gmail.com or to create an issue.

Libraries

Backend

Frontend

Structure

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/ and templates/ folders. The templates/ 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 a users table.
  • The toolbox/ folder is a personal choice, in it I keep all the other code the application will need.

Setup

Vanilla

  • 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.

Virtual environment

To do.

Configuration

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.

Deploy

To do.

Examples

Inspiration

Other possibilities