Core architecture

Hubleto is built from small parts that are connected in a few well-defined places. Knowing these places is more useful than knowing every class.

Principles

• Everything is an app. The sign-in page, the desktop, settings and the CRM are apps. An app is a folder with a manifest.yaml and a Loader class. The ERP core only loads and wires the apps.
• The model describes everything about the data. Columns, relations, labels, table and form descriptions are in the model. The UI asks the model what to display. See the Description API.
• The browser is a thin client. PHP renders the page shell with Twig and the React components fetch the data from JSON endpoints.
• Apps talk to each other through contracts, not by editing each other: managers (Calendar, Workflow, Dashboards, Settings), events, extendibles and FormCustomizer.
• Services are singletons created by the dependency injection container.

The extension points

Extension points.

Where the code runs

┌──────────────────────────────── PHP (server) ─────────────────────────────┐
│ index.php → boot.php → Loader::init() → AppManager (init() of each app)   │
│ Router → Renderer → Controller::prepareView() → Twig view                 │
│ Api controllers → Model → RecordManager (Eloquent) → MySQL / MariaDB      │
└────────────────────────────────────────────────────────────────────────────┘
┌──────────────────────────── JavaScript (browser) ─────────────────────────┐
│ Loader.tsx of each app → hblreact-* tags → Table / Form components        │
│ request.get() / post() → api/... endpoints                                │
└────────────────────────────────────────────────────────────────────────────┘

The details of each step are in Core.

Pages in this chapter

• Dependency injection
• User management and authentication