bafser
A synchronous Flask and SQLAlchemy foundation for small applications and services: typed JSON schemas, JWT authentication, permissions, audit logs, model helpers, transaction-aware files, a bounded request dashboard and a project generator. Python 3.10 or newer.
Start a small project
Install bafser in your Python environment, then run:
bafser init_project
The first invocation creates bafser_config.py if it is missing. Edit that file,
then rerun the generator and answer n when it asks whether you want to change
the ready configuration. Existing files are preserved unless --force is
supplied. --directory PATH selects the project directory.
For a small SQLite prototype, set use_alembic = False in the generated config:
bafser init_project
python main.py dev
The generated one-process entry point can prepare its database and storage at
startup with AUTO_SETUP=True. DEV_MODE=True enables full diagnostic logging.
For a migration-managed application, create the initial revision before starting
it; see the guide.
Production
Use AUTO_SETUP=False for normal web/worker startup and perform setup explicitly:
python main.py --setup
Enable MULTIPROCESS_LOGGING=True when processes share log files. Keep persistent
storage and keys outside replaceable release directories. Server logs retain
messages and full exceptions by default; LOG_ERROR_DETAILS=False selects
reduced production diagnostics. Per-route RequestPolicy controls body limits
and HTTP data logging; production bodies and queries are omitted by default.
See deployment and security for keys, migrations, JWT validation, proxy configuration, database pools and backups.
Documentation
- Guide and API contracts: quick start,
Undefined, schemas, transactions, authentication, files and deployment. - Agent notes: short reminders for code-generating agents.
Dependency bounds and package metadata are maintained in pyproject.toml. The library keeps a small-project workflow; production requirements are configured explicitly by the application.
Metadata
Release files for bafser 2.18.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 |
|---|---|---|---|---|
| bafser-2.18.0.tar.gz | 96.3 kB | With provenance | Details for bafser-2.18.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bafser-2.18.0-py3-none-any.whl | Python 3 | none | any | Details for bafser-2.18.0-py3-none-any.whl |
Total release size: 219.3 kB
Release files / bafser-2.18.0.tar.gz
| Download URL | bafser-2.18.0.tar.gz |
|---|---|
| Size | 96.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47a79d1c91e4b389703adc25b77cc953bfbefb5bef56456fd54463dda5b824fe
|
|
BLAKE2b-256 checksum How to use checksums |
3ba085f3e824aa812f4d2a2e7c4d9527040e4d0578ec101816fa5b0a1336b355
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logRelease files / bafser-2.18.0-py3-none-any.whl
| Download URL | bafser-2.18.0-py3-none-any.whl |
|---|---|
| Size | 122.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ac00598844706de009e248dd7b41273ff336b88acb5a10f6e129833f5373705
|
|
BLAKE2b-256 checksum How to use checksums |
8200fe54e9630fa05ae9a5f3eff2f533e53110642fcf071ab1d5e7be99a6042f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logSecurity for bafser 2.18.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for bafser-2.18.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logA 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.