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
The documentation on installing the database on a different server is light. My impression is that it's only intended that this module supports the web machine, not that it also run on the db machine?
I've been looking in class wordpress::db (I realise that's not documented in README.md, so perhaps I should not consider it to be part of the external API?)
wordpress::db is simple enough, so I thought I'd just call it on the db server, but then I realised that the way 'db_host' is used for the mysql_user and mysql_grant resources, it actually refers to the IP of the client system, not the host that the db is on. That surprised me, but by providing the name of the web host there, it looks like it would still work. However, the module 'require's wordpress::app, which clearly means it can't be used on the db host in it's current form.
It appears that I'm looking beyond the usage that's been contemplated to date, so consider this a feature request.
The text was updated successfully, but these errors were encountered:
The documentation on installing the database on a different server is light. My impression is that it's only intended that this module supports the web machine, not that it also run on the db machine?
I've been looking in class wordpress::db (I realise that's not documented in README.md, so perhaps I should not consider it to be part of the external API?)
wordpress::db is simple enough, so I thought I'd just call it on the db server, but then I realised that the way 'db_host' is used for the mysql_user and mysql_grant resources, it actually refers to the IP of the client system, not the host that the db is on. That surprised me, but by providing the name of the web host there, it looks like it would still work. However, the module 'require's wordpress::app, which clearly means it can't be used on the db host in it's current form.
It appears that I'm looking beyond the usage that's been contemplated to date, so consider this a feature request.
The text was updated successfully, but these errors were encountered: