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
{{ message }}
This repository has been archived by the owner on Dec 27, 2023. It is now read-only.
Please introduce a framework to implement sanity checks into setup.php. Checks should run in batch on click (or initiated by CLI).
Possible features are:
Lately users had issues due to not eliminated files. E.g. matomo (piwik) does checks on file integrity. As a result it shows files that do not belong to the installation
To check on file permissions might be a good idea, too.
Also a common source for issues is an invalid DB structure. In my understanding the file <APP>/Setup/setup.xml provide the structure of the target model (whereas one cannot see if update scripts ran sucessfully)
Additional checks could test for utf8mb4 or similar
Functioning of httpd routing/rewrites for ActiveSync and WebDAV
The text was updated successfully, but these errors were encountered:
hi Johannes,
good idea, I'll discuss that with the team.
we already have some kind of framework here: \Setup_Controller::checkRequirements - we could enhance that and add additional checks there.
it is also callable via cli:
$ php setup.php --check_requirements
OK - All requirements are met
The following optional binaries are missing: tika
Also a common source for issues is an invalid DB structure. In my understanding the file /Setup/setup.xml provide the structure of the target model (whereas one cannot see if update scripts ran sucessfully)
this is already implemented as a separate cli function (chich shows the differences and even allows to fix the structure):
setup.php --compare -- otherdb=tine20other
caveat: you have make a fresh install into "tine20other" to be able to compare the 2 databases.
Please introduce a framework to implement sanity checks into setup.php. Checks should run in batch on click (or initiated by CLI).
Possible features are:
<APP>/Setup/setup.xml
provide the structure of the target model (whereas one cannot see if update scripts ran sucessfully)The text was updated successfully, but these errors were encountered: