Operations grimoire/WordPress: Difference between revisions
From Nasqueron Agora
(Created page with "Plan to create a WordPress SaaS is documented at [https://devcentral.nasqueron.org/T1685 T1685]. Currently, only credentials are managed by the saas-mediawiki role, ie it allows to generate wp-config.php. If you need a WordPress site, blog or more sophisticated, review T1685 plan, and if you agree with the plan, we can implement that quickly. == Add a new WordPress site == === Credentials == ;Note for multisite :If a multisite installation is used, there is nothing to...") |
(No difference)
|
Revision as of 21:03, 30 April 2023
Plan to create a WordPress SaaS is documented at T1685.
Currently, only credentials are managed by the saas-mediawiki role, ie it allows to generate wp-config.php.
If you need a WordPress site, blog or more sophisticated, review T1685 plan, and if you agree with the plan, we can implement that quickly.
Add a new WordPress site
= Credentials
- Note for multisite
- If a multisite installation is used, there is nothing to prepare, credentials are then share for all the WordPress sites from that specific multisite installation.
- Database
- Create a database on the cluster B (MariaDB). A dedicated database only for this site is recommended. See Operations grimoire/MySQL.
- WordPress secrets
- Configure pillar/saas/mediawiki.sls, then use rOPS: utils/vault/wordpress-provision-secrets.py with the path given as secrets argument in the pillar to populate the needed secrets (8 for WordPress 6.2).
