Possible TODOs

[graste]

• make it possible to disable exports or just run no formatters by default etc.
• add check list command instead of always running checks (maybe --dry-run option?)
• add general php ini settings check (done)
  • beware: post_max_size = 0.25M or post_max_size = 10M (multiple spaces before the 10M)
• add general php extensions check (including options) (done)
• perhaps add check for invalid whitespace before/after <?php/?>
• add export formatter for following formats:
  • markdown
  • json (done)
  • php (done)
  • xml (done)
  • nagios plugin compatible report format?
• add token handling for dependencies (including multiple reruns)?
  • add nested checks or just delete the interface?
  • add automatic mode to executable checks when dependency management is there?
  • for dependencies or nested checks:
  • ask for value (writable directory etc.) when certain check fails
• add check for accelerator (apc, eaccelerator, xcache, opcache) being present
• add simple pre-execution check for environaut requirements
  • JSON extension should be installed (json_encode etc.)
  • libXML extension should be installed (DOMDocument etc.)
  • PHP version should be >= 5.3.2
• think about PHP-FPM settings check and other WEB instead of CLI related checks
  • certain directories should not execute PHP files (like upload locations)
  • web server should handle and return cache headers correctly
  • are certain security related headers available (X-Content-... etc.)
  • aggregate some good practices for file uploading into a check?
  • ...
• think about quality assurance checks:
  • it's probably something that should be done by a CI system, but still...
  • is there a "security related" sniffer for code analysis that may be run?
  • perhaps lint common file extensions (php -l, jsl, xmllint...)
  • this could be a last resort or pre-flight checklist for deployments
• think about user/group/file system permissions and perhaps check directories and files for being non-writable with exclusions for cache, log, uploads etc.

[OskarStark]

Sometimes you can't solve the requirement immediately. For example, when you don't have sudo rights on the machine. Maybe it is a nice idea that you can quit a single check, an rerun it later when the requirement is set (by an admin i.e.)?

[graste]

It's a question about how Environaut should work and if it should fail directly or just compile a report or run in loops after waiting for resolutions or whatever. We should make a new ticket for this.

[graste]

At the moment (release 0.2.0) all checks are run. When they ran successfully (that is, they return true) the results of the checks are marked as SUCCESS. Only cachable settings from successful results are written to a cache file and it's then not necessary to re-enter those information on subsequent runs as the cached values can be used by the checks.