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

Custom Installation

Deploy APPNETOS on infrastructure tailored to your application mix, network topology and operational requirements.

1. Prepare the infrastructure

Provision a supported PHP 8.5 runtime, Apache 2.4 with PHP-FPM, MongoDB, Redis and Composer. Configure PHP extensions required by the core and selected applications. The exact runtime topology, process management and resource allocation are deployment-specific.

Layer Responsibility
Web server Apache virtual hosts, PHP-FPM integration, TLS and reverse proxy where required
PHP runtime APPNETOS core and application code, PHP extensions and CLI
Persistence MongoDB with access controls, backup and recovery
Runtime services Redis and other services required by installed applications
Workers Scheduled and queued processing for applications that need it

2. Prepare the project

Deploy the APPNETOS core and the chosen applications into the same APPNETOS workspace layout. Each application can maintain its own dependencies and installation resources.

appnetos/
├── appnetos/
├── application-one/
├── application-two/
├── application-three/
├── public/
└── scripts/

Repository paths and application names are illustrative. Configure the runtime environment and secrets according to your server policy before running the installer.

3. Run installation

cd /path/to/appnetos/appnetos
bash scripts/install.sh

Run the installer as the appropriate deployment user with permissions to write the shared runtime directories. Confirm that required MongoDB and Redis services are reachable. The installation script is the documented entry point; custom service provisioning must be completed separately.

4. Configure Apache and application hosts

A single host Apache may serve APPNETOS directly through PHP-FPM or forward requests to a separate APPNETOS web server. Configure each public hostname in the relevant Apache virtual host and in the APPNETOS application context configuration.

# Example: Apache acting as a reverse proxy to an APPNETOS web service.
<VirtualHost *:80>
    ServerName application-one.example.com
    ProxyPreserveHost On
    ProxyPass / http://127.0.0.1:20000/
    ProxyPassReverse / http://127.0.0.1:20000/
</VirtualHost>

This is an infrastructure example, not an APPNETOS application configuration file. Actual host names, slugs, exposed ports and HTTPS configuration must match the deployed application contexts. Multiple application domains can forward to the same APPNETOS HTTP entry point; the APPNETOS router then resolves the matching application and context.

5. Configure application-specific services

Install only the services needed by the selected applications. A deployment without DNS Control does not require the DNS Control worker, BIND or RNDC. Applications with background jobs may use separate runners or share the same infrastructure.

6. Example: combine workers for two applications

For application-one and application-two , a custom worker host or container can supervise two separate long-running runner processes. They share CPU, memory and deployment infrastructure while retaining independent application commands and restart behavior.

# Conceptual process layout, not APPNETOS CLI syntax:
worker-host/
├── runner-application-one  -> application-one queue(s)
└── runner-application-two  -> application-two queue(s)

Use a process supervisor (for example systemd or supervisord) to start and restart both processes independently. Configure each runner with the application-specific queue and command supported by the deployed worker implementation. The uploaded documentation does not define a verified command-line syntax for combining multiple applications in one runner, so no unverified APPNETOS CLI flags are prescribed here.

If the runner implementation supports consuming multiple queues, the same runner process may be configured to handle both applications. Otherwise use two runners within one container or host. Preserve isolation for conflicting dependencies, resource limits, security boundaries or workloads that require independent scaling.

7. Validate and secure

Verify HTTP routing for every configured domain, database and Redis connectivity, filesystem permissions, CLI healthcheck output and any enabled worker queues. Configure log collection, monitoring, TLS, backups and recovery procedures.

Further configuration

Detailed application host, slug, context and worker configuration belongs to the respective application configuration and runtime reference documentation.

Next Steps

Previous

Docker Installation

Go to Docker Installation

Next

Installer Reference

Go to Installer Reference