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
Improve Tiny Tiny RSS service #33347
Conversation
cc: @zohl @Nadrieril @bjornfor |
nixos/modules/misc/ids.nix
Outdated
@@ -301,6 +301,7 @@ | |||
pykms = 282; | |||
kodi = 283; | |||
restya-board = 284; | |||
tt_rss = 285; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The application directory is chowned
on startup. Therefor it is not necessary to allocate a static uid/gid.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But tt_rss must be given some uid/gid somewhere anyway, right? If not here, then the user must provide it. At least that's how it works with immutable users and I'd prefer supporting immutable users seamlessly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the user must not provide it. It will be allocated on the first use.
Static uids/gids are limited. Therefore we only allocate them, if necessary (i.e. when we have a lot of files, where we cannot change owner on startup)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, will it be allocated automatically even with immutable users?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have any example user ID's or services in your mind where no static uids/gids were used but automatically generated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it is an issue that each webapp defines and uses its own uid, we could add a generic phpfpm
uid which can be used by all webapps using php-fpm. Similarly, as uwsgi
uid. But of course it's best if each webapp is "isolated" with its own uid.
FWIW, I upgraded nixos on my server few monthes ago and got tt-rss broken too. There were problems with php configuration and wrong interpretation of exit codes in
As far as I remember, I got blank web page and no information in logs. Turned out, the problem was in php-variables. |
- Add tt_rss system user. - Use tt_rss as the user by default. - Create tt_rss user and group automatically if used.
If the user chooses MySQL, it is enabled by default. Also, the used database is created automatically along with the user and permissions.
tt-rss switched to a rolling release model
I've cleaned this up and updated tt-rss, thank you very much! |
Motivation for this change
Tiny Tiny RSS service was broken, see: #27048
This pull request fixes that and also makes a few small improvements to the service, in my opinion. Comments and feedback welcome.
To activate Tiny Tiny RSS service, this suffices:
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)