You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are refactoring the modsecurity-docker repository, and we saw that the ModSecurity-apache binary is built in the Dockerfile from source.
And while the installation process is simple, we would prefer to simply install a binary or a package for a target platform, for several reasons:
Building, testing and attaching a version number should be part of the release process of the software, not the build process of a Docker image.
ModSecurity binaries we ship with an image should be available also separately, outside of the Docker image.
If there are any dependencies they should be covered by the software's build process to make installation easy on and independent from installation processes of ModSecurity's target platforms.
Are you planning on releasing ModSecurity-apache packages here on GitHub? Is there anything that we can help you with getting that realized?
The text was updated successfully, but these errors were encountered:
The packages for ModSecurity are distribution (and platform) dependent, we trust the distributions to keep the packages up to date. Maybe, it is the case to install the distribution package in the docker image.
We are refactoring the modsecurity-docker repository, and we saw that the ModSecurity-apache binary is built in the Dockerfile from source.
And while the installation process is simple, we would prefer to simply install a binary or a package for a target platform, for several reasons:
Are you planning on releasing ModSecurity-apache packages here on GitHub? Is there anything that we can help you with getting that realized?
The text was updated successfully, but these errors were encountered: