This outlines WordPress-focused features that would make Ploi.io the go-to platform for developers and agencies managing multiple WP installs.
As it stands, ploi is great - but i feel the below would add a huge advantage over the competition. This list is not exhaustive but i feel would be a great starting point.
WordPress Config
Installation
I think this could be expanded on - maybe transition installation and config using wp-cli
- wp core download
- wp config set db etc
- wp core install
- --url={pulled from site}
- --title={pulled from free text field in ploi}
- --admin_user={pulled from free text field in ploi}
- --admin_password={automatically generated, but pulled from text fiels}
- --admin_email={again - pulled from field (maybe default to ploi user?}}
- ability to run custom wp cli copmmand afetr install?
General
- Ability to see version info on general tab? https://roadmap.ploi.io/projects/3-panel-requests/items/1105-show-project-laravel-wordpress-etc-version-on-the-sites-list
- Theres some other useful info available that could be displayed in the dashboard.
- Run custom wp-cli commands
- Per site resource metrics would allow the ability to find a site that is being hammered. requency tied to Ploi’s existing check intervals.
- Ability to quickly enable and disable WP debug. and add that log file to the logs section on the site panel.
- One-click login. but this will probably need a mu-plugin. (not too important
- WP Cron can be triggered using wp-cli - related https://roadmap.ploi.io/projects/2-site-level-requests/items/607-option-for-run-wordpress-cron-with-wp-cli
Staging / Templates / Cloning
- Ability to clone a wordpress site (use wp db export to dump the db in the clone) wp search-replace for handling of url changes.
- Ability to create a staging site using a similar method (making sure no-index is set)
- The above would allow the creation of a blueprint / template site. Maybe could be marked in a templates section in ploi.
- cross server cloning would be helpful.
See - https://roadmap.ploi.io/projects/2-site-level-requests/items/939-clone-wp-incl-database
Caching
- consider use of nginx helper plugin installation and config in ploi
- adopt WP_REDIS_PREFIX per site to avoid wp_ conflicts
both above should be achievable using wp-cli as well
Security
- Integrate with Wordfence Threat Intel API (free for commercial use).
- Flag outdated/insecure plugins/themes.
- Periodic wp core/plugin verify-checksums
- 7g/8g firewall https://perishablepress.com/8g-firewall/ works with all sites, not just WP
- Ability to quickly enable / disable xml-rpc
- fail2ban integration with wordpress rules
- support for editing wp-config.php files that are placed outside the webroot directory. https://roadmap.ploi.io/projects/3-panel-requests/items/1192-wordpress-support-for-wp-configphp-outside-webroot
Backups
Although more server level, WP DB and files would ideally be saved in a single archive. this could be simplified by allowing a custom command to be run before and after backup. Or maybe a checkbox that will run a wp db export whatever.sql then remove after??? On restore - the db would have to be re-imported, then the file deleted.
WordPress updates
- Ability to see outstanding updates and update wither wp, plugin, or theme etc.
Thats off the top of my head - i have tried linking existing roadmap items where poss.
Apologies for any terrible markdown formatting :/
- WP-CLI Search and Replace - also for Elementor
EdwardG added some extra features that would be helpful that I probably missed...
- Staging with a custom domain
- PHP settings to change per site from the panel (This is possible, but require knowledge of php config files), a few simple fields (on the site level) like execution time, input time, input vars, memory limit, post max size, max upload, session garbage collection time, php worker count.
- We have FastCGI cache clearing per site, but Redis / opcache per site would be very handy
- ModSecurity implementation
Thanks again Edward - lets keep this conversation going.
Would love to help test any steps in this direction. We still use Gridpane because of the cloning and simplicity of full WP support and I'd love WP to feel as integrated as laravel does on Ploi
Most of the key features have already been mentioned here. I would be super happy to help test anything if this starts moving forward. Would be a huge relieve to have all of our websites managed through ploi.