-
Notifications
You must be signed in to change notification settings - Fork 59
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
Added support to limit synching to specified directories #80
Conversation
Adds 'local_uploads' and 'remote_uploads' vars and ':uploads' task to both ':up' and ':down'
Man, you're right on. I usually don't care about anything but those. I do think that perhaps we should pivot off of shared. |
I tried making this work as a one line rsync like this:
but the only issue is rsync removes the parent directories of the source, so without appending The other option would be to loop through each key in
What do you think? |
Went ahead w/ the second option. I've tested it on a few projects and it seems to be working just fine. |
Bah! Just realized this doesn't work with staging/production as the |
Temporarily closing so this isn't merged by accident. |
Avoids any issues w/ dir overlap in remote/local_web vars and shared_children vars
You can leave it open, and just put [RFC] or [WIP] in the title for clarity... |
Cool. I changed to a dedicated "rsync_limited" var to avoid the issue w/ duplicate dirs in "shared_children" and "remote/local_web". Thoughts? |
* master: (43 commits) Install tasksel Add auto_correct to Vagrantfile Default WordPress to latest, then 3.7.1 Bump to v0.2.41 Bump to v0.2.40 Simplified wp cookie regex (based on cookie regex we're using in production.vcl) Removed some version changes that shouldn't have been there (part of the revert) Switch from 0.2.* to ~0.2.36 versioning Forcing minimum MaxClients value of 5 Fixed underscore cookie match in varnish vcl Revert rollback of v0.2.38 Bump to v0.2.39 Bump to v0.2.38 Bump to v0.2.37 Bump to v0.2.36 Add more detail to v0.2.35 Bump to v0.2.35 Move events from after deploy:update Bump to v0.2.34 Added Vagrant troubleshooting in README ...
I've thoroughly tested this on both existing Genesis setups and site conversions and it's been running like a champ. Let me know if you figure out some way to test these types of tasks and I'll make an attempt at writing some. |
* master: (21 commits) Remove genesis version Remove debug code Fix hosts addon console.log(browser.html()); sudo mkdir Symlink web to /vagrant/web Debug mode Correct bower install bower install in test/temp Install latest genesis-wordpress branch Install tasksel Install before generation NPM install Install bower sudo provision me a sandwhich Working functional test Add travis-ci badge Add .travis.yml Initial mocha test Force sourceRoot ...
@ericclemmons @jimmynotjim should we merge this down and start using it? It looks like it's been lurking here for months. |
I've just been waiting for someone to give the 👍 I've tested it on multiple projects and it works great. |
I think we can merge this down safely for now. For |
Sooo....this going to get merged down? |
Monthly reminder... |
Added support to limit synching to specified directories
Whoohooo. Now to update projects to use it. |
See #63
rsync_limited
var:limited
task to both:up
and:down
NOTE: Rather than change the functionality of the current
:files
task I thought it better to add an:limited
task to synch the directories specified (with/uploads
as the default). This is really useful when converting really old sites with lots of cruft over to Genesis.To test on a Genesis project run
and select the branch when prompted.