p202 system info

What Account › Settings shows: versions, PHP limits, memcache, clicks recorded, database size, cron, DataEngine, GeoIP database

Web UISettings
All commands

01Jobs it does

Each one is a real command line. Copy it, or open it in the builder below to change it.

install settings

Also: versions, database size, geoip database age, geolite build date

p202 system info
Web UISettings

02What you get

Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.

p202 system info
$ p202 system info
clicks_recorded:            2904
cron_last_ran_at:           1792622297
cron_last_ran_seconds_ago:  4
database_size_bytes:        128434176
database_upgrade_needed:    false
dataengine:                 {"minutes_left":0,"percent_done":0,"tasks_done":0,"tasks_total":0}
keyword_preference:         searched
memcache:                   {"installed":false,"running":false}
mysql_version:              10.11.19-MariaDB-ubu2204
php_limits:                 {"max_execution_time":"30","max_input_time":"60","post_max_size":"8M","upload_max_filesize":"2M"}
php_safe_mode:              false
php_version:                8.3.35
schema_version:             1.9.78
version:                    1.9.78
Real output · p202 1.9.79 · demo dataexit 0

03Build your command

Pick values and the command line writes itself, quoted and ready to paste.

p202 system info

Set flags below; the command updates as you type.

04How it works

The Prosper202 code and database versions (database_upgrade_needed when they differ), PHP and MySQL versions, memcache, the PHP limits uploads and long reports run under, clicks recorded to date, database size, when the cron job last ran, and the DataEngine's progress. Whether a newer release exists is not reported: the UI asks a remote service for that.

geoip_database is the GeoLite2 City file every location lookup reads, from its own metadata: state (current, stale past stale_after_days, missing, unreadable), built_at and built_on, and age_days; reason says why when it is not current. geoip_refresh is its weekly refresh with the install's MaxMind account: whether the account ID and licence key are stored (never their values), how the last run ended (last_outcome, last_error) and when the next is due. The refresh is set up and run under Account › Settings › GeoIP database.

Needs an Admin or Super user key whose role has access_to_settings (as Account › Settings asks), and system:read.

05For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands system info --json.
  • With AI_AGENT, CLAUDECODE or another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with a hint.
  • Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure, 6 no Pro licence on the install.
p202 commands system info --json
{
  "path": "p202 system info",
  "use": "info",
  "short": "What Account › Settings shows: versions, PHP limits, memcache, clicks recorded, database size, cron, DataEngine, GeoIP database",
  "long": "The Prosper202 code and database versions (database_upgrade_needed when they differ), PHP\nand MySQL versions, memcache, the PHP limits uploads and long reports run under, clicks\nrecorded to date, database size, when the cron job last ran, and the DataEngine's progress.\nWhether a newer release exists is not reported: the UI asks a remote service for that.\n\ngeoip_database is the GeoLite2 City file every location lookup reads, from its own metadata:\nstate (current, stale past stale_after_days, missing, unreadable), built_at and built_on, and\nage_days; reason says why when it is not current. geoip_refresh is its weekly refresh with the\ninstall's MaxMind account: whether the account ID and licence key are stored (never their\nvalues), how the last run ended (last_outcome, last_error) and when the next is due. The\nrefresh is set up and run under Account › Settings › GeoIP database.\n\nNeeds an Admin or Super user key whose role has access_to_settings (as Account › Settings asks), and system:read.",
  "runnable": true,
  "example": "p202 system info\n  p202 system info --json",
  "tasks": [
    {
      "run": "p202 system info",
      "ui_pages": [
        "Settings"
      ],
      "phrases": [
        "install settings",
        "versions",
        "database size",
        "geoip database age",
        "geolite build date"
      ]
    }
  ]
}