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

Creating an RPM package

C

cornerstone

Guest
Could anyone point me in the right direction?

I am trying to create a custom WordPress install to upload to the Application Vault. We want to install the new version of WP into this package,with prepackaged themes and plugins, as we are stuck with a broken version of 2.3.3, right now.

Is there a way to create this package easier than using Linux commands? My Linux skills are minimal and our other developer has left and took his Linux knowledge with him (He used to do the RPM builds).

Your help is more than appreciated. Please steer me in the right direction.
 
To make rpms you always need at least two tools, an editor and rpmbuild, everything else is related to building the package (compilers, interpreters, lint, etc). I haven't made any app vault rpms recently, but I'd be happy to give you pointers. I do have a basic wiki page here:

http://www.atomicorp.com/wiki/index.php/RPMS

This covers some do's and don'ts for packaging, and some specifics for app vault packages. Did you already have a src.rpm of the wordpress appvault package?
 
Back
Top