Download the PHP package cboxdk/platform without Composer
On this page you can find all versions of the php package cboxdk/platform. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download cboxdk/platform
More information about cboxdk/platform
Files in cboxdk/platform
Package platform
Short Description Cbox Platform — the typed application model, deterministic Kubernetes compiler, and plan/diff primitives shared by Cbox Local and Cbox Cortex.
License MIT
Homepage https://github.com/cboxdk/platform
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package platform
Cbox Platform
A typed application model, a deterministic Kubernetes compiler, and plan/diff primitives — as a library you embed, not a platform you run.
This is not another PaaS and not a Kubernetes framework. It runs no service, owns no cluster, applies nothing, and has no opinion about how you deploy. It answers one question — what does an application resource mean, and what Kubernetes objects does that intent compile to? — and answers it the same way every time.
No container, no ORM, no configuration file, no network. That is the whole point.
Why it exists
Two products needed to agree on what a Cbox application is:
- Cbox Cortex — the hosted platform. Customer intent lives in Postgres; the compiled output is applied to production clusters over a Go bridge.
- Cbox Local — a local, production-like development platform on kind.
They differ in how intent is discovered, built, applied and operated. They must not differ in what an application means or how that intent compiles to Kubernetes — otherwise "works locally" stops being evidence of anything. So the middle of the diagram became a package, and both products consume it.
Cortex and Local are the reference consumers. Nothing about either is required to use this package.
Install
Requires PHP 8.4+. The only runtime dependency is symfony/yaml.
What it gives you
Typed intent, not arrays. ServiceSpec, DatabaseSpec, BackupSpec,
RunSpec, EnvironmentGatewaySpec and friends are readonly value objects.
Where they come from is your problem and deliberately so — an ORM, a YAML file,
a Git repository, CLI flags, or a test fixture written by hand.
A compiler that is a pure function. compile() reads no database, no
cluster, no config, no clock, no environment, no network. Everything it needs
arrives in the spec and the target. Given the same input it emits the same
bytes — which is what makes the next two features possible at all.
Plan/diff without touching a cluster. Manifests are content-hashed with a canonical encoding, so "did anything change" is a hash comparison against what you last applied:
Retain the previous bodies as well and the plan can say what changed, not merely that something did — with secret material redacted, always:
A typed target instead of feature flags. What a cluster can actually do —
whether its nodes can checkpoint an idle workload, where the HTTP autoscaler's
interceptor lives, which engine images to run, who signs its certificates, what
a customer's own kubectl may do — is one PlatformTarget object. There is no
if ($local) anywhere in the compiler, and there will not be: a difference
between two clusters is a value, and a value is testable.
Product semantics, not mechanisms. Scale-to-zero, suspend/resume, autoscaling and health are expressed as what the customer asked for. Whether a wake is a checkpoint restore or a cold pod start is the target's business, not the application's.
What it does not do
- Apply anything. It emits objects. Applying them — server-side apply, drift reconciliation, status — is yours.
- Build images. It consumes an image reference. Dockerfiles, BuildKit and registries live in the consumer.
- Provision infrastructure. No clusters, no node pools, no provider APIs, no credentials.
- Pretend Kubernetes isn't there. Kubernetes is the shared runtime contract,
and the abstraction is at the application-resource level. There is no
GenericRuntimeCompilerwaiting for a Nomad backend that is not coming.
Documentation
- Overview and mental model
- Quickstart
- Architecture
- The platform target
- Labels on compiled objects
- Kubernetes API versions
- Plan and diff
- Public API and what
0.xmeans - Compiling without a framework
- Writing your own mapper
- Testing: the shipped trait and fakes
- Threat model
- The open-source boundary
Status
0.x. The model and compiler are extracted from a system running real customer
workloads, so the behaviour is not speculative — but the API is young and may
change in a minor release. See Public API
for what is covered and what is internal.
Contributing
CONTRIBUTING.md. The short version: the compiler stays pure, and golden files are never regenerated to make a test pass.
License
MIT. See LICENSE.
