There are a million different ways WordPress developers set up their environment to build a new site. Through our experience, this is the ideal set up that works for us and we think it's worth a try.

The Ideal custom WordPress Theme Setup:

  • Develop Locally using Shifter-Local
  • Migrate your DB changes and Uploads using AIO WP Migration if necessary
  • Track Theme changes via Git
  • Deploy Theme changes tracked in Git with WP Pusher

Going from Local to Develop to Production

For example, here is a quick overview and step by step of deploying your custom Theme changes.

  1. Create a new local site using Shifter-Local
  2. Install your custom Theme, develop your code and commit your changes
  3. Push changes to Github, Bitbucket, etc.
  4. Create a new site on Shifter
  5. Install AIO WP MIgration and WP Pusher
  6. Create an export from your local site with AIO WP MIgration. Select just what you need such as DB, Media Uploads, etc.
  7. Upload that backup to your newly created site on Shifter
  8. Add your custom to WP Pusher's settings, sync an and activate that Theme
  9. Test to ensure your data and theme is correct
  10. Generate a new Artifact

After the initial setup, the process is simple. From your local env, commit your new changes to Git and push. Log into Shifter and pull them down.

At this time, that process it not automated but when Shifter Webhooks become available we are hoping to add this feature.

Is this the only way?

Nope! There are so many ways that developer prefer to work and we can't cover them all here. But if you do have a suggestion, let us know and we'll give it a try and add it to the official docs.

Note regarding SFTP/FTP

Shifter does not support direct SFTP/FTP access at this time. Instead, we suggest WordPress Plugins such as File Manager or tracking with Git via WP Pusher which are supported.

Did this answer your question?