Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database migrations #13

Open
chrisvanpatten opened this issue Nov 30, 2012 · 2 comments
Open

Database migrations #13

chrisvanpatten opened this issue Nov 30, 2012 · 2 comments

Comments

@chrisvanpatten
Copy link
Member

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.

@chrisvanpatten
Copy link
Member Author

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.

@chrisvanpatten
Copy link
Member Author

Still needs work, but Sequel Pro gets the job done for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant