Daniel Nephin

Ah, I was looking at the wrong branch. I've verified it works for my tags with both version `0.8` and master. You can see the tags here: https://hub.docker.com/r/dnephin/test/tags/ ``` [DEBUG]...

My release worked: https://circleci.com/gh/dnephin/dobi/486 However, I do use docker 1.10: https://github.com/dnephin/dobi/blob/master/circle.yml#L2-L4 I'm not sure if it's an issue with docker 1.9. Would you be able to try with Docker 1.10...

Good questions. I think it should be able to run from within the project directory, that would be the major reason to create a separate thing from `includes` which are...

Another possible implementation would be to make includes an object instead of just a string. That would let us include other parameters like `optional:` on the includes: ``` yaml meta:...

Another idea from https://github.com/dnephin/dobi/issues/40#issuecomment-255088427 would be to support remote http urls as the include path. `dobi` would download the file and cache it in `.dobi/includes/`. Each time `dobi` is run...

Maybe the `include` field could be either: - a list of filepaths (strings) which use the existing include logic ("fragment" style includes) - a list of objects with the structure:...

`goware/urlx` looks very cool, thanks for the link! I've needed something like that a couple times before, so I will be sure to make use of it. I agree that...

Ya, that sounds right for caching. For `optional` the use case is user overrides. I might have some personal tasks that I want to run that don't make sense as...

I like this idea!

I think it would be good to support something like this. `--dobi-file` already exists as `-f` (`--filename`). Many [fields already support variables](https://dnephin.github.io/dobi/variables.html#config-fields) and others can be added. The only thing...