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

speedify suggestion #23

Open
dncastilho opened this issue Jul 10, 2018 · 2 comments
Open

speedify suggestion #23

dncastilho opened this issue Jul 10, 2018 · 2 comments

Comments

@dncastilho
Copy link

regular cap deploys are smart enough not to do much if there isn't much to be done - i.e. when the process gets to the compile phase, it actually doesn't change any of the assets that were previously generated.

with this gem, there's always a big rsync phase, even if no assets changed - it copies a lot of files across. it would would be great for this to be similar to the original cap deploy, and not have much to do if no assets changed.

@joshua5201
Copy link
Contributor

maybe this can be fixed by not removing public/packs and public/assets before the task?

@toymachiner62
Copy link
Collaborator

PR Welcome

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

No branches or pull requests

3 participants