Skip to content

Latest commit

 

History

History
44 lines (33 loc) · 1.67 KB

README.md

File metadata and controls

44 lines (33 loc) · 1.67 KB

Issabel PBX

Issabel for Docker in centos 7 (development - not production)

Install

$ docker run --privileged --restart=always --name issabel -v /sys/fs/cgroup:/sys/fs/cgroup:ro -dti --hostname pbx  deathmetall/issabel:latest
$ docker exec -it issabel ./install.sh

This process is necessary to install issabel within the centos image with systemd, after the installation we create a new image from it with our pbx configured.

This image is designed to be used as a host leaving available ports 80 and 443 which I am using with Traefik, port 80 and 443 are still exposed in the image.

$ docker commit issabel deathmetall/issabel:live
$ docker rm -f issabel

Run


$ docker run --restart=always --name issabel \
        --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro \
        -v issabel-etc:/etc -v issabel-data:/var/lib \
        -dti --hostname pbx.saiyans.com.ve --network host \
       deathmetall/issabel:live

docker-compose.yml

This compose is designed to be used as a host leaving available ports 80 and 443


$ git clone https://github.com/tomasmetal23/Issabel.git

to configure the apache ports edit the ssl.conf and httpd.conf files that were downloaded from the repository.


$ docker-compose up -d

Done

Notes

I think that an optimal image for production should have each service separated into another image, example: apache/issabel, mysql/issabel.

https://blog.saiyans.com.ve/2020/09/25/pbx-issabel-despliegue-con-docker/

https://hub.docker.com/repository/docker/deathmetall/issabel