Add support for /Add module Clientbuffer about docker-znc HOT 7 CLOSED

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

from docker-znc.

Alternatively, open up the ability for end-users to build custom modules within the docker container.

When attempting to do this:

root@e3511eee33ec:/# znc-buildmod /usr/lib/znc/custom/clientbuffer.cpp
[ !! ] Could not find g++. What happened to your compiler?

from docker-znc.

There is nothing stopping you in making those docker-mods and PR it to our docker-mod repo.

Building modules in the container are not something we want to support. The build tools are usually massive and will grow the image size a lot.

from docker-znc.

Agreed and understood about the build tools causing inflation in size. However, docker-mods seem like an inflated way to drop any custom znc module into the znc program and getting it to work. Docker mods would be one off for each module.

Performing the function in Issue #29 would render the need to create a docker mod, unneeded. I am still trying to understand the concept of Linuxserver's docker-mod system to make the necessary option.

from docker-znc.

As I have no idea how the znc modules build works, I can't comment on the function of the issue you mention, other than it didn't look like there was a final solution.

from docker-znc.

I've switched to the znc official docker container - as the benefits of having the build process work, outweigh the con of having the inflated image.

from docker-znc.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from docker-znc.