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
feature request: Support exclude(ignore) using .riceignore #83
Comments
This would be a great feature, currently having to manually edit my rice-box.go to remove DS_STORE files and others |
Has this been implemented? |
@at15 If you're still interested in making a PR for this, it would be very welcome. Perhaps we should try to follow the gitignore guidelines for pattern matching. |
No, please, not an ignore option, or at least also provide a include-only thing. |
@mdone-cloudian Is your .git directory in the assets box you're embedding? |
Please be patient, it will take me a couple of days until I can revisit this and give input. We're in release mode here at |
[Two months later...] Ok, the way I solved it (and I guess it was the original intended method) was to put the files in its own subdir and point |
Similar issues: #80 #37
go.rice does not support excluding files and this result in huge binary if you have folders like
node_modules
, and due to the way rice find boxes (related #47 ), it's hard to specify different box location for same box during development and production. So similar to git and docker, which has.gitignore
and.dockeringore
, a.riceignore
file can be introduced to make rice more flexible withoutchanging how rice find boxes.
The implementation in docker for
dockerignore
can be a good start, also there is a dockerignore libraryI have already tried it in my own fork in this commit. It works for append zip only, and use the library mentioned above, it works for this small project. Though the behavior is not exactly same as
gitingore
and only.riceignore
file at box root is supported.I can make a pull request if go.rice is still under development. Thanks~
The text was updated successfully, but these errors were encountered: