rmm-fcul
commented
8 years ago collect_data.py already has the --logpath option implemented. This way
is fairly explicit and would be my preferred option to use in the sandbox
generation too; if there were just one tool that depended on it. However,
looking into the deployment procedure, deploy.py needs to generate and
transfer the files, then assisirun.py needs to execute the generated
fabfile.
For this reason, I think to keep the chance of errors down (e.g. running old code, or failing to find a fabfile), we either need to use the .assisi file to define custom sandbox locations, or stick with the fixed location.
Any other ideas?
On 18 August 2016 at 15:10, Damjan Miklic notifications@github.com wrote:
Currently, autogenerated files (sandbox) and data files (data) are stored alongside project files (*.assisi etc.) This is not always desirable, as mentioned in #32 https://github.com/larics/assisi-python/issues/32. Two options for specifying the location of autogenerated files come to mind:
1) Specify by command-line option 2) Specify in the project file (.assisi)
The two options seem mutually not exclusive.
@rmm-fcul https://github.com/rmm-fcul please comment.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/larics/assisi-python/issues/80, or mute the thread https://github.com/notifications/unsubscribe-auth/AHa-l7sJ1BANbq4CaQW-AxSKJZlJdCV9ks5qhGfCgaJpZM4Jnh1v .
Currently, autogenerated files (sandbox) and data files (data) are stored alongside project files (*.assisi etc.) This is not always desirable, as mentioned in #32. Two options for specifying the location of autogenerated files come to mind:
1) Specify by command-line option 2) Specify in the project file (.assisi)
The two options seem mutually not exclusive.
@rmm-fcul please comment.