-
Notifications
You must be signed in to change notification settings - Fork 76
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
Kol user [KOLIBRI_HOME and KOLIBRI_USER best practices needed, hopefully with help from Learning Equality] #3505
Conversation
|
Not quite there yet 'command --help' doesn't work. |
|
then fix it yourself |
A little FYI something is messed up if any user other than could run /usr/bin/kolibri
Note the invoking user's home directory is being populated, ignoring what is in the config files, all with just calling 'help', Good luck. |
If we do move ahead with /etc/password hygiene (likely, can't hurt) using |
not my issue have fun |
Yes. RECAP: Kolibri documentation remains missing with a broken link[1] as to where things like KOLIBRI_HOME and KOLIBRI_USER should properly be set. Leading to these ongoing problems. Hopefully that will be cleared up in coming months with help from @jredrejo, @benjaoming or @radinamatic. [1] Broken link https://kolibri.readthedocs.io/en/latest/advanced.html within https://github.com/learningequality/kolibri-installer-debian/blob/fdb96a173efff92d79789140201ac3f385b20364/debian/README.etc#L19 as discussed on learningequality/kolibri-installer-debian#115 |
to be clear, I will use python, so the current kolibri user with no home, shell, or password is not a problem. |
If you
However there is function called check_debian_user imported in cli,py that might of caught the other issue above and raised a warning/prompt, makes me wonder if this is an import ordering issue, should check if the user is valid before trying to modify the filesystem. Perhaps it's just an ownership issue of /library/kolibri/. Again good luck. |
Thanks much for highlighting that and your summary here: Until Kolibri clarifies "official" guidelines — as to where KOLIBRI_USER and KOLIBRI_HOME should best be set — ideally with SSOT / DRY in mind to help us all reduce brittleness in coming years 🙏 |
Fixes bug:
issues raised in #3504
Description of changes proposed in this pull request:
kalite approach to dealing with HOME and USER
Smoke-tested on which OS or OS's:
U-22.04 VM
Mention a team member @username e.g. to help with code review: