~work in progress~
Flask-Batteries
An opinionated command line tool for bootstrapping Flask applications with less boiler-plate code.
Inspired by Ruby on Rails.
Installing
This has not been deployed to PYPI yet, as it is still under active development.
To install, clone the repo and install using pip
git clone git@github.com:graydenshand/flask_batteries.git
pip install ./flask_batteries # path to source code
Usage
Currently there are just two commands:
flask_batteries new <name>
flask_batteries destroy <name>
The new command creates a Flask app in a new directory with the specified name.
The destroy command will recursively erase a directory with the specified name. Be careful with this, as it will erase any directory you specify without checking to make sure it's actually a Flask-Batteries project.
Tests
Tests are run with tox against python 3.9.
From the root directory of the project, simply call:
tox
Roadmap
- Finish building the basic template. Add SQLAlchemy (Flask-SQLAlchemy) + Alembic (Flask-Migrate).
- Extend Flask's CLI with a set of commands for quickly generating and destroying assets. E.g.
flask g route loginmight generate a view function, map it to a url, generate a template, and generate a test. - Add an
installcommand for installing common flask extensions. - Add an
--apioption to thenewcommand to installFlask-RestfulandMarshmallowand generate a blueprint for API resources. - Add an
--spaoption to thenewcommand to set up a Node JS project and generate a "catch all" client blueprint for rendering a JS Single Page Application (SPA). Possibly integrate withcreate-react-appand/or Vue's hello world example. - Add a
--websocketoption to thenewcommand to installFlask-SocketIOand use its event loop instead of standard flask server. - Add a
--skip-dboption to thenewcommand to not install SQLAlchemy. - Implement a flexible uploads system that can be configured to work with multiple back ends
- ...and more
Metadata
Release files for flask-batteries 0.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| flask-batteries-0.0.0.tar.gz | 44.8 kB | Without provenance | Details for flask-batteries-0.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flask_batteries-0.0.0-py3-none-any.whl | Python 3 | none | any | Details for flask_batteries-0.0.0-py3-none-any.whl |
Total release size: 102.8 kB
Release files / flask-batteries-0.0.0.tar.gz
| Download URL | flask-batteries-0.0.0.tar.gz |
|---|---|
| Size | 44.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9229cb2388ab368c967a09ed6cca5be2fdd425958a76e2b19582073844121f81
|
|
BLAKE2b-256 checksum How to use checksums |
7ed3c494720d098fe5e9519a00edf92bf5f8e75532882651f97640fe3ae28c23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.5
|
Release files / flask_batteries-0.0.0-py3-none-any.whl
| Download URL | flask_batteries-0.0.0-py3-none-any.whl |
|---|---|
| Size | 58.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
91d5be178b576a6df01b1b16a2b54fc6c75508587e9ce897049a57be27211ad9
|
|
BLAKE2b-256 checksum How to use checksums |
a7bdf5b39768c629218ce10c4457c459cd744af4dcabe0acc803cef4678ee173
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.5
|
Security for flask-batteries 0.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.