One of the challenges that developers bump into when developing locally, especially in a very local or containerized environment, is the assumption that the Software Discovery Tool is located in /opt.
This is hard-coded throughout the application, and also may not reflect what users ultimately want to do when they deploy this application in production anyway.
This issue is to review the prevalence of this assumption throughout the code, and then come up with ideas for how to tackle it.
One of the challenges that developers bump into when developing locally, especially in a very local or containerized environment, is the assumption that the Software Discovery Tool is located in /opt.
This is hard-coded throughout the application, and also may not reflect what users ultimately want to do when they deploy this application in production anyway.
This issue is to review the prevalence of this assumption throughout the code, and then come up with ideas for how to tackle it.