Tim
My feedback
17 results found
-
36 votes
A user suggested a workaround on our forum: https://talk.plesk.com/threads/docker-error-permission-denied.372306/#post-938302
Maybe it helps to bridge the time until Plesk includes native Docker support for Alma 9.
-- PD
Tim
supported this idea
·
-
14 votesTim
supported this idea
·
-
6 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.—
IGTim
supported this idea
·
-
6 votes
Thank you for your feature request. We will consider the possibility of its implementation if it becomes sufficiently popular and in demand.
—
IGTim
supported this idea
·
-
38 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGTim
supported this idea
·
-
3 votes
-
25 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.—
IGTim
supported this idea
·
-
53 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.
—
IGTim
supported this idea
·
-
268 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
Tim
supported this idea
·
-
1 vote
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
24 votes
Thank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGTim
supported this idea
·
-
40 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGTim
supported this idea
·
-
2 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment -
8 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.
—
IGTim
supported this idea
·
-
20 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.—
IGTim
supported this idea
·
-
26 votes
Thank you for your input. We will consider this functionality in upcoming releases.
Tim
supported this idea
·
-
19 votes
Thank you for your input!
Could you tell us which scenarios you want to enable with this functionality?
Everyone, please continue voting for this feature if you consider it important.
— rk
An error occurred while saving the comment Tim
commented
Scenario and functionality. If a code update is committed which breaks functionality, on every other Git based CI system you can simply roll-back to the previous update.
To fix this with Plesk, you need to make an unnecessary commit or manually edit production files, ruining the point of having the automated system.
Tim
supported this idea
·
Igor to be clear, this isn't a feature request it's getting Plesk to remove the misguided change that nobody asked for.
I have no faith that Plesk will fix this, especially not based on feedback here nor will they bother if it's "popular" since the product (Plesk) currently isn't being managed by a competent PM.