Is dropping FPM-images set in stone already? #5790
-
|
Back in 2024 I made a suggestion on how the public-assets thing can be handled So is the decision on dropping FPM-images set in stone, or is it (hopefully) still viable if we get rid of the public-folder issue? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Is it my responsibility to monitor each and every response, especially on closed issues?
I am not willing to support the FPM image anymore. |
Beta Was this translation helpful? Give feedback.
-
Sure not on a locked one, and since I couldn't comment there, I used this feature here.
Thanks. I fully understand the burden of the support. My only was: If the frustration of support only stems from fixing assets, maybe resurrecting my old issue and fixing that can take away the frustration. |
Beta Was this translation helpful? Give feedback.
-
Partially. It's my job to decide for the best investment of my time. And removing that particular part simplifies the docker build massively. I will re-open the discussion, as I assume that other users will have questions as well. |
Beta Was this translation helpful? Give feedback.
Is it my responsibility to monitor each and every response, especially on closed issues?
I am not willing to support the FPM image anymore.
But I don't mind if the community provides a FPM image.