web2.0 implementation of project8/dripline
The dockerfile builds in SSL support and automatically generates default certificates. These certificates are valid for encription but are local. Your browser will warn that the source is not known. If we want to use this for real we should figure out how to get legit certificates and they should not be stored in a repo, they should be local to the host system and volume mounted to the container.
If you want to develop code with a running container and volume mount (excellent choice, by the way), note that you should mount your page at /var/www/html/<page_data> not at the top-level /var/www/html location. This is because the dripline-web files are stored in /var/www/html/dripline-web and you don't want to mount over them.
Other dependencies, if needed, can be similarly be stored in /var/www/html/<lib_name> so that they don't conflict.
For amqp we want to use the rabbitmq:3-management image.
The php image (base for this Dockerfile) doesn't play well in the foreground (ie -it run options), you should always run it detatched (-d) and then use the docker exec command to attach if needed.
For now there are demo scripts from the AMQP tutorial. To run them build the Dockerfile in the scripts subdirectory. The default command is to run the tutorial's server, but both are included.