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

How can I add custom Skeleton Directories?

A

acidbox

Guest
So here is my dilema.

I am trying to make a custom skeleton for Plesk 7.5.4 and am running into an issue.

The documentation says that it will only recognize certain directories, i.e.

Skeleton file may contain the following top-level directories only:

* httpdocs
* conf
* cgi-bin
* anon_ftp
* error_docs

I need to be able to deviate from this for two reasons.

a.) I want to add some custom files to the /lib/ and /usr/ directories

b.) I want to create another top-level directory (i.e. customdir)

There has to be a way around this. Anyone know how to do this?

If not, is there a way I can get Plesk to run a custom bash script while creating a domain? That way I could write the code to put the correct files in place and plesk could just run the script after it does its thing...

Let me know :)
 
Originally posted by acidbox
If not, is there a way I can get Plesk to run a custom bash script while creating a domain? That way I could write the code to put the correct files in place and plesk could just run the script after it does its thing...

Yes... Ever checked the manual?

http://download1.sw-soft.com/Plesk/Plesk7.5/Doc/plesk-7.5r-sdk-html/docs/event_manager/index.html

The Event Manager will do the trick - look for "Physical Hosting created" and "Subdomain created"
 
Thanks I figured that part out.

One question.

When I use <new_system_user_password> in my bash script, it outputs xxxxxx instead of the actual password. Is there some way to reveal the REAL password instead of a bunch of x's?
 
Back
Top