-
-
Notifications
You must be signed in to change notification settings - Fork 39
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 version 5.1.0 #345
Conversation
I'd love to see |
Hey @felddy, same question. Are you still dedicated to push this project? I think there are many interested users and willing contributors. |
Hello; I'm migrating weewx to a new machine and wanted to use docker. Happy to help... Just running a build myself on my own fork - I notice that the extensions have been removed.. wondering if any specific reason... |
4c1e8e2
to
cbb7789
Compare
Hey everyone. I appreciate your interest and patience. I've made a great deal of progress fighting the bit rot. I'm running through testing now, and making sure I've covered some of the common use cases I know about. I hope to have a release out in the next few days. If you're either impatient or brave you can try pulling the images that are being generated by GitHub Actions for the PR at: Note I'm targeting version Stay tuned... |
This should be installed via an extension going forward
b1aa0a1
to
55c0fa4
Compare
Thanks @felddy I was running the PR over the weekend, most issues where related to me getting the SDR to work. Thanks again: Update confirmed that the reporting update is not connected to the docker image. |
@felddy all seems well with the image, with one exception. I've found that I needed to rebuild the base image supplying the uid I need weewx to run under. Just supplying this at runtime didn't work as there was no user of that id inside the image |
I have the same comment as @mbwhite, it's missing something that allows for user switching.
|
@mbwhite I'm looking into the |
By properly configuring the logging options of WeeWX to send to the console, we can remove all the code that was required to run as root and the drop to a different user.
It's the actual ID of the user that that I need to match. Thev data directory is mounted and if to avoid those been written out as a user I don't have on the host system. I also need to add in extra libraries to get the SDR to work. See https://github.com/ampretia/womble-weewx |
I think there's something else going on there as well as the uid gid... |
A new build was published by CI/CD that you should pull. I've was able to simplify to the container's user management by removing the need for ---
services:
weewx:
image: ghcr.io/felddy/weewx:release-5.0.2
user: 1001:dialout
volumes:
- type: bind
source: ./data
target: /data
devices:
- /dev/ttyUSB0 You'll also need to configure the console logging with: [Logging]
[[root]]
level = INFO
handlers = console, As for the SDR library. If it had been Python you can install it with: And it would be saved on your data volumes Python path. Since you're bringing it in with Let me know if this works for you. |
🗣 Description
Support WeeWX
v5.1.0
💭 Motivation and context
It seems people are interested, and I've finally found a few spare cycles to continue the work.
Also, I'd like to get it working with my Home Assistant setup. ;)
🧪 Testing
✅ Pre-approval checklist
in code comments.
to reflect the changes in this PR.
✅ Pre-merge checklist
✅ Post-merge checklist