Tim
My feedback
-
18 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
·
-
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
·
-
242 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 -
22 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
·
-
33 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 -
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
·
-
171 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
·
-
19 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
·
-
23 votes
Thank you for your input. We will consider this functionality in upcoming releases.
Tim
supported this idea
·
-
448 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
·
-
1,512 votes
We hear you and see a clear demand for this feature.
I want to say that implementing these features requires a lot of investment, and in 2021 Plesk team keeps focusing on the delivery of other improvements (sad, but true).
We will back to the re-evaluation of these features at the beginning of the next year.
Please continue to share your use cases and requirements, and it would really helpful if you point to existing solutions that we can review and check before implementation.
Your feedback is important to us. Thank you, everyone.
—
AATim
supported this idea
·
-
94 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.
—
IGAn error occurred while saving the comment Tim
commented
If Plesk don't have a direct replication / HA option on the cards, allowing the use of traditional methods (eg Galera + lsyncd) would be the next best thing.
Tim
supported this idea
·
-
18 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.