🚢 inboard 🐳
Docker images and utilities to power your Python APIs and help you ship faster.
Description
This project provides Docker images and a PyPI package with useful utilities for Python web servers. It runs Gunicorn with (or without) Uvicorn, and can be used to build applications with Starlette and FastAPI.
Justification
Why use this project? You might want to try out inboard because it:
- Offers a Python package and Docker images that work together. Python packages and Docker images don't automatically share the same versioning systems, but inboard can help with this. You might install the Python package with a minor version constraint. You can also pull the corresponding Docker image by specifying the minor version in the Docker tag (
FROM ghcr.io/br3ndonland/inboard:<version>). - Tests everything. inboard performs unit testing of 100% of the Python code, and also runs smoke tests of the Docker images each time they are built.
- Sets sane defaults, but allows configuration. Configure a variety of settings with environment variables. Or run it as-is and it just works.
- Configures logging extensibly. inboard simplifies logging by handling all its Python log streams with a single logging config. It also offers the ability to filter health check endpoints out of the access logs. Don't like it? No problem. You can easily extend or override the logging behavior.
Quickstart
Get started with Docker, pull and run an image, and try an API endpoint.
docker pull ghcr.io/br3ndonland/inboard
docker run -d -p 80:80 --platform linux/amd64 ghcr.io/br3ndonland/inboard
curl -s http://localhost:80 | jq
Documentation
Documentation is built with Zensical, deployed to Vercel using the Vercel project configuration in vercel.json, and available at inboard.bws.bio and inboard.vercel.app.
Background
I built this project to use as a production Python web server layer. I was working on several different software applications, and wanted a way to centrally manage the web server layer, so I didn't have to configure the server separately for each application. I also found it difficult to keep up with all the changes to the associated Python packages, including Uvicorn, Starlette, and FastAPI. I realized that I needed to abstract the web server layer into a separate project, so that when working on software applications, I could simply focus on building the applications themselves. This project is the result. It's been very helpful to me, and I hope it's helpful to you also.
This project was inspired in part by tiangolo/uvicorn-gunicorn-docker. In addition to the benefits described in the justification section, inboard also has the following advantages:
- One repo. The tiangolo/uvicorn-gunicorn images are in at least three separate repos (tiangolo/uvicorn-gunicorn-docker, tiangolo/uvicorn-gunicorn-fastapi-docker, and tiangolo/uvicorn-gunicorn-starlette-docker), with large amounts of code duplication, making maintenance difficult for an already-busy maintainer. This repo combines three into one.
- One Dockerfile. This project leverages multi-stage builds to produce multiple Docker images from one Dockerfile.
- One Python requirements file. This project uses Hatch for dependency management with a single pyproject.toml.
- One logging configuration. Logging a Uvicorn+Gunicorn+Starlette/FastAPI stack is unnecessarily complicated. Uvicorn and Gunicorn use different logging configurations, and it can be difficult to unify the log streams. In this repo, Uvicorn, Gunicorn, and FastAPI log streams are propagated to the root logger, and handled by the custom root logging config. Developers can also supply their own custom logging configurations.
- One programming language. Pure Python with no shell scripts.
- One platform. You're already on GitHub. Why not pull Docker images from GitHub Container Registry?
The PyPI package is useful if you want to use or extend any of the inboard Python modules, such as the logging configuration.
1 maintainer
Metadata
1 maintainer
Release files for inboard 0.99.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 | |
|---|---|---|---|
| inboard-0.99.0.tar.gz | 17.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inboard-0.99.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 37.1 kB
Release files / inboard-0.99.0.tar.gz
| Download URL | inboard-0.99.0.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
177701cbea2532b2128043887c1bf68e15faba3e03c5dd80d444f501c1158df7
|
|
BLAKE2b-256 checksum How to use checksums |
c3a09c596f1e4ea5dd846123dde834324e48e14a2416e74b8a9f828aed0d3f44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 11, 2026.
Transparency logRelease files / inboard-0.99.0-py3-none-any.whl
| Download URL | inboard-0.99.0-py3-none-any.whl |
|---|---|
| Size | 19.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
948e26c0746711aa71520db6ba124c6bc24677f0f5e2e6c0e738ead2c4d36176
|
|
BLAKE2b-256 checksum How to use checksums |
f24fdf80e1294041b94fe7541745ca3774f466ba06f060fa28e63092b8676043
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 11, 2026.
Transparency log
