Git Workflow: DEVELOPMENT > PRODUCTION
Many developers use git these days when working on a website or webapp. It would be great if Plesk supports a simple deployment workflow:
Example when using two branches:
Branch "development" will be automatically deployed by Plesk to /var/www/vhosts/example.com/dev.example.com => connected to https://dev.example.com
Branch "master" will be automatically deployed by Plesk to /var/www/vhosts/example.com/httpdocs => connected to https://www.example.com
What about database connectivity?
When using different databases for development and master you should not include your "database-connection.ini" into git but manually store it in the designated directory and edit via Plesk File Manager for example.
What about access restriction?
You can use .htaccess file for development:
deny from all
allow from <your ip>
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
Workaround: Add the repo a second time, change "Repository name" (otherwise it will tell you it already exists), change branch, change deploy path. Done.
I'm trying to actually use Plesk's Git extension in prod for the first time and I find it's absolutely useless as it doesn't support this feature.
Using a dev / master branch is the very basic of Git.
Please support this feature ASAP.
Andrey Chursin commented
Paul Hermans commented