I’ve setup a nice local dev environment using Valet, everything works. I’m tracking the wp-content folder with git (this seems to be the recommended approach, right?)
Now. As I’m developing the site, I create a lot of bogus posts and stuff like that, just to test functionality. So, at first, it seemed obvious to me that, to deploy the site, I would have a fresh, empty database on the the production server.
However: the settings seems to also be stored in the database, in the wp_options table. So, if I change things like the permalink structure, and want it to be reflected on the production site, it seems I have to also push my dev database.
Is that correct? I have to cleanup the databases of test content before pushing to keep my options intact? Am I missing something here?
The ideal case, I guess, would be to have a local database with whatever junk I want, and a dev database with the actual content. And I would be able to make changes in my dev environment and push them to production without overwriting the database data. Is that possible?
Thanks!
[ad_2]