Docker Installation
Set up the APPNETOS Docker environment, install the project and enable only the services required by your applications.
1. Obtain the repositories
Clone the APPNETOS Docker repository and then place the APPNETOS project inside its workspace.
git clone <APPNETOS_DOCKER_REPOSITORY_URL> appnetos-docker
cd appnetos-docker
mkdir -p workspace
git clone <APPNETOS_REPOSITORY_URL> workspace/appnetos
The Docker repository contains infrastructure configuration; the APPNETOS project provides the core, applications and installation scripts.
2. Configure Docker
cp .env.example .env
id
Review
.env
, especially Linux UID/GID mapping, service ports, database credentials and Xdebug
settings. The environment file must not be committed.
LOCAL_UID=1000
LOCAL_GID=1000
LOCAL_USER=developer
LOCAL_GROUP=developer
The values above are examples; use the actual account and group values for your host.
3. Optional: DNS Control and BIND
Only deployments that include
appnetos-dns-control
and its BIND integration need the
DNS-specific services, volumes, worker processes and RNDC key. If those services are enabled, create the
key
before starting the DNS environment:
bash scripts/bind/generate-rndc-key.sh
The key is stored at
shared/bind/rndc/rndc.key
and must never be committed. Ensure the relevant
Compose services are enabled only for applications that require them.
4. Start the required containers
docker compose -f compose.yaml -f compose.development.yaml up --build -d
docker compose -f compose.yaml -f compose.development.yaml ps
The command above follows the supplied development Compose documentation. For production, review and adapt the Compose files, network exposure, secrets, volumes and enabled services instead of assuming the development override is production-ready.
5. Run the APPNETOS installer
docker exec -it appnetos-php bash
cd /var/www/appnetos/appnetos
bash scripts/install.sh
The installer processes Composer, Git, Environment, Platform, Public, Permissions, Applications and Healthcheck. It discovers applications automatically.
6. Validate the deployment
docker compose -f compose.yaml -f compose.development.yaml ps
docker compose -f compose.yaml -f compose.development.yaml logs --tail=100
Check installer output and the configured HTTP endpoint (development default
http://localhost:20000
). The installer healthcheck validates public resources and CLI
execution; it is not a substitute for application-level end-to-end checks.
7. Application-specific workers
Worker Scheduler and Runner containers may be deployed for applications that need background processing. Do not start DNS-specific worker containers unless DNS Control is installed and its worker functionality is required.
bash scripts/worker/status.sh
bash scripts/worker/restart.sh
These scripts are available in the supplied newer Docker README. Restart long-running workers after code deployments when loaded PHP code has changed.
8. Host Apache and application domains
When Apache is installed on the host as a reverse proxy, it forwards requests to the exposed HTTP port
of the
APPNETOS Apache container. For example, a host virtual host can forward a domain to the local port
20000
.
Application context routing and permitted hostnames are configured separately in each application's
configuration.
# Illustrative Apache host virtual host; adapt DNS, TLS and ports.
<VirtualHost *:80>
ServerName application.example.com
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:20000/
ProxyPassReverse / http://127.0.0.1:20000/
</VirtualHost>
Enable the required Apache proxy modules and terminate HTTPS appropriately. Preserve the original Host header so APPNETOS can match application host configurations. The host Apache configuration does not replace APPNETOS application routing; the domain must also be configured for the intended application context.
Replace development credentials, disable Xdebug, restrict MongoDB/Redis exposure, protect RNDC and other secrets, configure TLS, and verify backup and restore procedures.