vagrant integration, splitting into multiple instances #4
Conversation
| include_recipe "mysql::server" | ||
|
|
||
| mysql_bin = (platform_family? 'windows') ? 'mysql.exe' : 'mysql' | ||
| user = "'#{db['user']}'@'#{db['host']}'" | ||
| user = "'#{db['user']}'@'%'" |
There was a problem hiding this comment.
why do you allow access from all server? is it secured?
There was a problem hiding this comment.
Good point, I will limit the access to same subnet only.
There was a problem hiding this comment.
ideally would be to give access only for those hosts, that need that access (app servers)
|
couple of questions more:
|
| :upstream2 => node['wordpress']['app2']['host'] | ||
| ) | ||
| action :create | ||
| end |
There was a problem hiding this comment.
what if you change your template (configuration for nginx), how nginx will now about new configuration?
There was a problem hiding this comment.
I guess when this solution is deployed in a chef environment (chef server and clients), the chef-client will run periodically and check if nginx configuration is up to date with the recipe. Am I right?
There was a problem hiding this comment.
No, you could run it on production once a week. on development each day
erth111
changed the title
No description provided.