You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two problems, but the second subsumes the first, so I'll start with the easy one:
I don't think it's right to use the global constant FS_CHMOD_DIR as what is essentially a temporary variable here. If some other code calls these public functions, then FS_CHMOD_DIR will become defined globally, and will affect the permissions of any other directory that is created -- not just the fonts directories.
But the bigger issue is that...
You really shouldn't need chmod at all. On our systems, for example, it breaks our ACLs. And in general it doesn't solve any problems that aren't better solved in some other way. I've written a long explanation of this at chmod breaks ACLs keycdn/cache-enabler#320, so maybe you can forgive me for not reproducing it here.
Of course, if you forego the chmod entirely, the unintended FS_CHMOD_DIR side effects cease to matter.
The text was updated successfully, but these errors were encountered:
Hello, I've encountered two issues with the way directory permissions are handled. The code (repeated twice) looks like,
There are two problems, but the second subsumes the first, so I'll start with the easy one:
FS_CHMOD_DIR
as what is essentially a temporary variable here. If some other code calls these public functions, thenFS_CHMOD_DIR
will become defined globally, and will affect the permissions of any other directory that is created -- not just the fonts directories.But the bigger issue is that...
Of course, if you forego the chmod entirely, the unintended
FS_CHMOD_DIR
side effects cease to matter.The text was updated successfully, but these errors were encountered: