LocalWP, GitHub, and WP Engine – Why is this development flow so complicated?

[ad_1]

Hi everyone. I'm the web manager at a company that uses WordPress. Although I'm the only dev, other non-devs in the company upload blog posts and make small front-end changes, so I need to set up version control.

My knowledge and experience with git are mediocre, so I've found this process much more daunting than other CMSs like Shopify. Local's help docs have an article about connecting GitHub to Local, but it only provides information on deploying to Flywheel, not WP Engine. I have tried deploying my files to WP Engine via Git Push with no luck.

This is clearly a skill issue, I'm aware of that, but I had hoped to find one single guide to establishing this workflow. It just doesn't seem to exist.

Perhaps I should use a different workflow? Any help would be appreciated!

[ad_2]
10 Comments
  1. Git is basically its own thing you don’t have to use any integration with local just use git commands on the folder for the local project.

    Another issue is that WordPress does things in database and database on server isn’t a file that can just be replaced

  2. WPengine having staging and dev environments, unlimited back ups, and simple upload options from Flywheel local. Why not skip Git and work with one of those options?

  3. Wait wat.

    I use all those tools and is incredible easy.

    Just use the LocalWP integration with WPEngine to update your LocalWP, and then sync your local files with GitHub. Or other other way around.

  4. You are not required to use any external tools other than an FTP connection to manage your WP website. However, the tools you mention help to avoid errors in production.

    If you don’t want to use GIT you can use manual backups, on a small site this shouldn’t be a problem, unless you have 10 devs making changes all day.

  5. You should follow WPEngine specific documentation: [https://wpengine.com/support/git/](https://wpengine.com/support/git/)

    Also, use a basic setup, and just do `git add, git commit, git push`, then setup Github actions to deploy changes when the master/main branch changes.

  6. Don’t tell me you have the entire WordPress site on GitHub with its core files

  7. Just get a $5 hosting account at a mainstream provider for dev and develop there before moving to prod.

  8. If you’re building custom themes or plugins, use Git for version control of files. It’s a crucial skill and tool. But when you make changes to content or settings on a WordPress site, those changes are stored in the database, and those changes won’t and shouldn’t be tracked by version control.

  9. On top of what many people said here, reach you it to customer support.  It’s some of the best in the industry so they should be able to point you in the right direction.

 

This site will teach you how to build a WordPress website for beginners. We will cover everything from installing WordPress to adding pages, posts, and images to your site. You will learn how to customize your site with themes and plugins, as well as how to market your site online.

Buy WordPress Transfer