Open douglaswross opened 10 months ago
Good question!
I see a few options:
1) Move the entire prepdocslib into app/backend, and then adjust scripts/prepdocs.sh to call it from there. In that case you'd probably just use a single Python environment, and merge the requirements files.
2) Add an azd predeploy hook that will cp -r
the prepdocslib folder into app/backend. You would still need to make sure you had all the requirements however, and you'd also need to cp for local development.
So I think I'd vote for #1. Let me know if you need help making that adjustment.
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
OS and Version?
azd version?
Versions
Mention any other details that might be useful
Is there a simple way to access the prepdocslib from a new python file in app/approaches/ where new file works a lot like prepdocs.py
Thanks very much for any help.