• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Where to store private / 'non public' files to survive a Plesk Migration?

M

metareason

Guest
I have been using plesk for a while and it is great - however I now need to move to another server with plesk using the migration manager and it is missing some files each time.

Due to regularly changing code and the desire to roll back changes quickly - I delete my httpdocs folder and symlink it to the current exported tag for a site - my problem is where to store this tagged data so it survives a Plesk Migration

Currently I put the files for a version of a site in /var/www/vhosts/mysite.com/releases/TAGID.

Then soft symlink /var/www/vhosts/mysite.com/httpdocs -> /var/www/vhosts/mysite.com/releases/CURRENT-TAG

However the releases directory does not get transferred during a plesk migration

My question is:
Where can I store my 'releases' data so it is transferred with each Plesk Migration?

(note the 'private' directory seems to be too heavily secured to use)
 
Back
Top