Skip to content
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

support serving local folders using web-server-chrome #90

Merged
merged 1 commit into from
Mar 2, 2016

Conversation

kzahel
Copy link
Contributor

@kzahel kzahel commented Mar 1, 2016

Everything seems to be working. Only nitpick I notice so far is that if you change the password via the remote interface it does not restart the server nor update the auth credentials. I am not sure if this is desired. But you could update the .opts.auth data field if wanted...

@kzahel kzahel mentioned this pull request Mar 2, 2016
@kzahel
Copy link
Contributor Author

kzahel commented Mar 2, 2016

I notice that when I enter a bad port (say 80 or rather any ports under 1024 I think?) the web server will fail to start, but there is no indication to the user why there was a failure. Perhaps it would make sense to validate the input, and have a way to show an error upon launching the kiosk app

@matt-cook
Copy link
Member

Roger that. I'll enforce client side. I was considering hiding the interface/port options entirely (just use 127.0.0.1:8080, or another random port).. but there could conceivably be a port conflict, so I'll probably allow it to be user configurable.

#91

matt-cook added a commit that referenced this pull request Mar 2, 2016
support serving local folders using web-server-chrome
@matt-cook matt-cook merged commit de09d80 into lookitscook:serve-local Mar 2, 2016
@matt-cook matt-cook modified the milestone: 5.6.0 Mar 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants