• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Detecting install / configuration

SMorrison

New Pleskian
Hi all, I am new here, and new to Plesk Panel. I have been going through the documentation (and this forum), but have been unable to find what I am looking for.

We are deploying Plesk Panel via Puppet. For the most part this is pretty straight forward using the automated install options. But I am wondering if anyone can point me to a list of files that are created, or modified, as a result of running any of the commands in /usr/local/psa/bin/? This would be useful as it would give me an easy way to check the status / progress of the install, config, and state of Plesk without having to write API calls.

For example, I know init_conf updates the DB and sets up the admin user details. But, other than /etc/psa/.psa.shadow, I haven't been able to identify any files system files that it touches. Would it be a safe assumption to say the follwing?

If /etc/psa/.psa.shadow has an encrypted password set for admin then init_conf, or web setup, has been run.

Also, if you are using Puppet and have any suggestions when working with Plesk I would love to hear from you.

Thanks...
 
Last edited:
Hi. I dont have the answer to your question, but I am very interested in your Puppet script for automated Plesk installs. Would you be willing to share it with us?

Most of the settings changed by the various binaries, APIs and scripts are saved in MySQL. Very little settings are stored on disk using files.

Perhaps a possible approach is to dump the psa database using --skip-extended-insert, and parse the dump through Augeas
 
Last edited:
Back
Top