CRUD Admin Starter (Container Edition)

Engineering & Development

A database admin back-office example built on a Python web framework: create, list, edit and delete screens for a Contacts table and a Groups table, backed by PostgreSQL and brought up with Docker Compose on your own machine. Derived from a frozen snapshot of an open-source project under the BSD-3-Clause licence; the delivery includes an orchestration file (database image fixed by digest, port bound to 127.0.0.1), a script that generates the passwords and secret, and a quick-start guide.

Subscribe & download See how to start

SubscriptionUS$49 per month

Last run2026-11-12

In practice

Readiness3 / 5

What you need

Few changes needed4 / 5

Who it is for

Developers and small teams who want to see quickly what a table-plus-login admin back office looks like, for evaluation or learning.

How to start

$ sh scripts/quickstart/init-env.sh
$ docker compose up -d --build

Browse the files

Files in the product repository at the pinned commit. A few house files are left out of the zip.

File overview850 paths

▸babel2

babel.cfg
messages.pot

▸bin11

babel_extract.sh
babel_init.sh
bootswatch_update.sh
config.py
db_create.py
db_migrate.py
db_upgrade.py
hash_db_password.py
migrate_db_0.7.py
migrate_db_1.3.py
…

▸docker4

openldap/
web/

▸docs67

Makefile
_static/
_templates/
_themes/
actions.rst
addons.rst
advanced.rst
api.rst
breaking.rst
cli.rst
…

▸examples407

README.rst
base_api/
base_filters/
basefilter/
composite_keys/
crud_rest_api/
employees/
enums/
extendsecurity/
extendsecurity2/
…

▸flask_appbuilder243

__init__.py
_compat.py
actions.py
api/
babel/
base.py
basemanager.py
baseviews.py
charts/
cli.py
…

▸images23

ListThumbnail.png
chart.png
chart_time1.png
chart_time2.png
charts.png
contact_list.png
contacts.png
direct_chart.png
fab.png
group_list.png
…

▸requirements11

base.in
base.txt
base_legacy.txt
dev.in
dev.txt
docs.in
docs.txt
extra.in
extra.txt
tests.in
…

▸requirements-fe2

package-lock.json
package.json

▸scripts5

babel_extract.sh
babel_init.sh
copy_fe_dependencies.sh
create_release.py
quickstart/

▸tests46

__init__.py
base.py
config_api.py
config_oauth.py
config_security.py
config_security_api.py
config_security_cli.py
const.py
data/
fixtures/
…

▫ATTRIBUTION.md

▫CHANGELOG.rst

▫CONTRIBUTING.rst

▫Dockerfile

▫LICENSE

▫MANIFEST.in

▫PRODUCT.md

▫QUICKSTART.md

▫README.rst

▫RELEASE.rst

▫SECURITY.md

▫delivery-manifest.txt

▫docker-compose.yml

▫release.sh

▫setup.cfg

▫setup.py

▫tox.ini

▫Config and hidden files 12

Latest passing run

Clone → Checkout → Toolchain → Admin up and serves

Pre-purchase Disclosure

What you are buying

A database admin back-office example: create, list, edit and delete screens for a Contacts table and a Groups table, behind a sign-in, backed by PostgreSQL and brought up with Docker Compose on your own machine.

Derived from an open-source project under the BSD-3-Clause licence, and not the original project itself. Our work: a Dockerfile, an orchestration file, a script that generates the passwords and secret, and a quick-start guide in Traditional Chinese.

Delivery is a frozen snapshot: one zip, taken from the product repository at revision 2c67ad2.

Known limitations

The service serves plain HTTP on port 8080 of the local machine only; TLS and a reverse proxy are yours to bring for any wider access
The example application runs on the framework development server and is not designed for serving the public
The data lives in a Docker named volume, and docker compose down -v deletes all of it
The first start builds the image on your machine, fetching from registries and package repositories during that time
Pinned to the delivered snapshot; it does not follow upstream.

The liability cap, the scope of what is promised and the statutory floor are governed by the Terms of Service.

Vetting record

Everything below was checked against the pinned commit 30e13dc. Every verdict carries its full reasoning, an evidence link and the checker; failures are published, not hidden — do not take our word for it, verify it yourself.

3 PASS2 WARN0 FAIL

Source ReviewPASS

Read: docker-compose.yml (port published only on 127.0.0.1, the database reachable only inside the compose network, database image fixed by digest, startup refused when a required value is missing), scripts/quickstart/init-env.sh (openssl generates random values), docker/web/entrypoint.sh (creates the admin user, then starts the example application) and docker/web/config.py (secret and database credentials come from environment variables). The upstream source was not read file by file.

Script SafetyPASS

The scripts on the buyer path were read line by line: init-env.sh runs on the buyer host and only writes .env; entrypoint.sh runs inside the container. Neither downloads anything or pipes a download into a shell. The Dockerfile installs the package and the PostgreSQL driver with pip at build time; what those packages do was not inspected.

RecencyWARN

This product is a frozen snapshot and does not follow upstream: the upstream source is pinned to the revision recorded in the product repository (see the evidence link). How recently upstream has been active was not checked.

LicensePASS

SPDX:BSD-3-Clause

The LICENSE file in the product repository was read: the BSD-3-Clause text with the upstream copyright line, and PRODUCT.md and ATTRIBUTION.md record the same licence for upstream. The evidence link points at the upstream file at the pinned revision; it was not compared byte by byte with the copy in the product repository from this environment.

Dependency LicensesWARN

This records the declared side, not a scan result: dependency packages are fetched by the buyer at build time and the database image is pulled from its registry, and their contents were not scanned for licences. Upstream has no submodule and no third-party dataset was copied in (see ATTRIBUTION.md).