# Additional Kinsta Constants

**URL:** https://community.kinsta.com/t/additional-kinsta-constants/1506
**Category:** Installation
**Created:** [May 26, 2022, 11:09am UTC](https://community.kinsta.com/t/additional-kinsta-constants/1506 "2022-05-26T11:09:09Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![dgilfillan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/dgilfillan/32/1122_2.png) [@dgilfillan](https://community.kinsta.com/u/dgilfillan)
#### Post date: [May 26, 2022, 11:09am UTC](https://community.kinsta.com/t/additional-kinsta-constants/1506/1 "2022-05-26T11:09:09Z")

</div>

Hi, after importing a staging site from Kinsta to DevKinsta, I notice the following at the top of the wp-config.php file:

```auto
<?php /* BEGIN KINSTA DEVELOPMENT ENVIRONMENT */ ?>

<?php if ( !defined('KINSTA_DEV_ENV') ) { define('KINSTA_DEV_ENV', true); /* Kinsta development - don't remove this line */ } ?>

<?php if ( !defined('JETPACK_STAGING_MODE') ) { define('JETPACK_STAGING_MODE', true); /* Kinsta development - don't remove this line */ } ?>

<?php /* END KINSTA DEVELOPMENT ENVIRONMENT */ ?>

```

Can you explain what this is?  
Should it only apply to the wp-config.php file in our site’s staging envrionment?  
Can/should it be removed from wp-config.php file in local dev?

---

<div class="post-metadata">

### Author: ![Kevin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/kevin/32/808_2.png) [@Kevin](https://community.kinsta.com/u/Kevin)
#### Post date: [May 26, 2022, 4:46pm UTC](https://community.kinsta.com/t/additional-kinsta-constants/1506/2 "2022-05-26T16:46:11Z")

</div>

Hi @dgilfillan, thanks for reaching out! These are added by default to all our Staging environments when they are created. When you Push the site back to a Live environment on Kinsta, those lines are removed.

Those constants are needed for functions or plugins that should be disabled on development environments.

DevKinsta doesn’t really require those lines but it doesn’t hurt to leave them either. Many plugins can already tell that a `*.local` domain is a development environment.