Integrity checking system

[Derkades]

The problem

Many user reported issues are caused by missing files, extra files, modified files, files from different Nameless versions, or corrupt in some other way.

The solution

Ship a checksums file with NamelessMC, so the integrity of files can be verified. Files that are expected to change or be edited (e.g. cache, uploads, custom templates and modules) are ignored.

Workflow

Run php -f dev/scripts/generate_checksums.php to generate the checksums file to be included in a release

Run php -f dev/scripts/verify_checksums.php to verify checksums using the checksums file (after preparing the release, so removing directories like node_modules, .git, etc.)

Ideally StaffCP would also run this with a cache, and display a warning in the "Server compatibility" section if there are issues. I did not implement that for now.

[Derkades]

I don't know how to fix (or ignore?) the "undefined constant ROOT_PATH" issue phpstan is reporting

[Derkades]

I have no idea why phpstan is failing, it works locally...

[Derkades]

I think phpstan itself is crashing. It does not say problems were found with the code, it says that it itself crashed with a link to create a bug report. That also explains why ignoring the line doesn't help.

[tadhgboyle]

I really like this idea, and it would be cool to push it out eventually.
Since we want to display this information to users in StaffCP, I think it would take up a lot of space so it would not work well in the Server Compatibility widget - could we consider making a more general "Website Health" page (name can be hashed out)?

Resolved