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

differential assets loading #48

Open
digitall-it opened this issue Nov 18, 2016 · 5 comments
Open

differential assets loading #48

digitall-it opened this issue Nov 18, 2016 · 5 comments

Comments

@digitall-it
Copy link

Feature request: ability to only perform differential uploads and downloads via rsync. This would speed up asset syncing if done frequently. We all understand that even if this is not an edge use case, and that better suited tools exists for that scope (like Deployer), it would be nice and very useful to incorporate this functionality.

@dhensby
Copy link
Contributor

dhensby commented Nov 22, 2016

Why not just use rsync?

@digitall-it
Copy link
Author

sspak also syncs the database

@dhensby
Copy link
Contributor

dhensby commented Nov 22, 2016

you can use sspak to do the DB (that won't be incremental) and rsync for the assets?

@digitall-it
Copy link
Author

Yes, but probably that would be better suited as a proper deployer recipe.

Sspak is a good basic entry point to automated deployment and I've found out it works well if coupled with Plesk Gitman, if only it could do differential assets loading. Plesk can even detect Composer repos and update/install them as per instructions.

It could smooth out transition to something more fancy like Capistrano, Deployer, Rocketeer, that also enable to flush and dev/build.

But as more I write this answer, the more I understand that this could open up to more scope creeping that this little gem should handle on its own shoulders alone.

@dhensby
Copy link
Contributor

dhensby commented Nov 24, 2016

That's my thinking really. sspak has a very narrow scope and being a wrapper for rsync calls is not really one of them...

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

4 participants