snipe-it

Files

T

Jeremy Price ed8da6ad1b Docker: Ensure permissions on Laravel log file

FIXES: https://github.com/grokability/snipe-it/issues/12725

In some of our Docker startups, it was possible for the Laravel log file
to be created with root permissions, causing future errors when the
non-root webapp tries to write to it.

We'll now always chown (and create, if necessary) the log file to the proper
user after running any artisan commands (as root)

We _could_ run them as the proper user via su, but IMO not doing so keeps the
script easier to read, but I'm not married to the approach. I'd still
want to keep the chown command(s) in, because it will also fix the
permissions for anyone who already has this issue.

2025-05-29 17:45:14 -07:00

000-default-2.4.conf

Alpine linux docker image (#6645 )

2019-01-30 14:45:36 -08:00

000-default.conf

Version 3 - hold onto your butts

2016-03-25 01:18:05 -07:00

001-default-ssl.conf

Fix path to snipeit-ssl.crt (#2428 )

2016-08-16 13:03:55 -07:00

column-statistics.cnf

Replace .my.cnf with column-statistics.cnf at the system level for mysqldump