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

Complete copy #29

Closed
matjack1 opened this issue Mar 13, 2013 · 2 comments
Closed

Complete copy #29

matjack1 opened this issue Mar 13, 2013 · 2 comments
Assignees

Comments

@matjack1
Copy link
Contributor

I think would be useful a flag to pull and push the complete WordPress tree.

This would be useful for the first deploy and then to restart working on a production site, getting all the core and plugin updates done in the meantime.

I'm proposing something like:

wordmove pull -w

and:

wordmove pull -W

for a pull/push of everything, database included

@alessandro-fazzi
Copy link
Member

I've have discussed with @mukkoo and we have a some notes about that:

  • it is essential and urgent. I said URGENT! ^_^
  • overall we think it would be better to have the -w flag push/pulling just the wp core; in other words excluding what other flag already handle. By this way we would assure a more elastic management of the site; e.g.: think you're working on a theme/plugin new feature, but you have to upgrade wp core due to important security fixes; you'll probably want to have a granular control over that, despite your git branches management.

I know that git is flexible enough to manage these situations, but I think we have to assure the minimal overhead for the dev.

Drop us a line about what you think about that

@matjack1
Copy link
Contributor Author

fixed by this pull request: #34

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

3 participants