Flask-bigapp

Change in the way `flask-imp init` works. When run on its own without any arguments, it will ask you what level of app you want to generate.

Build tool move to flit
Lint tool move to ruff

New minimal init option

`flask-imp init --minimal`:

text
app/
├── extensions
│ └── __init__.py
│
├── global
│ ├── static
│ │ ├── css
│ │ │ └── water.css
│ │ ├── img
│ │ │ └── flask-imp-logo.png
│ │ └── favicon.ico
│ ├── templates
│ │ └── index.html
│ └── routes.py
│
├── __init__.py
└── default.config.toml


Generates a Flask-Imp app with no blueprints.

New init slim app.

`flask-imp init -n app --slim`


app/
├── extensions
│ └── __init__.py
│
├── global
│ ├── cli
│ │ └── cli.py
│ ├── error_handlers
│ │ └── error_handlers.py
│ ├── static
│ │ └── favicon.ico
│ └── templates
│ └── errors
│ ├── 400.html
│ ├── 401.html
│ ├── 403.html
│ ├── 404.html
│ ├── 405.html
│ └── 500.html
│
├── www
│ ├── config.toml
│ ├── __init__.py
│ ├── routes
│ │ └── index.py
│ ├── static
│ │ ├── css
│ │ │ └── water.css
│ │ ├── img
│ │ │ └── flask-imp-logo.png
│ │ └── js
│ │ └── main.js
│ └── templates
│ └── www
│ ├── extends
│ │ └── main.html
│ ├── includes
│ │ ├── footer.html
│ │ └── header.html
│ └── index.html
│
├── __init__.py
└── default.config.toml


This deploys a Flask app with only one blueprint, and no models.

This release also sees a new blueprint file structure, seen above.

Improved CLI command project deployments.

`flask-imp init`

`flask-imp blueprint`

Updates to the generated config file.

Blueprints now have a new section to their config files, DATABASE_BIND


[DATABASE_BIND]
ENABLED = true
DIALECT = "sqlite"
DATABASE_NAME = "www"
LOCATION = ""
PORT = ""
USERNAME = ""
PASSWORD = ""



This allows each blueprint to be shipped or stored with a connection to its own database.
Changes to the way blueprints are registered in this change. The blueprints no longer try and find the imp instance, partials are created instead, then ran later to inject the imp instance.