-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat big gui update #16
Conversation
Remove . and .. because these are not files
followup to previous commit
don't list non existing files
update Dockerfile, stripped docker image down remove sudo from dependencies add status backend endpoint add ping status to display scanner offline status in web ui add loading spinner to selected button in web ui add more verbosity to runScanner.sh rename env variables for consistency
name was always root before not editable with USERNAME env var
remove unused lines in scripts
Big update (second try)
@philippderdiedas: It didn't quite work out of the box. I adapted and corrected a number of things (variable handling, download path, etc.), added a ping interval, implemented defaults, etc. See commits above for details.
Maybe you can take a look, as well. I am not very well versed on the GUI side of things and a lot has changed. You might be faster in finding these errors. Good news: I tested scanning via buttons, etc. also and this works fine. So the tedious user issues should not be a problem. |
oof, i think you broke the runScanner.sh. when you do |
i think i switched the default value for WEBSERVER because i misread that somehow, thats why my variable is called WEBSERVER_ENABLED impyling if not set the default is false, would call it WEBSERVER_DISABLED then |
and thats why all labels are "" for more info shell parameter expansion |
WEBSERVER_ENABLE was never unset though, as it is set to at least empty string in the backward compatibility section (which had a different issue, but this is fixed now, as well). But you are right, even if set to "false" it would turn on, as it is a string with length > 0. Added an explicit comparison in the recent commits. Tested and works. Anyway, all of this is doesnt solve the mystery of the missing buttons on the page... |
Do you have a compose file for reference? |
Aaahh..maybe the UI block is the issue... I am currently focusing on backward compat checks with something like this:
|
Excellent! That got me on the right track, thank you! I missed out a semicolon in status.php when adding the "unknown" status. Buttons are there, scan can be triggered, nice! Unfortunately, there still seem to be some permission issues, when scanning from the GUI:
Any ideas? If not, I will take a look in te coming days. I am very willing to take up all these changes now. You put a lot of effort in and it shows! I really like the nicer GUI, the blocking, the scanning animation, etc. Not to mention all the cleaning of my hacked scripts. Thank you very much! |
Somehow this dropped off my radar for quite some time and only came back up, when #24 came up. Since that one works as a drop in replacement, we have merged that to master and I consider this superseded |
testing and working in the changes from #15