• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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