thomastospace, 3 months ago

@syntaxseed I think it comes down to 'there's no better way'.

When I worked on Wordpress, we had all our code in custom plugin/theme. These are versioned of course.

If we needed pages/products/etc. from production, we used WP Migrate DB Pro to pull the database without customer data.

Yes... If we needed to adjust something in the database, that happened 3 times. Locally, staging & prod. Luckily that was rare.

I haven't found a better way since. If you find it, I would love to hear about it.

gmazzap, 3 months ago

@syntaxseed Because it is extremely hard. Your script approach works up to the point you have to syncronize media, that are very coupled with DB. If your site is small enough, you can figure out something anyway. To solve that issue with big sites you need to do things at infrastructure level or go to managed hostings that have it figured out for you.

heiglandreas, 3 months ago

@syntaxseed what do you mean: staging, prod, dev... ????

🙈

iamdtms, 3 months ago

@syntaxseed Sync WP in db layer & fs with git could be enough. Handling 3 variant is an unnecessary pain, but making work with personal concept is a success.

michael, 3 months ago

@syntaxseed yeah, it's one of the main reasons why I hate working with WordPress so much. The more time passes, the more subtle differences you are going to accrue between the various environments, and it becomes almost unmanageable.

syntaxseed, 3 months ago

I started writing a #PHP cli tool to sort of do this. It takes db snapshots & imports them & uses wp-cli to search & replace paths & urls in the db.

But if your prod site isn't static, you are snookered.