This release is a pre-release and may not be stable for production use.
half-orm-gen
⚠️ Alpha — not for production.
This project is under active development. APIs, generated code structure, and CLI commands may change without notice between releases. Do not use in production environments.
A halfORM extension that generates a Litestar REST API and a frontend backoffice (SvelteKit 5 or Angular) from your half-orm-dev project.
Installation
pip install half-orm-gen
API
half_orm gen api --litestar
litestar --app ho_api/app:application run --reload
Frontend backoffice
# SvelteKit 5
half_orm gen frontend --svelte
cd ho_frontend/svelte && npm install && npm run dev
# Angular
half_orm gen frontend --angular
cd ho_frontend/angular && npm install && npm start
Contributing
We are looking for contributors with expertise in:
- Angular — improve generated components, routing, and state management
- SvelteKit — improve generated stores, layouts, and page components
- Litestar — improve the dynamic runtime, middleware, and OpenAPI integration
See CONTRIBUTING.md for how to set up a development environment and the areas where help is most needed.
Documentation
Authentication
- Overview — authentication vs authorization, env vars, file map
- Local authentication —
identity.user,local_auth.py, HS256/RS256 signing - Federation — sharing identities across independently-deployed peers
Backend
- Authorization — JWT, roles,
/ho_access,/ho_setup - CRUD access — access model, verbs, field access,
@ho_api_filter,@tools.api_* - What goes in a relation class — class vs.
ho_api/custom/, the escape hatch
Frontend (shared)
- Generated frontend code — file layout, regenerated vs scaffolded
- ResourceSilo reference — full reactive API, one silo per app
- AuthService / AuthState reference — session, WS, simulation, route guards
Angular
- Access control — reactive buttons, FK auto-resolve, dynamic roles, simulation
Svelte
- Access control — reactive buttons, FK auto-resolve, dynamic roles
Internals — half-orm-gen's own implementation, for maintaining/extending the generator itself
- Litestar architecture — runtime, CRUD_ACCESS, role system, WebSocket
- Frontend architecture — silo pattern, access map, live updates
- Angular silo architecture — signals, data flow, deduplication
- Svelte silo architecture — runes, data flow, deduplication
See also
- half-orm — the PostgreSQL ORM at the core
- half-orm-dev — the development framework
Metadata
Release files for half-orm-gen 1.1.0a1
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 | |
|---|---|---|---|---|
| half_orm_gen-1.1.0a1.tar.gz | 578.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| half_orm_gen-1.1.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / half_orm_gen-1.1.0a1.tar.gz
| Download URL | half_orm_gen-1.1.0a1.tar.gz |
|---|---|
| Size | 578.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
688197e4a02ef6497b3bc3d691efb12f3aaadb6747253dae609d707ed4598ba1
|
|
BLAKE2b-256 checksum How to use checksums |
8a5bfb362b79e2d87431e1b144954fb4d942c7b5e16fceccc9780e2c254bed57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Release files / half_orm_gen-1.1.0a1-py3-none-any.whl
| Download URL | half_orm_gen-1.1.0a1-py3-none-any.whl |
|---|---|
| Size | 631.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b7d9a0c29aa361f3adb23cfc066de3e16e5b36d369b30175475015f5ea574e4
|
|
BLAKE2b-256 checksum How to use checksums |
1b9631008c95f6f240232b95715a02b5df9f1178b679dd7981f9cb75be02b2f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Security for half-orm-gen 1.1.0a1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.