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

Healthcheck

Technical details of the Healthcheck installation phase.

The Healthcheck installation phase validates the completed APPNETOS installation.

It is executed after all installation phases have finished successfully and verifies that the runtime environment is ready for use.

The healthcheck performs only validation.

No installation data is modified during this phase.

Goals

The Healthcheck installation phase has the following responsibilities:

  • Validate the completed installation.
  • Detect incomplete installations.
  • Verify critical runtime components.
  • Prevent unnoticed installation failures.

Validation Process

The healthcheck executes a series of independent validation steps.

Each validation verifies one critical part of the APPNETOS installation.

If one validation fails, the installation is considered unsuccessful.

Public Resources

The healthcheck verifies that all required public resources have been installed successfully.

Typical output:

[ OK ] Public 'appnetos' healthcheck passed
[ OK ] Public 'application-one' healthcheck passed
[ OK ] Public 'application-two' healthcheck passed

Every installed application providing public resources is validated individually.

Command Validation

The installer verifies that the APPNETOS command line interface is operational.

Typical output:

[ OK ] APPNETOS command healthcheck passed

This confirms that the runtime can successfully execute APPNETOS commands after installation.

Installation Validation

After all individual checks have completed successfully, the installer validates the installation as a whole.

Typical output:

[ OK ] Installation healthcheck completed

This indicates that all required installation phases completed successfully.

Failure Handling

If any validation fails, the installer stops immediately.

The reported error identifies the failed validation so that the problem can be corrected before the installation is used.

The healthcheck never attempts automatic repairs.

Its sole purpose is validating the installation state.

Extensibility

The Healthcheck architecture is intentionally modular.

Additional validation steps can be introduced without changing the existing workflow.

Examples include:

  • MongoDB connectivity
  • Redis connectivity
  • Filesystem validation
  • Permission validation
  • Worker availability
  • REST endpoint validation
  • Application-specific healthchecks

Applications may provide their own healthchecks in future versions.

Continuous Validation

Although primarily executed during installation, the healthcheck architecture is suitable for additional use cases.

Examples include:

  • Deployment verification
  • Continuous Integration
  • Automated testing
  • Container startup validation
  • Production monitoring

This makes the healthcheck useful beyond the initial installation process.

Summary

The Healthcheck installation phase provides:

  • Runtime validation
  • Public resource verification
  • Command validation
  • Early detection of installation problems
  • Fully deterministic validation
  • Extensible healthcheck architecture

Next Steps

Previous

Applications

Go to Applications