Closed tituspijean closed 2 months ago
!testme
Just had a review at the code, seems great to me.
I was just wondering if conf/scheduler.yaml
should not contain instead:
status:
cache-purge: enabled
cache-clear: enabled
default-site-backup: disabled
Don't know what you think of it, since cache cleanup maybe is a good thing to have by default.
Also, I was wondering about the permissions used. Shouldn't the group be set to www-data
as is done globally in the install script?
Don't know what you think of it, since cache cleanup maybe is a good thing to have by default.
Indeed, though it may increase load on lower spec devices?
Also, I was wondering about the permissions used. Shouldn't the group be set to www-data as is done globally in the install script?
Actually the PHP pool runs as $app:$app so there is no influence on that here. I'm actually wondering now about the relevance of www-data
... ha yes, a look to nginx.conf makes sense of its use.
Also, the relevant part of the install script is actually https://github.com/YunoHost-Apps/grav_ynh/blob/68edebace10aabac9ccaa171353f522d54c0d92c/scripts/install#L63 ;)
Though I concede mixing $app:www-data
and $app:$app
files may not make actual sense.
Yes, for coherence I'd have used the same permissions everywhere, but I've no idea what's better in fact.
Let's merge this as-is. I do not want to give myself a headache with files permissions right now. :)
Fixes #162
PR Status
Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)