{"id":1260,"date":"2023-08-16T21:30:43","date_gmt":"2023-08-16T16:00:43","guid":{"rendered":"https:\/\/geekpython.in\/?p=1260"},"modified":"2024-03-01T17:08:45","modified_gmt":"2024-03-01T11:38:45","slug":"structure-flask-app-with-blueprint","status":"publish","type":"post","link":"https:\/\/geekpython.in\/structure-flask-app-with-blueprint","title":{"rendered":"Structuring Flask App with Blueprint – How to Use"},"content":{"rendered":"\n
Introduction<\/h1>\n\n\n\n
Large applications can become complex and difficult to manage due to the presence of numerous components and intricate structures.<\/p>\n\n\n\n
Flask blueprints help in organizing large applications into smaller, manageable components, leading to enhanced maintainability of the application.<\/p>\n\n\n\n
Blueprints can contain views, templates, and static files for various components, similar to the structure of a typical Flask application. These blueprints can be registered with the Flask app to integrate them into the application.<\/p>\n\n\n\n
Flask App Structure<\/h1>\n\n\n\n
If you’ve used the Flask framework before, you might structure your Flask application as follows:<\/p>\n\n\n\n
In smaller projects, defining views within the main file may not pose a significant problem. However, in more complex projects, when you need to create routes for various components such as user management, admin functions, profiles, voting, and more, organizing these routes within a single file can become challenging. This can lead to poor code maintainability and make the project harder to manage.<\/p>\n\n\n\n
This is precisely where blueprints prove valuable, as they allow you to structure your application into smaller components, enhancing maintainability.<\/p>\n\n\n\n
Creating the Blueprint<\/h1>\n\n\n\n
Add the following code to a new Python file at the root level, blueprint.py<\/code>.<\/p>\n\n\n\n
The code imports the Blueprint<\/code> class from the flask<\/code> which will help in defining the routes.<\/p>\n\n\n\n
The instance of the Blueprint<\/code> is created by calling Blueprint(\"blueprint\", __name__)<\/code> and passed in two arguments, first, \"blueprint\"<\/code>, is the Blueprint’s name, and the second, __name__<\/code>, is the Blueprint’s import name. After that, the instance is saved in the bp<\/code> variable.<\/p>\n\n\n\n
The routes are defined using the Blueprint instance (bp<\/code>) in a similar manner to how routes are defined using the Flask application instance (app<\/code>).<\/p>\n\n\n\n
The @bp.route()<\/code> decorators are used to associate URL routes with the view functions defined within the blueprint. The home()<\/code> function is associated with the root URL (\"\/\"<\/code>), and the user_info()<\/code> function is associated with the \"\/user\"<\/code> URL.<\/p>\n\n\n\n
Registering the Blueprint<\/h1>\n\n\n\n
A blueprint is similar to a Flask app, but it is not an app, instead, the blueprint must be registered within the Flask app to extend its functionality.<\/p>\n\n\n\n
Navigate to the main Flask app created in the app.py<\/code> Python file and register the above-created blueprint.<\/p>\n\n\n\n
The code imports the Blueprint instance, bp<\/code>, from the blueprint<\/code> module (blueprint.py<\/code>), and this import includes all of the blueprint’s routes and views.<\/p>\n\n\n\n
The register_blueprint()<\/code> method is then used to register the blueprint instance (bp<\/code>) with the Flask app instance (app<\/code>).<\/p>\n\n\n\n
If you run the app, you can access the routes defined within the blueprint.<\/p>\n\n\n\n
Mounting Blueprints at Different Locations<\/h1>\n\n\n\n
Blueprints can be attached to a certain URL path that can be prefixed with all of the routes defined within the blueprint.<\/p>\n\n\n\n
You can make this happen by using the url_prefix<\/code> parameter while registering the blueprint using the register_blueprint()<\/code> method in the Flask app.<\/p>\n\n\n\n
The url_prefix<\/code> is now \"\/demo\"<\/code>. This means that the routes within the blueprint (\"\/\"<\/code> and \"\/user\"<\/code>) can be accessed by adding \"\/demo\"<\/code> at the beginning of their URL paths.<\/p>\n\n\n\n
The complete URL of the (\"\/\"<\/code>) route is changed to \"\/demo\/\"<\/code> for the home()<\/code> function. Also, the complete URL of the \"\/user\"<\/code> route will now be \"\/demo\/user\"<\/code> for the user_info()<\/code> function.<\/p>\n\n\n\n
You can set the url_prefix<\/code> while making the Blueprint instance. The Blueprint class offers a url_prefix<\/code> parameter, and the provided code example demonstrates its usage.<\/p>\n\n\n\n
The URL path for the (\"\/\"<\/code>) route will become \"\/sample\/\"<\/code>. Likewise, the URL path for the \"\/user\"<\/code> route will change to \"\/sample\/user\"<\/code>.<\/p>\n\n\n\n
Note:<\/strong> If you set the url_prefix<\/code> parameter inside the blueprint, avoid setting it again during the blueprint registration. Doing so will overwrite the blueprint’s URL prefix.<\/p>\n\n\n\n
\n
Caution:<\/p>\n\n\n\n
If you set url_prefix in the blueprint and then set it again while registering the blueprint within the app, the latter will overwrite the former.<\/p>\n<\/blockquote>\n\n\n\n
Templates and Static Folders<\/h1>\n\n\n\n
You have several options for organizing your app using blueprints.<\/p>\n\n\n\n
If your project’s structure aligns with the example above, you’ll have to indicate the locations of templates<\/strong> and static<\/strong> folders within your Blueprint<\/code>.<\/p>\n\n\n\n
The Blueprint<\/code> class gives you parameters, templates_folder<\/code> and static_folder<\/code>, which allow you to define the exact path (either absolute or relative) to the blueprint’s templates<\/strong> and static<\/strong> folder when creating an instance of the Blueprint<\/code> class.<\/p>\n\n\n\n
Both \"admin_bp\"<\/code> and \"user_bp\"<\/code> blueprints have their own directories for templates and static files. This separation ensures that their respective templates and assets are kept separate from other parts of the app, maintaining isolation and organization.<\/p>\n\n\n\n
Avoid Template Name Clashes<\/h1>\n\n\n\n
When you’re designing blueprints for different parts of your application, the arrangement of your project holds significance. For instance, referring to the layout mentioned above, duplicating HTML filenames in the admin\/templates<\/code> and user\/templates<\/code> directories can lead to a name clash.<\/p>\n\n\n\n
The Flask application searches for templates in the \"templates\"<\/code> directory. If there are duplicate template file paths across different blueprints, the one that takes precedence depends on the order of blueprint registration. The one registered later will override the earlier one.<\/p>\n\n\n\n
To avoid potential issues, you can shape the project layout in the following manner:<\/p>\n\n\n\n
Alternatively, you can assign distinct names to the templates.<\/p>\n\n\n\n
Template Routing with Blueprints<\/h1>\n\n\n\n
Template routing with blueprints is distinct from the conventional approach. It involves a specific format where the blueprint name is added as a prefix to the associated view function.<\/p>\n\n\n\n
As an example, if your blueprint is named admin_blueprint<\/code> and includes a view function named home()<\/code>, then the format becomes admin_blueprint.home<\/code>.<\/p>\n\n\n\n
The link mentioned above points to the route connected with the home()<\/code> function in the user_blueprint<\/code>. The url_for()<\/code> function dynamically produces a URL for the user_blueprint.home<\/code> route.<\/p>\n\n\n\n
Likewise, the situation is identical to the link mentioned earlier. It leads to the route linked with the home()<\/code> function in the admin_blueprint<\/code>. The url_for()<\/code> function dynamically generates a URL for the admin_blueprint.home<\/code> route.<\/p>\n\n\n\n
Including CSS Files with Blueprints: Creating URLs for Static Assets<\/strong><\/h1>\n\n\n\n
The procedure is quite similar to what you did with templates. To include CSS files within the HTML template, you should construct a URL that directs to the CSS file situated in the specified static folder of the blueprint.<\/p>\n\n\n\n
As an example, the method to link the \"style.css\"<\/code> file found in the static<\/code> directory of the \"admin_blueprint\"<\/code> blueprint would be url_for('admin_blueprint.static', filename='style.css')<\/code>.<\/p>\n\n\n\n
Note: You must indicate the directory path where static files (CSS, JavaScript, images, etc.) are situated for this blueprint. This is achieved using the static_folder<\/code> parameter.<\/p>\n\n\n\n
This HTML code snippet above uses the url_for()<\/code> function to generate a URL that points to the “style.css”<\/strong> static file linked to the admin_blueprint<\/code>.<\/p>\n\n\n\n
Custom URL Path for Static Files<\/h1>\n\n\n\n
Flask Blueprint<\/code> provides a static_url_path<\/code> parameter that provides flexibility to define a custom URL prefix for the static files (CSS, JavaScript, images, etc.) associated with the Blueprint<\/code>.<\/p>\n\n\n\n
The static_url_path<\/code> is set as \"admin\"<\/code>, effectively making the static files within the admin_blueprint<\/code> accessible under the admin\/<\/code> URL path.<\/p>\n\n\n\n
Now you can directly include static files (CSS, JavaScript, images, etc) by specifying the static URL path.<\/p>\n\n\n\n
Including Static Files using Static URL Path<\/h2>\n\n\n\n
The complete webpage would look like the image shown below:<\/p>\n\n\n\n<\/figure>\n\n\n\n
Conclusion<\/h1>\n\n\n\n
A Flask Blueprint is used as an extension for a Flask app, and it serves the purpose of organizing large and complex applications into smaller, more manageable components.<\/p>\n\n\n\n
Let’s recall what you’ve seen in this tutorial:<\/p>\n\n\n\n
\n
What is Blueprint in Flask<\/li>\n\n\n\n
Creating and Registering a Blueprint<\/li>\n\n\n\n
Template routing with Blueprint<\/li>\n\n\n\n
Including static files with Blueprint<\/li>\n\n\n\n
Custom URL path for static assets<\/li>\n<\/ul>\n\n\n\n
![\"Flask](\"https:\/\/geekpython.in\/wp-content\/uploads\/2023\/08\/image.png\")
<\/figure>\n\n\n\n