This image serves as a starting point for legacy CodeIgniter projects.

The CodeIgniter User Guide is served up by default if nothing has been copied or mounted to /var/www/html.

• php5.6-apache, latest: Dockerfile
• php7.1-apache : Dockerfile.php7.1

Start a container using the latest image, mapping your local port 80 to the container's port 80:

$ docker run -p 80:80 --name codeigniter aspendigital/codeigniter:latest
# `CTRL-C` to stop
$ docker rm codeigniter  # Destroys the container

If there is a port conflict, you will receive an error message from the Docker daemon. Try mapping to an open local port (-p 8080:80) or shut down the container or server that is on the desired port.

• Visit http://localhost using your browser.
• Hit CTRL-C to stop the container. Running a container in the foreground will send log outputs to your terminal.

Run the container in the background by passing the -d option:

$ docker run -p 80:80 --name codeigniter -d aspendigital/codeigniter:latest
$ docker stop codeigniter  # Stops the container. To restart `docker start codeigniter`
$ docker rm codeigniter  # Destroys the container

Using Docker volumes, you can mount local files inside a container.

The CodeIgniter system folder resides in /var/www/codeigniter. You may need to update the $system_folder variable in your project's include/ci_include.php file.

The container uses the working directory /var/www/html for the web server document root. You can introduce your local project code with bind-mounted volumes:

$ docker run -p 80:80 --rm \
  -v $(pwd):/var/www/html \
  aspendigital/codeigniter:latest

Save yourself some keyboards strokes, utilize docker-compose by introducing a docker-compose.yml file to your project folder:

# docker-compose.yml
version: '2.2'
services:
  web:
    image: aspendigital/codeigniter:latest
    ports:
      - 80:80
    volumes:
      - $PWD:/var/www/html

With the above example saved in working directory, run:

$ docker-compose up -d # start services defined in `docker-compose.yml` in the background
$ docker-compose down # stop and destroy

Environment variables can be passed to docker-compose.

The following variables trigger actions run by the entrypoint script at runtime.