• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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