-
Notifications
You must be signed in to change notification settings - Fork 124
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
"deploy.after_build" - stops/cancels out "after_build do" #20
Comments
Ah, good find! I'll have a look. Thanks. |
Works for me. :( |
Hmm.. I'll take another look. Are you using FTP deploy or Rsync? or would not that make a difference? |
I tried FTP and rsync. Both work. For example, please see: https://github.com/tvaughan/tvaughan.github.com/commit/8174022ea94bf409ce77c18b12b52e999553a70f [1]
[1] ftp.example.com points to a test vm. I set the hostname in /etc/hosts. That's a valid setup. |
I removed deploy from the after_build hook in the latest release (v0.1.0). I added it simply because I could but that workflow doesn't make any sense, not all builds are meant to be deployed. Let me know if this causes you any grief. |
I was doing a HTMLBeautification after build with "after_build do" like so:
but that never runs/fires if I have: deploy.after_build = true set for middleman-deploy. Sorry to throw a spanner in the works. I just thought I'd raise it as it might crop up for a few people.
cc: @tdreyno
The text was updated successfully, but these errors were encountered: