Replies: 2 comments 3 replies
-
|
I don't know if this is desired for ddev (I suspect not), but you might consider using https://github.com/Automattic/go-search-replace instead of the wp cli search-replace command. It handles serialized arrays and more. And is faster. You'd have to export/dump and re-importthe db though |
Beta Was this translation helpful? Give feedback.
-
|
I like the concept @hirasso, we're always interested in how to improve the WP integration. I suspect this is a little too intrusive for actions that DDEV likes to take. We'd be happy to change the configured URL, but it would be pretty intrusive to do the Note that your life will be a bit easier by specifying the alternate port explicitly with something like |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I used to have all my WordPress projects running on Laravel Herd but am slowly migrating them to ddev. But Herd is still blocking my default ports (80, 443). So anytime I start one of my ddev projects, it get's a random port assigned:
To make it simpler to work with this mechanism, I've developed this little script that keeps my WordPress URL synced to whatever the current flavor of
DDEV_PRIMARY_URLis:I'm running the script automatically each time ddev starts. In
.ddev/config.yaml:Now my WordPress URLs are now automatically in sync with whatever DDEV is currently using, weeeeh :)
I'm wondering if this would be something worth adding to the default ddev integration for WordPress?
Beta Was this translation helpful? Give feedback.
All reactions