SCAN_INTERVAL=1h restart: unless-stopped volumes: phpipam-logo:/phpipam/css/images/logo phpipam-cron: IPAM_DATABASE_NAME=existing_db_name restart: unless-stopped volumes:
Phpipam-logo: Docker External MySQL ServerĮxample external MySQL server deployment via docker-compose. phpipam-db-data:/var/lib/mysql volumes: MYSQL_ROOT_PASSWORD=my_secret_mysql_root_pass restart: unless-stopped volumes: SCAN_INTERVAL=1h restart: unless-stopped depends_on: Image: phpipam/phpipam-cron:latest environment: phpipam-logo:/phpipam/css/images/logo depends_on: IPAM_DATABASE_WEBHOST=% restart: unless-stopped volumes: IPAM_DATABASE_PASS=my_secret_phpipam_pass # WARNING: 'my_secret_phpipam_pass' and 'my_secret_mysql_root_pass' version: '3 ' services:
# WARNING: Replace the example passwords with secure secrets. Save and edit the the below configuration as docker-compose.yml and run docker-compose -p phpIPAM up -d from the same directory.
nightly Nightly development snapshot (non-production).Įxample full stack deployment via docker-compose.1.5x Tracks the latest 1.5x release candidate.latest Tracks Latest production release (1.4x).When running under Kubernetes, set allowPrivilegeEscalation=true Supported Tags When running under Docker, NET_ADMIN and NET_RAW container capabilities are required for ping and SNMP functionality. Only a single running replica of the phpipam-cron container should be deployed. Multiple replicas of the phpipam-www container can be deployed and load-balanced. phpipam-cron cron container for scheduled network discovery jobs.phpipam-www Frontend Apache/PHP container.Issues and pull requests for the phpIPAM application can be found at Container Images Issues and pull requests/patches for phpipam-docker can be found at See HAProxy example below.įor advanced use-cases phpIPAM can be installed in a VM by following the instructions found at Source files, Issues & Pull Requestsĭockerfile build sources can be found at Native SSL support can be achieved by use of the many reverse-https-proxy docker images available on DockerHub. Given the intended audience, simplicity is preferred over complexity and some advanced use cases are not supported with these images. As the typical users of phpIPAM (Network admins) have limited experience with LAMP stacks, these docker images provide a simpler method to create and maintain a working phpIPAM environment.
0 kommentar(er)
