Title: Setting up development environment on WordPress
Last modified: May 19, 2017

---

# Setting up development environment on WordPress

 *  [Denis Žoljom](https://wordpress.org/support/users/dingo_d/)
 * (@dingo_d)
 * [9 years ago](https://wordpress.org/support/topic/setting-up-development-environment-on-wordpress/)
 * I’ve read [this](https://github.com/studio24/wordpress-multi-env-config), [this](https://developer.wordpress.org/themes/getting-started/setting-up-a-development-environment/)
   and even [this](https://codex.wordpress.org/Running_a_Development_Copy_of_WordPress),
   but none of them really help with sort of seamless integration of WordPress development
   process.
 * What I mean is – imagine you are working on a big project with a team of people.
   Ofc you use versioning (say github), and have a repo posted where everyone is
   working on. You have master, development, staging and bunch of other branches,
   but the first three are your main concern.
 * Say you’ve already deployed your product and now a new update comes out. First
   you’ll work locally, then push it to dev. After tests pass, this can be pushed
   to staging, where client will be able to test the site. If all of that passes,
   you can deploy this to a live server and safely update the site.
 * Is it possible to have a script that runs either on Semaphore or Travis CI so
   that you have automatic deploying without much fuss (say staging to production)?
 * The first link I added seems like a great way to have this separation, but the
   problem is deployment – especially on production – and especially the database.
 * What is the best way of solving this issue? Writing your own scripts? Doing all
   this manually?
 * So far I’ve only worked for small clients, so I’d just develop locally on my 
   vagrant and then migrate it all by hand using a search and replace script.
 * But I’d like to streamline this process.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [Kayless](https://wordpress.org/support/users/kayless/)
 * (@kayless)
 * [9 years ago](https://wordpress.org/support/topic/setting-up-development-environment-on-wordpress/#post-9149476)
 * Hey,
 * Have you looked into Pantheon? I think it does some of what you need with it’s
   built-in dev, testing and live environments…
 * [https://pantheon.io/features/wordpress-hosting-on-pantheon](https://pantheon.io/features/wordpress-hosting-on-pantheon)
 * I used them a while back for a Drupal site and the whole process is pretty impressive
   🙂
 *  Thread Starter [Denis Žoljom](https://wordpress.org/support/users/dingo_d/)
 * (@dingo_d)
 * [9 years ago](https://wordpress.org/support/topic/setting-up-development-environment-on-wordpress/#post-9149784)
 * I’m looking at more general solution. I cannot dictate what hosting the client
   is going to have 😉
 *  [Dion](https://wordpress.org/support/users/diondesigns/)
 * (@diondesigns)
 * [9 years ago](https://wordpress.org/support/topic/setting-up-development-environment-on-wordpress/#post-9153579)
 * Pushing new files to a client site would be problematic. If the client server
   doesn’t run PHP as the user who owns the WordPress installation directory, you
   would have no way to add files.
 * If you could dictate that the PHP SAPI be a FastCGI handler (perferably PHP-FPM),
   then you could write a simple plugin that uses wp-cron to check your server for
   package updates. The plugin could use a POST request that contains info to identify
   the site, and your server would respond accordingly.
 * It could even be written as a standalone script if you were able to install a
   CRON task on the client site.
 *  [Maciek Palmowski](https://wordpress.org/support/users/palmiak/)
 * (@palmiak)
 * [9 years ago](https://wordpress.org/support/topic/setting-up-development-environment-on-wordpress/#post-9185513)
 * Hi Dingo-d
 * At our company we are using buddy.works for GIT and deployments. As buddy works
   is Docker based we also use docker for local development.
 * Read [https://buddy.works/guides](https://buddy.works/guides) – there are many
   practical info which you can use.
 * In our workflow buddy.works gives us:
    – git hosting – pipelines for running 
   node/gulp/composer etc – it’s important, because we use bedrock and sage – pipelines
   for running backups – pipelines for testing is the website up

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Setting up development environment on WordPress’ is closed to new replies.

## Tags

 * [development](https://wordpress.org/support/topic-tag/development/)
 * [environments](https://wordpress.org/support/topic-tag/environments/)
 * [versioning](https://wordpress.org/support/topic-tag/versioning/)

 * In: [Developing with WordPress](https://wordpress.org/support/forum/wp-advanced/)
 * 4 replies
 * 4 participants
 * Last reply from: [Maciek Palmowski](https://wordpress.org/support/users/palmiak/)
 * Last activity: [9 years ago](https://wordpress.org/support/topic/setting-up-development-environment-on-wordpress/#post-9185513)
 * Status: not a support question

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics