APPNETOS is under active development This website and its documentation are being prepared for public launch. Content and features may change.
Select Theme
Loading

Public

Technical details of the Public installation phase.

The Public installation phase prepares the public web directory used by APPNETOS.

Applications may provide publicly accessible resources such as assets, images, JavaScript files or application entry points.

The installer automatically discovers these resources and installs them into the shared public directory.

Goals

The Public installation phase has the following responsibilities:

  • Create the shared public directory.
  • Discover application public resources.
  • Install public application files.
  • Preserve existing resources where appropriate.
  • Keep the public runtime synchronized with installed applications.

Public Installation Area

Applications may provide a public installation area.

Example:

.files/public/

If the directory exists, it is processed automatically.

Applications without public resources are skipped.

No manual registration is required.

Shared Public Directory

All installed public resources become part of the shared APPNETOS public directory.

Example:

public/
├── appnetos/
├── application-one/
├── application-two/
├── application-three/
├── application-four/
└── ...

Each application owns its own public namespace.

This prevents resource conflicts between applications.

Automatic Discovery

During installation every discovered APPNETOS application is examined.

If a public installation area exists, its contents are copied into the shared public directory.

Typical installer output:

[ OK ] Public 'appnetos' installed
[ OK ] Public 'application-one' installed
[ OK ] Public 'application-two' installed

Applications without a public installation area are skipped automatically.

Installation Behaviour

Existing resources are validated before being copied.

Unchanged files remain untouched.

Only required resources are installed.

This guarantees deterministic installation results.

Runtime Resources

Typical public resources include:

  • CSS
  • JavaScript
  • Images
  • Fonts
  • Static assets
  • Application entry resources

Applications remain fully responsible for the contents of their public resources.

Debug Resources

Some runtime resources are generated only for development environments.

For example, the APPNETOS DebugBar resources are installed automatically when debugging is enabled.

Production installations remain free of unnecessary development assets.

Idempotency

The Public installation phase is fully idempotent.

Running the installer multiple times does not create duplicate resources.

Existing files are validated before installation.

Error Handling

Errors occurring during the public installation phase stop the installation immediately.

This prevents incomplete public runtimes.

The installer reports the responsible application.

Summary

The Public installation phase provides:

  • Automatic public resource discovery
  • Shared public runtime generation
  • Application-specific public namespaces
  • Development resource support
  • Fully repeatable execution

Next Steps

Previous

Platform

Go to Platform

Next

Permissions

Go to Permissions