On Tuesday, January 16, 2024 at 6:44:43 AM UTC-8 G Hammer wrote: The point isn't if you can change what's written in a guide, the point is if the guide works as written. It does not. Later in the quick start there are commands that DO require sudo.
This is not complicated. - If you are root and want to run as root you do not need to use sudo. - If you are a non-privileged user you do need to use sudo for ‘some’ commands typically - If you are root and ‘want’ to use sudo you of course can…if your system is configured accordingly. - If you are a non-privileged user and need to use sudo, your system must be configured to permit that as well But…there are edge cases for a install and run non-privileged setup where sudo would not be required either if you go outside typical installations. I can think of a couple ways it would work on a typical pi but I won’t mention them here. There are always edge cases where any docs written for the 98% will be incorrect for those in the 2% who do uncommon things. You always need to understand your system well enough to know if you need to salt to taste a little, so to speak. Installing into Docker is in that 2% that need to do more things or slightly different things in most cases, depending on how you want things to run privileged or non-privileged. No docs can be 100% perfect for an infinitely variable desired end state. Once you go Docker the onus is on the integrator to up their techie-fu and think more rather than blindly following a recipe intended for the other 98% of configs. -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/bed210bc-c4b9-4c56-9ef4-4a3b0e01fd96n%40googlegroups.com.
