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
Just thinking out loud: it might be nice if, instead of ignoring wp-config.php, this tool actually wrote to wp-config.php, updating it with the provided environment's database credentials and URLs (DB_NAME, DB_USER, DB_PASSWORD, DB_HOST, WP_HOME) during a file deploy. Since all that information is already present in-the-clear in the Gruntfile.js, why not provide a way to provide that information to the config file during a deployment?
The text was updated successfully, but these errors were encountered:
Just thinking out loud: it might be nice if, instead of ignoring wp-config.php, this tool actually wrote to wp-config.php, updating it with the provided environment's database credentials and URLs (DB_NAME, DB_USER, DB_PASSWORD, DB_HOST, WP_HOME) during a file deploy. Since all that information is already present in-the-clear in the Gruntfile.js, why not provide a way to provide that information to the config file during a deployment?
The text was updated successfully, but these errors were encountered: