# Wp-config.php differences between DevKinsta & MyKinsta

**URL:** https://community.kinsta.com/t/wp-config-php-differences-between-devkinsta-mykinsta/2073
**Category:** Application Support
**Created:** [February 22, 2023, 2:51pm UTC](https://community.kinsta.com/t/wp-config-php-differences-between-devkinsta-mykinsta/2073 "2023-02-22T14:51:48Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Agus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/agus/32/1515_2.png) [@Agus](https://community.kinsta.com/u/Agus)
#### Post date: [February 23, 2023, 1:20am UTC](https://community.kinsta.com/t/wp-config-php-differences-between-devkinsta-mykinsta/2073/2 "2023-02-23T01:20:23Z")

</div>

Hello Matt 🙂

When pulling (import) the site from MyKinsta to our local computer, DevKinsta would indeed automatically change the DB settings (`DB_HOST` to _devkinsta\_db_ , `DB_NAME` to its site DB name , `DB_USER` to _root_, and `DB_PASSWORD` to its _root DB password_) in the `wp-config.php` file - that would match with the “_Database_” details on the “_Site info_” page in DevKinsta.

We can also see this _action_ in [the application log file (`main.log`)](https://kinsta.com/knowledgebase/devkinsta/error-codes/#viewing-the-application-log-file) - such like this for example:

> [2023-02-23 07:35:33.449] [info] [dockerUtil/getContainer] Get ‘devkinsta\_fpm’ Docker container  
> [2023-02-23 07:35:34.076] [info] [containerExec] **Command ‘cd /www/kinsta/public/yoursitename && wp --allow-root --skip-themes --skip-plugins config set DB\_HOST devkinsta\_db && wp --allow-root --skip-themes --skip-plugins config set DB\_PASSWORD \*\*\*\*\*\* && wp --allow-root --skip-themes --skip-plugins config set DB\_USER root && wp --allow-root --skip-themes --skip-plugins config set DB\_NAME Your\_Site\_Name’** on devkinsta\_fpm finished with exit code 0

then also, when pushing the local site (from DevKinsta) to MyKinsta (either to Premium Staging or Standard/free Staging), DevKinsta would automatically perform the WP CLI to set/update those DB settings (in `wp-config.php` file) back to match with the DB host/settings/credentials we have in MyKinsta.

In the `main.log` file, we can see such action like this as well for example:

> [2023-02-23 07:37:32.625] [info] [dockerUtil/getContainer] Get ‘devkinsta\_fpm’ Docker container  
> [2023-02-23 07:37:32.713] [info] [ProgressIndicator] { isFailed: false, isOpen: true }  
> [2023-02-23 07:37:32.756] [info] [ProgressIndicator] { isFailed: false, isOpen: true }  
> [2023-02-23 07:37:33.668] [info] [containerExec] Command ‘ **ssh siteusername@35.xxx.xxx.xxx -p 54643 -o “UserKnownHostsFile /dev/null” -o “StrictHostKeyChecking no” -o “PasswordAuthentication no” -o “ChallengeResponseAuthentication no” 'cd /www/siteusername\_707/public && wp --allow-root --skip-themes --skip-plugins config set DB\_HOST localhost && wp --allow-root --skip-themes --skip-plugins config set DB\_PASSWORD \*\*\*\*\*\* && wp --allow-root --skip-themes --skip-plugins config set DB\_USER sitedb && wp --allow-root --skip-themes --skip-plugins config set DB\_NAME sitedb** ’’ on devkinsta\_fpm finished with exit code 0

I’m not sure how you and/or your coworker would be working on your site (created in DevKinsta) on GitHub - as DevKinsta doesn’t have an integration with GIT (or GitHub) currently and we won’t be able to provide support for that.  
I could only tell how the default process works (import/pulling and pushing site) in DevKinsta as explained above. Perhaps based on the information above maybe your coworker (or your developers) have some ideas or workaround to get it work on GitHub 😃

Cheers,  
Agus

---

_[View the full topic](https://community.kinsta.com/t/wp-config-php-differences-between-devkinsta-mykinsta/2073)._