• 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!
  • 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.

Question GIT extension: Same repository, deploy different branches to different subdomains

B_P

Regular Pleskian
Hi all,

On my Plesk Onyx installation, I am using GIT to manage one specific subdomain sub.example.com using a local repository as explained at Using a Local Repository. The automatic deployment uses the master branch and deploys changes into the folder /sub.example.com. The docroot of sub.example.com is set to /sub.example.com/public.

For the testing branch of that repository, i would now like to set up a second subdomain sub-testing.example.com, where all changes to that branch are automatically deployed to. Unfortunately, the GIT settings for sub-testing.example.com only allows to either use a remote repository or create a new local repository. What I would like to do instead is of course to use the existing local repository but use the testing branch. Does anybody have an idea how one should do this?
 
Back
Top