RFE: Provide example usage when bundling content in derived builds.

[edseymour]

When using the container to deploy to a clustered environment, the mechanism for mounting content may differ.

It could be that content is bundled with the image through a new image build process, for example docker build or using an OpenShift S2I technique. A common use-case is for static websites to be built using some toolset and framework, for example Python Sphinx, or a Node.js build (ng build --prod). In these cases we might want to create a build pipeline that generates a new container image based on httpd-container and including the static content.

The main challenge with the existing container is where do I put this content? The /var/www directory, which can be used as a volume mount point, works fine for mounted content, but has some unexpected behaviour if used to drop-in content during a container build (I think this technique may work if content is dropped to /opt/rh/httpd24/root/var/www).

One technique that I adopted for an OpenShift S2I build was to use the default location /opt/app-root/src and drop in a static.conf file to /etc/httpd/conf.d that adds this location using a <Directory> directive.

[phracek]

Closing this issue as it has been stale for a long time. Feel free to re-open it and even file a PR with test