which MySQL tables to skip when pushing staging to production?
- This topic is empty.
- You must be logged in to reply to this topic.
May 2024 only! Join our Discord free of charge.
Because we decided to abandon any sort of PHP script for pushing staging to production in SlickStack for a variety of reasons, I am going to save this previous research here for future reference.
Below are some of the database tables you probably should never merge when pushing a WordPress or WooCommerce staging site to production:
wc_download_log
wc_product_meta_lookup
wc_reserved_stock
woocommerce_sessions
woocommerce_order_items
woocommerce_order_itemmeta
woocommerce_payment_tokens
woocommerce_payment_tokenmeta
woocommerce_log
wp_commentmeta
wp_comments
wp_usermeta
wp_users
Related thread
I had not even considered about this before..
Wait
so does SlickStack allow for merging the stating site into production or not?
Friends, the time has come for us to ask for your financial support. After 5+ years of (growing) expenses, and taking time away from consulting and services, we must start generating donations in order to continue this level of rapid project development. Please consider donating, so that we can keep SlickStack free and open source. Thank you! 🙏 😍
We champion core values like free speech, transparency, and portability, and welcome anyone else who does too.
Here is a non-exhaustive list of plugins, themes, and other services that we recommend checking out.
Every stack script and server deployment platform is a bit different, so check to see how SlickStack compares.
Subscribe to our free newsletter to receive occassional updates, we respect your privacy and do not sell your information.
Here’s some of the incredible performance features you can expect after launching your SlickStack cloud VPS.
If you are wondering what specific problems SlickStack can help solve, browse some of the solutions below.
In lieu of donations, please show your support by mentioning SlickStack on your blog or write a review. Thank you!