You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
As many points are configured for a single wordpress site, i'd like to know how to correctly purge the server about any configuration for a site I want to remove / delete from the server (webroot folder, nginx vhosts configs, unix users, fw rules, databases, varnish config,.... )
The text was updated successfully, but these errors were encountered:
As I can discover by parsing the roles, a complete configuration for a site consists in :
unix user accounts
database
fail2ban rules
webserver (nginx) config & vhost
php config and fpm pool definition
pki / ssl generation and configuration
redis configuration
varnish cache setup for the vhost
wordpress setup
am I complete with this listing ?
I have noticed that if I remove some sites from the inventory/hosts :
all the configuration seems to remains (which appears a normal behavior as I did not explicitely told debops to clean old config),
but all old sites cannot connect to their database anymore.
I believe thid kind of site deletion could be initiated with an argument like 'state=absent' in their inventory/host line, then we could initiate a global 'debops wordpress' run, or even narrow it with 'debops wordpress --limit DOMAINTOREMOVE'
Hello there.
I followed this guide
https://github.com/carlalexander/debops-wordpress/wiki/How-to-configure-multiple-WordPress-sites-on-a-single-server
to manage multiple wordpress sites on a single server.
all wordpress sites on the server are defined through a dns wildcard pointing to the server's ip:
As many points are configured for a single wordpress site, i'd like to know how to correctly purge the server about any configuration for a site I want to remove / delete from the server (webroot folder, nginx vhosts configs, unix users, fw rules, databases, varnish config,.... )
The text was updated successfully, but these errors were encountered: