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

build / pre-compile creating unwanted files #33

Closed
colinmccann opened this issue Feb 20, 2017 · 6 comments
Closed

build / pre-compile creating unwanted files #33

colinmccann opened this issue Feb 20, 2017 · 6 comments
Labels

Comments

@colinmccann
Copy link

Something in the build process seems to re-gen this file:
_assets/img/transparency/DataPrivacyTransparencyofCanadianISPs-2013.pdf

I can keep deleting it, but obviously that's not optimal. Anyone with more competency know why this is going on?

@dcwalk
Copy link

dcwalk commented Feb 21, 2017

This should be addressed here: 1c37f1b

Basically during grunt build it monitors the img directory for changes and updates from __src, (https://github.com/ixmaps/website2017/blob/master/_assets/__build/Gruntfile.js)

Please test!

@colinmccann
Copy link
Author

Makes sense. Can you explain to me the intended flow here? I'm making changes directly to eg the _assets/img directory (eg adding a file). Is it preferred to make changes in __src and let the build update as required?

@dcwalk
Copy link

dcwalk commented Feb 22, 2017

Um, yeah I think you want to continue to take advantage of grunt watching/compiling scss/optimizing img sizes/serving php for testing changes locally and building. It should be documented maybe more clearly that you are expecting people to use that process (and my descriptive text in the README is maybe misleading.

So: those things watched should go to __src first (including images)

@colinmccann
Copy link
Author

colinmccann commented Feb 23, 2017 via email

@dcwalk
Copy link

dcwalk commented Feb 23, 2017

Answered on separate email thread. I think some confirmation on from @jknee on what expectations were could help guide our process?

@dcwalk
Copy link

dcwalk commented Mar 16, 2017

Closing this as it was addressed in #40 and also #41, which both have landed. how about we open up new issues if/as the issues recurs?

@dcwalk dcwalk closed this as completed Mar 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants