You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to change how database migrations are handled. Currently, we have the (brilliant) custom migration tool that you built, @PeterUpfold. The problem is, it's relatively inflexible, particularly i/r/t URLs.
I would love to see this functionality actually pulled out of wpframe entirely, and relegated to a purpose-built tool or dedicated Python "app" or RubyGem that works alongside wpframe without necessarily depending on it. Perhaps it's as simple as tweaking the Python app so it can be easy_install'ed and work independently of wpframe.
I'm still thinking over the best way to accomplish this, but I want to add an idea into the mix:
Suppose we migrate this tool to Ruby (or adapted an existing tool; there are many) and merged it into the vpmframe gem. This would be an easy way to keep the tool easily available, and without creating an additional project to maintain.
I'd like to change how database migrations are handled. Currently, we have the (brilliant) custom migration tool that you built, @PeterUpfold. The problem is, it's relatively inflexible, particularly i/r/t URLs.
I would love to see this functionality actually pulled out of wpframe entirely, and relegated to a purpose-built tool or dedicated Python "app" or RubyGem that works alongside wpframe without necessarily depending on it. Perhaps it's as simple as tweaking the Python app so it can be easy_install'ed and work independently of wpframe.
The wp-cli wiki has a page listing some search/replace migration tools. Some of these may be useful to us and may serve to inspire us.
The text was updated successfully, but these errors were encountered: