Is your feature request related to a problem? Please describe
I didn't notice it, and realized ignorance with my issue at hand, during my migration to crowsnest from mjpeg-streamer
initially mjpeg-streamer and crowsnest initially conflict upon installation
enabling debug showed an issue with bind address, uninstalling mjpeg-streamer, or changing crowsnest port solved the issue
crowsnest: ERROR: Start of camera-streamer [cam rpi] failed! added for google crawlers
Describe the solution you'd like
detection of mjpeg-streamer installation via kiauh.sh
prompt "are you migrating from/to crowsnest/mjpeg-streamer"?
prompt to auto uninstall crowsnest/mjpeg-streamer IF user responds [Y]es
prompt WARNING stating conflict between the services if user enters [N]o - similar to installing fluidd/mainsail in tandem
Describe alternatives you've considered
Simply offering a Warning in place of the conflict described above
Ability to prompt for port change in config when installing either service if conflict is detected( IF user enters No at point 2 or 3- I believe this would be more complex)
Additional information
mjpeg-streamer installed via kiuah.sh
had to enable debug level logging to find the root cause
not realizing that Crowsnest and MJPEG-streamer were trying utilize the same port(8080)
Less knowledgeable users would be stuck on this particular issue when migrating or "testing" the different services in tandem, utilizing the script for its ease of use.
this is a thought I'd bring up incase there IS an issue with it in the future
Is your feature request related to a problem? Please describe
I didn't notice it, and realized ignorance with my issue at hand, during my migration to crowsnest from mjpeg-streamer initially mjpeg-streamer and crowsnest initially conflict upon installation enabling debug showed an issue with bind address, uninstalling mjpeg-streamer, or changing crowsnest port solved the issue
crowsnest: ERROR: Start of camera-streamer [cam rpi] failed! added for google crawlers
Describe the solution you'd like
Describe alternatives you've considered
Simply offering a Warning in place of the conflict described above Ability to prompt for port change in config when installing either service if conflict is detected( IF user enters No at point 2 or 3- I believe this would be more complex)
Additional information
mjpeg-streamer installed via kiuah.sh
had to enable debug level logging to find the root cause not realizing that Crowsnest and MJPEG-streamer were trying utilize the same port(8080)
Less knowledgeable users would be stuck on this particular issue when migrating or "testing" the different services in tandem, utilizing the script for its ease of use.
this is a thought I'd bring up incase there IS an issue with it in the future
verbose logging level tail in crowsnest
debug loging level tail in crowsnest