Conversation
users.users makes home only owner-readable. This breaks nginx reading static assets from nextcloud's home, after a nixos-rebuild that did not restart nextcloud-setup.
|
Isn't nginx's user part of the nextcloud group now? Or am I misunderstanding the issue you're having? :) |
It is in the same group, but 700 is not readable my nextcloud group members but only nextcloud users. |
|
So, Finally, why 750 if you claim to make I'm sorry, maybe I'm just blind atm and totally missing the point! |
It does not have the exec permissions if home is re-chowned by the users activation script but nextcloud-setup.service is not restarted.
fixed the title. Commit message can be fixed by using Github's squash feature.
|
| wantedBy = [ "multi-user.target" ]; | ||
| before = [ "phpfpm-nextcloud.service" ]; | ||
| path = [ occ ]; | ||
| serviceConfig.ExecStartPre = "+${pkgs.coreutils}/bin/install -m750 --owner nextcloud --group nextcloud -d ${cfg.home}"; |
There was a problem hiding this comment.
I guess this should be enough?
| serviceConfig.ExecStartPre = "+${pkgs.coreutils}/bin/install -m750 --owner nextcloud --group nextcloud -d ${cfg.home}"; | |
| serviceConfig.ExecStartPre = "+${pkgs.coreutils}/bin/install -m710 --owner nextcloud --group nextcloud -d ${cfg.home}"; |
users.users makes home only owner-readable.
This breaks nginx reading static assets from nextcloud's home,
after a nixos-rebuild that did not restart nextcloud-setup.
Motivation for this change
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)