-
Notifications
You must be signed in to change notification settings - Fork 170
[nextcloud] Including imagemagick extension? #133
Comments
I didn't want to integrate this extension because of many security issues in the past. |
I am building |
I see... I don't have an explanation for now. |
I've tried it on my kubernetes cluster (CoreOS) and locally on boot2docker. Same issue, you can trigger the |
I just built |
did you try |
My bad. Just tried running before but I can confirm Can you try to compile from https://github.com/mkoppanen/imagick ? I'm going to bed so I don't have time right now. |
Imagick is used for previews in Nextcloud. It would be very nice to also have this in your image @Wonderfall. Maybe only as an option? If not, can you show an example of the best way to build upon your nextcloud image for extra php extensions. |
Mh, is imagick actually used by Nextcloud? I was not sure about that, though the documentation says it is. A way to add imagick would be to add |
@Wonderfall Yes, I wasn't aware of that too. If you see here: https://github.com/nextcloud/server/search?utf8=%E2%9C%93&q=imagick&type= |
hi, i think weikinhuang was right that alpine and imagick combined had some bugs, but i think they have been fixed. giving the build another try gave me a working wonderfall/nextcloud build with imagick enabled. theming works now as well. Tobias. P.S. I also think to nake in a config option to switch imagick off. I personally need the imagick module only during theming setup. once that is done the module could be switched off as far as i am concerned for my usecase. |
I've tried to add it to the build with:
However everytime php runs (cli and fpm), I get a segmentation fault. Any help would be appreciated.
The text was updated successfully, but these errors were encountered: