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
I'm wondering why .cache and .config directories have to live in the webserver's home directory, as this is not reliably identifiable, e.g. the $_SERVER['HOME'] superglobal might not be set, also environment variables, and even the owner of the current process might not be the webserver user.
Also, there's no configuration option for overriding the auto-detection of the home directory (which would be a first step to add), so CiviOffice will not work at all in such environments.
@jofranz, @bjendres can you provide some hints on why CiviOffice needs to write to the webserver's home directory?
@dontub I remember you looked into that as well and had suggestions …?
PS. Some tests for improvement in the homeDirectory branch (56b816e).
The text was updated successfully, but these errors were encountered:
Follow-up to #9.
I'm wondering why
.cache
and.config
directories have to live in the webserver's home directory, as this is not reliably identifiable, e.g. the$_SERVER['HOME']
superglobal might not be set, also environment variables, and even the owner of the current process might not be the webserver user.Also, there's no configuration option for overriding the auto-detection of the home directory (which would be a first step to add), so CiviOffice will not work at all in such environments.
@jofranz, @bjendres can you provide some hints on why CiviOffice needs to write to the webserver's home directory?
@dontub I remember you looked into that as well and had suggestions …?
PS. Some tests for improvement in the
homeDirectory
branch (56b816e).The text was updated successfully, but these errors were encountered: