Applications
Technical details of the Applications installation phase.
Installing an application does not mean every optional infrastructure service must run. Configure application-specific workers, DNS services and other dependencies only when needed.
The Applications installation phase is responsible for installing every discovered APPNETOS application.
Unlike traditional installers, APPNETOS does not maintain a predefined application list.
Instead, applications are discovered automatically during runtime and installed using a common installation workflow.
Goals
The Applications installation phase has the following responsibilities:
- Discover APPNETOS applications.
- Detect supported installation areas.
- Execute every installation area.
- Report installation results.
- Provide deterministic application installation.
Automatic Application Discovery
The installer automatically scans the APPNETOS workspace for applications.
Every valid APPNETOS application is processed.
No application registration is required.
This allows new applications to become installable immediately after being added to the workspace.
Installation Areas
Each application may provide one or more installation areas.
Currently supported installation areas are:
| Installation Area | Purpose |
|---|---|
| MongoDB | Database collections, documents and indexes |
| Filesystem | Application filesystem resources |
| Platform | Shared platform resources |
Applications are free to implement only the installation areas they require.
Missing installation areas are skipped automatically.
MongoDB
The MongoDB installation area prepares the database structure of an application.
Typical installation tasks include:
- Create collections
- Insert installation documents
- Create indexes
- Perform idempotent document updates
Installation resources are located inside:
.files/MongoDB/
Filesystem
The filesystem installation area prepares application-specific runtime resources.
Typical resources include:
- Directories
- Static files
- Configuration files
- Templates
- Runtime resources
Installation resources are located inside:
.files/filesystem/
Platform
The platform installation area installs shared platform resources.
Typical resources include:
- Shared runtime files
- Platform configuration
- Application bootstrap resources
Installation resources are located inside:
.files/platform/
Installation Workflow
For every discovered application the installer performs the following workflow.
Application
│
├── MongoDB
├── Filesystem
└── Platform
Each installation area executes independently.
If an installation area is not present, it is skipped automatically.
Installation Summary
After every application the installer reports a summary.
Example:
Installation summary:
[MongoDB]
insertedDocuments: 468
createdIndexes: 21
[Filesystem]
sourceDirectories: 3
sourceFiles: 1
[Platform]
sourceDirectories: 4
sourceFiles: 4
Duration: 0.441 seconds
APPNETOS application installed successfully.
This summary provides a complete overview of the performed installation.
Error Handling
Errors occurring inside an application installation stop the installation immediately.
The installer always reports:
- the affected application,
- the installation area,
- the reported error.
This prevents partially installed applications.
Idempotency
The Applications installation phase is fully idempotent.
Existing installation resources are validated before modifications are performed.
Typical examples include:
- Existing MongoDB documents are updated.
- Existing indexes are preserved.
- Existing platform resources are skipped when unchanged.
Applications can therefore be installed repeatedly without creating duplicate resources.
Extensibility
The application installation architecture is intentionally modular.
Future installation areas can be added without modifying existing applications.
Examples include:
- Redis
- Elasticsearch
- Object Storage
- Search indexes
- Queue initialization
Applications automatically benefit from new installer capabilities when supporting the corresponding installation area.
Summary
The Applications installation phase provides:
- Automatic application discovery
- Modular installation areas
- Independent application installation
- Detailed installation reporting
- Fully repeatable execution
- Extensible installation architecture