Requirements change detection fails for -r sub.pip

[lericson]

If a requirements file includes another requirements file, the app.deploy task won't figure that out. It would have to actually parse the contents to know.

[joar]

you can work around this by using a separate, standalone, file for each environmentt and point out the file to use with

settings:
  app:
    requirements: requirements-live.txt  
    # paths ending with .pip or .txt ar passed to 'pip install -r', 
    # paths ending with .py are passed to 'pyhon {} develop'.format(name)

[lundberg]

Could be done by recursive parse, but should probably be too slow since each file would needed to be fetched from server for comparison. One could instead change the -r usage the other way around, like using a master requirements file for live environment in repo root and then for dev/staging use a separate with debug-addons and a reference to the master.

[joar]

I have some progress on this in a local tree, now pushed to feature branch:
https://github.com/5monkeys/blues/tree/feature/parse-requirements

On Mon, May 25, 2015 at 9:14 AM, Jonas Lundberg notifications@github.com
wrote:

Could be done by recursive parse, but should probably be too slow since
each file would needed to be fetched from server for comparison. One could
instead change the -r usage the other way around, like using a master
requirements file for live environment in repo root and then for
dev/staging use a separate with debug-addons and a reference to the master.

—
Reply to this email directly or view it on GitHub
#2 (comment).

Joar Wandborg
wandborg.se