Migration runner ready and a sister site can deploy from a clean
checkout with one .env file.
ADRs relocated (migrations/adr/ -> docs/adr/):
- migrations/ is now Alembic territory, not docs.
- All cross-references updated: CLAUDE.md, docs/PLUGIN-HOOKS.md,
docs/PLUGIN-QUICKSTART.md.
Alembic initialized (migrations/):
- env.py, script.py.mako, alembic.ini copied from Flask-Migrate
templates so `flask db migrate` and `flask db upgrade` work without
a one-time `flask db init` (which would clash with the existing
migrations/ directory).
- Baseline migration generated via autogenerate, captures all 47
tables (core models + 6 plugins) as the upgrade target. Ready for
per-site `flask db upgrade` from an empty schema.
Deploy artifacts:
- Dockerfile: python:3.12-slim base, gunicorn server, non-root user,
healthcheck against /api/auth/login. Single image bundles all six
plugins; sites enable via `flask plugin install <name>`.
- docker-compose.yml: MySQL 8 + API container, healthcheck-gated
startup, env-driven secrets that fail loud on missing values
(`${SECRET_KEY:?}` form).
- .env.example: full env-var inventory with comments. Calls out
required vs optional. Matches what ProductionConfig.validate
enforces.
docs/DEPLOY.md:
- Step-by-step per-site runbook: clone, configure .env, bring up
stack, run migrations, seed reference data, install plugins,
create admin, front with TLS, backups, updates.
- Common-issues table.
- Cross-links to ADR-004 (per-site rationale), ADR-003 (plugin
distribution), and the config source.
Skills:
- migrating-asset-schema: Alembic + one-shot data migration policy.
Rules: additive first, renames are three steps, destructive ops
need rollback, equipment migration filter per ADR-001 + ADR-005.
- hardening-flask-config: production validation, CORS allowlist
policy, JWT cookie hardening, per-site deploy isolation per ADR-004.
CLAUDE.md updated to reflect the post-Phase-5 state. No tests added
this commit; the Alembic baseline is exercised by the existing
db.create_all-based test suite (tests do not touch the migration
runner; that's by design until per-plugin migrations land).
Test count unchanged: 101 passing.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5.3 KiB
Plugin Quickstart
Build a working shopdb-flask plugin in 30 minutes. This walks through generating, customizing, installing, and testing a plugin from scratch.
For the full hook reference, see PLUGIN-HOOKS.md. For the architectural decisions behind the contract, see docs/adr/.
Step 1: Generate the skeleton
flask plugin new cameras --description "Tracks shop-floor surveillance cameras"
Output: plugins/cameras/ with manifest, plugin class, example model, example routes, schemas stub, tests, and a README.
The generated plugin already passes the framework's contract tests. Verify before editing:
pytest plugins/cameras/tests/
Step 2: Edit the model
Open plugins/cameras/models/cameras.py. Replace the examplefield placeholder with your domain fields:
class Cameras(BaseModel):
__tablename__ = 'cameras'
assetid = db.Column(
db.Integer,
db.ForeignKey('assets.assetid', ondelete='CASCADE'),
primary_key=True,
)
streamurl = db.Column(db.String(255), nullable=False)
resolution = db.Column(db.String(20))
fps = db.Column(db.Integer)
poeport = db.Column(db.String(50))
asset = db.relationship('Asset', backref=db.backref('cameras', uselist=False))
def to_dict(self):
return {
'assetid': self.assetid,
'streamurl': self.streamurl,
'resolution': self.resolution,
'fps': self.fps,
'poeport': self.poeport,
}
Note the naming convention: lowercase concatenated, no underscores (streamurl, not stream_url). See CONTRIBUTING.md.
Step 3: Add routes
Open plugins/cameras/api/routes.py. The scaffold provides list and detail endpoints. Add CRUD as needed:
@cameras_bp.route('', methods=['POST'])
@jwt_required()
def create_camera():
data = request.get_json()
asset = Asset(assetnumber=data['assetnumber'], name=data['name'], ...)
db.session.add(asset)
db.session.flush()
camera = Cameras(
assetid=asset.assetid,
streamurl=data['streamurl'],
resolution=data.get('resolution'),
)
db.session.add(camera)
db.session.commit()
return success_response(camera.to_dict(), http_code=201)
For audit logging, use the public helper:
from shopdb.api import audit_log
audit_log(action='created', entitytype='Camera', entityid=asset.assetid, entityname=asset.name)
Step 4: Install the plugin
flask plugin install cameras
flask db migrate -m "Add cameras plugin tables"
flask db upgrade
install runs the plugin's on_install hook (which seeds the AssetType row), registers it in the plugin registry, and runs migrations.
Step 5: Verify it works
flask plugin list
You should see cameras [Enabled].
Run the plugin's tests:
pytest plugins/cameras/tests/
Hit the API:
curl http://localhost:5001/api/cameras
Step 6: Add hooks (optional)
Override hooks on the plugin class as needed. See PLUGIN-HOOKS.md for the full list. Common ones:
| Hook | Adds |
|---|---|
get_searchable_fields |
Plugin contributes to the global search endpoint |
get_navigation_items |
Plugin shows up in the sidebar nav |
get_dashboard_widgets |
Plugin's dashboard widget appears on the home page |
get_collector_schema |
Plugin accepts external pushes at /api/collector/<name> |
Each hook has a default that does nothing. Override only what your plugin needs.
Step 7: Frontend (manual for now)
Backend scaffolding is automated. Frontend is manual until the frontend scaffolding skill ships. Convention:
frontend/src/views/cameras/CamerasList.vuefrontend/src/views/cameras/CameraDetail.vuefrontend/src/views/cameras/CameraForm.vue
Copy from an existing plugin's view files (e.g., frontend/src/views/network/) as a starting point. Update the API client in frontend/src/api/index.js to add cameras endpoints.
Common errors
| Symptom | Cause | Fix |
|---|---|---|
PluginNotFoundError: manifest.json |
Manifest deleted or moved | Restore plugins/<name>/manifest.json |
PluginContractError: missing required field |
manifest.json incomplete | Re-add name, version, description |
PluginVersionError: requires core_version X but framework is Y |
Framework upgraded past your range | Update core_version in manifest |
Table 'cameras' is already defined |
Two models declared the same __tablename__ |
Pick a unique table name |
| Index name collision | Two indexes share the same name (SQLite enforces global uniqueness) | Prefix index names with table: idx_cameras_streamurl |
Next steps
- PLUGIN-HOOKS.md for the full hook reference
- CONTRIBUTING.md for naming conventions
- docs/adr/ADR-001-asset-as-platform-contract.md for what your plugin can rely on
- docs/adr/ADR-006-collector-contract.md for accepting external collector input
Distribution
If you are building a plugin for a specific GE Aerospace site (sister-site adoption), ship it as its own git repo. The site running shopdb-flask clones or symlinks your plugin into <repo>/plugins/<name>/. See ADR-003.