• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

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