• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Input Git - support for deploying releases/tags

pleskuser67553

Basic Pleskian
It would be helpful if the Git extension UI could deploy up to a certain release or tag. Perhaps a drop-down in "Change branch and path" that lists available tags. E.g. git checkout v1.2.3. I'm somewhat of a novice when it comes to Git, so I hope that makes sense.
 
+1

this is a must have feature. Today we have the repo two times on the server and must push to two different origins to deploy live or staging.
Expected is:
Push with tag "live" deploy to www.example.com
Push with tag "dev", deploy to staging.example.com
 
+1
This would be really helpful to have. the alternative of having eternal branches doesn't seem best practice (ie a branch names "staging")
 
Back
Top