-
Notifications
You must be signed in to change notification settings - Fork 15
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
/Setup
error and/or better docker support
#14
Comments
Thanks for the feedback! You're absolutely right about the whole docker setup. The configuration is currently inside the docker image. So if you want to add your own configuration, you will have to edit the files and build your own docker image. The Setup Wizard probably crashed because your docker image could not connect to the internet to query for your bridge IP at a Philips Hue API endpoint. I've fixed that in the latest version. The result of the Setup Wizard is json that you will have to manually add to your appsettings.json. So it's not as streamlined as I want it to be. The good news is, I'm currently working on v3. Suggestions are welcome! Thanks |
does DotNet et al make it prohibitively difficult to just it can even be inside the project folder, it just needs to be a sub-directory because docker generally assumes here's an example of a
here's an example of a desired
by default, without the however, the good news is the Docker volume being writeable by default means once the permissions are ironed out (ie: one |
Today the first version of the v3 docker image is released. The frontend is rewritten in Blazor and the setup / configuration of the bridges now happens through the UI instead of config files. So no need to map a dicrectory to docker or anything like that. |
finally looping back around to this... it's definitely the new UI, but the "Add bridge" fails.
I suspected the URL Parse was failing because my hostname is a fake TLD for internal network use, but the same error fires when I use IP. I'm also not sure where this data eventually gets stored; but I probably want it in a docker volume so I don't have to rejoin via a physical button elsewhere every time the container is recreated. this warning implies another reason / location that might need volume'd:
is [edit: my ancient container with a hard-coded |
Make sure that the IP or hostname your input does not contain http / https or any spaces. Just the IP or hostname. With this new version, the data gets stored in your browser's local storage, so you won't have to re-register when the container is recreated. |
I logged into Github today and my feed said you cut a new release, so I raced to go try it out, including the new docker image....
well, it turns out, I have been using a slightly fudged docker image:
Docker "volumes" basically hard-assume directory, not file. and while they "sometimes work" using a file as a volume mount, it can be error-prone and some toolchains will outright syntax error over the use of a non-directory volume mount. my quick workaround is simply publish my own site-local Docker image with my config "baked in", ie: hardcoded. this works, but is not an ideal setup because it's extra steps and not every Docker user has a full private registry and CICD stack to customize Docker images for site-local configs.
the quickest ""fix"" is probably to just put
appsettings.json
in some sort of site-local config directory and change whatever code reads the config to expect a directory basedir of some kind. the directory can be basically anywhere and named anything, it can even include a default copy ofappsettings.json
, it just must be a directory in a documented PATH so people like me can more easily override it."no bother, I'll try this new
Setup Wizard
button... oh." incidentally, Docker Users probably want the Setup Wizard to write the appsettings to a Volume Directory so it can persist between container runs, so I have little interest in drilling into this Setup error, but it is included for completeness:The text was updated successfully, but these errors were encountered: