Flask-MicroServices is a simple, lightweight attempt at bringing a self contained module hierarchy to Flask. Better project organization through isolation, or "microservices". These are not true microservices, but pantomime the idea of small, sectioned parts of a whole rather than a single large conglomerate.

An opinionated, but minimal approach to longterm project maintainability.

Those who use this plugin should be fully aware that it violates the Blueprint contract that many other plugins rely on to provide extended functionality to Flask. You should not use this plugin without first considering whether or not you plan to use plugins that rely on the default Blueprint behavior (e.g. Flask-Security).

• Django style route definitions
• Simple, modular, microservices inspired architecture
• Dynamic, overridable resolution of Static / Template directories

• Allow Blueprint defined template folders to override parent templates, rather than the other way around
• Allow Blueprint defined static folders to resolve from and override /static, rather than having to define individual /static_module_name folders
• Enable modular, but centralized definition of routes with a cleaner syntax so that you aren't forced to hunt for @app.route() decorators or use the arcane blueprint syntax in complex projects
• Allows drop in / drop out functionality of 'microservices' for testing, portability, and modularity

Flask-MicroServices is not exceptionally complex. In fact, it is quite small-- 200-ish lines of code, but it can bring a high level of reason to the way you write your Flask applications.

Check out the example project at ./example, or read below for a minimal example use-case.

• Project Layout
  • __init__.py
  • modules/
    • home/
      • static/
        • file.txt
      • templates/
        • main.html
      • __init__.py
      • urls.py
      • views.py

project_root/appname/__init__.py

You don't necessarily have to define your app within __init__.py, but this is how we will initialize our app for the purpose of this example.

from flask_microservices import MicroServicesApp

app = MicroServicesApp(__name__)

enabled_modules = [
    # Normally, we'd define more modules to enable:

    # 'home',
    # 'forum',
    # 'settings',

    # We will enable just one, for now:

    'admin'
]

# By default, this will assume your modules directory is "./modules" if a second argument is not provided.
app.register_urls(enabled_modules)
app.run()

project_root/appname/admin/__init__.py

This is the heart of every module, and is required for the app to be able to enable it.

from flask_microservices import Router
from . import urls

MODULE_NAME = 'admin'
IMPORT_NAME = __name__

# These blueprints are what is collected when you run app.register_urls()
blueprint = Router.create_blueprint(MODULE_NAME, IMPORT_NAME)
blueprint.register_urls(urls.urlpatterns)

project_root/appname/admin/urls.py

Your URL definitions for each module go here. Routes defined here follow all the normal patterns of @app.route(), with the exception of endpoint being renamed to name, and the order of view_func and name being reversed.

When a name is provided here, as with a normal blueprint it will become namespaced. A value of name='home' will become resolveable with url_for('admin.home').

from flask_microservices import url
from . import views

urlpatterns = [
    url('/admin/', view_func=views.admin_panel, name='home'),

    ## Example URLs:

    ### Minimal:
    # url('/admin/simple/', view_func=views.admin_simple)

    ### Advanced
    # url('/admin/roles/add/', view_func=views.admin_panel_roles_add, name='role_add', methods=['GET', 'POST']),
    # url('/admin/roles/edit/', view_func=views.admin_panel_roles_edit, name='role_edit', methods=['GET', 'POST']),
]

project_root/appname/admin/views.py

This is where your views are defined. As your project scales farther, you may want to separate your logic into files such as a.py, b.py, and import them into your views.py with from . import a, b in order to make them visible to urls.py.

from flask import render_template
from ExampleApp.ExampleWrappers import admin_access_required

@admin_access_required
def admin_panel():
    return render_template('admin/main.html')

project_root/appname/admin/templates/admin/main.html

Templates folder resolves as normal. The MicroServicesApp instance will check all module template directories before trying to resolve from the root template folder. An important caveat to this approach is to remember that when two modules both possess conflicting templates, they will be resolved in the order that they were defined in the enabled_modules value that you passed to app.register_urls().

<html>
  <h1> Holy cow! </h1>
  <p> If the router was unable to find this file, then it would try your root level templates folder at `project_root/appname/templates/admin/main.html` before failing.</p>
</html>

project_root/appname/admin/static/file.txt

Static folder resolves as normal. The MicroServicesApp instance will behave with respect to static files in an identical manner to how it handles template files. See above for caveats.

I am a file! If I could not be found, the Router would attempt to find `project_root/appname/static/file.txt` before 404'ing.

• Breaks the 'EXPLAIN_TEMPLATE_LOADING' flask configuration setting.