Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.skrmir.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Deploy Your First App

​
Audience

This page is for developers and implementers delivering an application into AiOS for the first time.

​
Goal and Scope

This page explains two common first-delivery paths:
  1. using Git as input to the unified delivery pipeline
  2. using Compose as input to the restricted import pipeline

​
Core Concepts

  • all application inputs ultimately normalize into the AppSpec delivery model
  • Git is a normal input source; Compose is a restricted import source
  • production delivery remains approval-gated by default

​
Standard Workflow

​
Deploy from Git

  1. provide the Git repository URL
  2. parse and generate AppSpec
  3. submit the deployment task
  4. track task state, audit records, and health-check results

​
Import from Compose

  1. read the Compose file
  2. generate a supported / warn / blocked report from the support matrix
  3. if validation passes, convert into AppSpec
  4. continue through the unified deployment chain

​
Planned CLI Examples (Not Yet Implemented)

The repository does not currently ship these delivery commands. They are retained only to show how a future CLI should reuse the same application-delivery path. 
aios app up --from-git https://example.com/org/app.git --env dev
aios app up --from-compose ./compose.yaml
aios app up --from-compose ./compose.yaml --strict

​
Web UI Path

  • application creation wizard → choose Git or Compose input
  • review import report, deployment history, and task status

​
Pitfalls / Risk Notes

  • Git input never bypasses the unified deployment or approval chain.
  • Compose import is not “full compatibility”; fields such as build may remain blocked in v1.
  • --strict is better suited for CI or production-facing import workflows.