Some sites have a lot of uploads. And to do development changes it’s not always necessary to have them all download.
So allow folks to pull the code down, but skip uploads – potentially even proxying it so requests for media from the upload directory will get http redirected to the environment that it was pulled from.
This could turn an hour long pull into a much much shorter option, and not get it people’s ways when they want to connect to a client site.
I suppose this could mostly be addressed by adding wp-content/uploads to .wpe-push-ignore and .wpe-pull-ignore by default, but I don’t see any options to preload those before doing the first pull.
I think you could accomplish the same @daljo628 if you create a new, blank site first and then go to the Pull tab in the bottom right corner and use MagicSync to deselect Uploads from the site you want to pull over top of it.
Interesting, thanks for the suggestion! It feels kinda kludgy though, versus the main way of pulling down sites, but I get it.
I wonder if it’d be doable via an add-on, and also integrate Bill Erickson’s GitHub - billerickson/BE-Media-from-Production: Uses local media when it's available, and uses the production server for rest.
You’re right, it’s definitely some extra steps @daljo628! I’ve passed your request along to the Local Dev team to get some more eyes on it. Thank you for sharing!
