- TypeScript 97.2%
- Shell 2.4%
- CSS 0.3%
- HTML 0.1%
|
All checks were successful
Quatrain CoreApps Sovereign CI / Build Containers & Validate Monorepo (push) Successful in 1m25s
Quatrain CoreApps Sovereign CI / Build Containers & Validate Monorepo (pull_request) Successful in 1m25s
Publish Studio Image Container / Build & Push Studio Image to qtrn.io (push) Successful in 1m19s
The packages/ entries were symlinks to absolute paths on one developer machine, dangling in every other checkout. Dependencies already resolve through the portal: resolutions and the studio-web Vite aliases point at ../../../Core and ../../../CoreUX directly, so nothing references them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| .tycho | ||
| .yarn/releases | ||
| apps | ||
| assets | ||
| bin | ||
| containers | ||
| examples/bookstore | ||
| .dockerignore | ||
| .gitignore | ||
| .yarnrc.yml | ||
| AGENTS.md | ||
| jest.config.ts | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| yarn.lock | ||
Core Applications & Deployments (CoreApps)
Important
The source of authority is git.qtrn.io/quatrain/core-apps: issues, pull requests, wiki and CI live there.
github.com/Quatrain/CoreAppsis a read-only mirror.
This monorepo houses all visual dashboard environments, local modeling APIs, API routing proxies, and containerized deployments built on top of the Core framework (by Quatrain).
🏗️ Repository Architecture
This workspace is managed using Yarn Berry (v4) Workspaces and is organized as follows:
CoreApps/
├── apps/
│ ├── studio-api/ # Local modeling API server (Express/SQLite)
│ └── studio-web/ # Visual developer studio frontend (React/Mantine)
├── containers/
│ ├── api-gateway/ # Traefik & Redis routing gateway container
│ └── studio-image/ # Bundled Visual Environment image
├── examples/
│ └── bookstore/ # Bookstore reference sandbox application
└── bin/
├── publish_container.sh # Container build & push to qtrn.io (Forgejo Actions)
└── push_tag.sh # Automated release tagging script
🛠️ Local Development
Prerequisites
To link and resolve package dependencies locally, the Core repository MUST be cloned in a sibling directory:
CODE/QUATRAIN/
├── Core/ # Foundation library packages
└── CoreApps/ # Applications & deployments (this repository)
All package linkages (@quatrain/*) are automatically mapped from the Core sibling packages via portal: resolutions.
Setup and Installation
Install dependencies and link workspaces:
yarn install
Running the Workspaces
Start all development environments concurrently:
yarn dev
Compiling
Build all applications and container setups sequentially:
yarn build
🚀 Versioning & Deployment
Deployments and releases are automated via Forgejo Actions on git.qtrn.io; images are published to the sovereign registry qtrn.io/quatrain/*:
- Release Tagging: Run the
bin/push_tag.shscript to bump the monorepo version patch, create a Git tag, and push it to the remote. - API Gateway Image:
.forgejo/workflows/publish-api-gateway.yamlrunsbin/publish_container.sh api-gateway. - Studio Environment Image:
.forgejo/workflows/publish-studio-image.yamlrunsbin/publish_container.sh studio-image. - Pushes to
developpublish:developand:sha-<commit>; pushes tomainbump the patch version, publish:<version>and:latest, and tag<container>-v<version>. SecretsREGISTRY_USERandREGISTRY_TOKENare required. - Images are published for
linux/arm64only: ARM64 is more resource-efficient (better performance per watt and lower instance cost), which is why the qtrn.io nodes and runners all run on it. Builds are therefore native, without emulation.PLATFORMScan request other platforms, built under QEMU;bun installis known to crash under amd64 emulation.
⚖️ License
Licensed under the GNU Affero General Public License v3.0 (AGPL v3).