Production overview

Dependencies

The core install is what every Feather app uses: Flask, Flask-SQLAlchemy, Flask-Migrate, Flask-Login, Flask-WTF, Werkzeug, SQLAlchemy, Alembic, Authlib, Requests, Jinja2 and urllib3. Everything else is an extra, so an app that renders no PDFs installs no PDF renderer.

Extra	Brings	Enable it when
`postgres`	psycopg2-binary, psycopg 3	`DATABASE_URL` is a `postgresql://` or `postgresql+psycopg://` URL
`redis`	redis, rq	`CACHE_BACKEND=redis` or `JOB_BACKEND=rq`, or `REDIS_URL` is set and those two are not
`email`	resend	Sending transactional email
`s3`	boto3	`STORAGE_BACKEND=s3`, or `S3_BUCKET` is set
`gcs`	google-cloud-storage	`STORAGE_BACKEND=gcs`
`pdf`	WeasyPrint	Generating PDFs
`ratelimit`	flask-limiter	Rate limiting across workers, for auth apps
`prod`	gunicorn	Running `feather start` or the Docker web process
`test`	pytest, pytest-cov	Running the app’s own tests
`all`	all of the above	Everything, when you’d rather not choose

pip install "feather-framework[postgres,redis,prod,test]"

feather new writes a requirements.txt naming the extras your answers enabled, so this is usually handled for you. feather --version and feather security-check report which extras are installed.

Importing a feature whose extra is missing raises an error naming the install command to run, rather than an import traceback.

Frontend libraries

Bundled through npm rather than a CDN: HTMX, Idiomorph, Apache ECharts. Loaded from Google: Google Fonts and Material Icons.

DEBUG mode behaviour

Setting	Asset loading	Description
`DEBUG=True`	Vite dev server on `localhost:5173`	Hot reload, no build needed
`DEBUG=False`	Built assets from `static/dist/`	Requires `feather build` first

Unstyled pages in production happen when DEBUG=False but feather build was never run, or when static/dist/ is stale. Run feather build before deploying.

Configuration shorthand

FLASK_CONFIG accepts shorthand names. These are equivalent:

FLASK_CONFIG=production
FLASK_CONFIG=ProductionConfig
FLASK_CONFIG=prod

Supported: development and dev, production and prod, testing and test.

Deploy to Appentic

Push from GitHub. Postgres, Redis and the worker run beside the app, with no server to manage.

Deploy with Docker

Eight files, one machine, Caddy in front.

Full configuration reference

Every key Feather reads, with its default.

Get started

Tutorial: build a Kanban app

Building the UI

Backend

Features

Tooling

Testing

Deployment

Production overview

Dependencies

Frontend libraries

DEBUG mode behaviour

Configuration shorthand

Deploy to Appentic

Deploy with Docker

Full configuration reference

​Dependencies

​Frontend libraries

​DEBUG mode behaviour

​Configuration shorthand

Deploy to Appentic

Deploy with Docker

Full configuration reference

Dependencies

Frontend libraries

DEBUG mode behaviour

Configuration shorthand