Closed Ballzer0 closed 5 years ago
Hi,
I don't think this is a good idea, it makes it very easy to break the current configuration as you would need to pass all the perl code to insert the additional settings, not just the parameter name and value.
If you need a custom Config.pm then the correct way of doing it is by creating a new image that uses this one as a base, and add your custom Config.pm file to /kernel, which then gets copied to /opt/otrs on container start.
Something like:
FROM juanluisbaptiste/otrs:latest
LABEL maintainer='xxxxxx'
COPY Config.pm /Kernel'
That's it.
would it be possible to have a "free text" field in the .env file where you could write Custom configuration, this text would be placed in the Kernel/Config.pm file in the section under the section.
this is not really an issue, but more of a feature request, but having this would mean that developers could preconfigure stuff like ldaps services, that are impossible to do in the SysConfig UI