MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information.

{
    "batchcomplete": "",
    "continue": {
        "lecontinue": "20251023183134|85",
        "continue": "-||"
    },
    "query": {
        "logevents": [
            {
                "logid": 95,
                "ns": 0,
                "title": "Guidelines:Edenctl",
                "pageid": 73,
                "logpage": 73,
                "revid": 253,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Dominic",
                "timestamp": "2026-02-02T20:05:59Z",
                "comment": "Created page with \"= Server Administration with Edenctl =  The '''edenctl''' tool is a ''bash'' script for server administration on Debian/Linux. The general usage of this script is (as root user):  <syntaxhighlight lang=\"bash\"> edenctl [command] [parameters] </syntaxhighlight>  == Setup and Teardown ==  To set up a newly installed Eden, run:  <syntaxhighlight lang=\"bash\"> edenctl setup </syntaxhighlight>  This will run you step-by-step through the setup process. Enter your server details...\""
            },
            {
                "logid": 94,
                "ns": 0,
                "title": "Guidelines:DualHost",
                "pageid": 72,
                "logpage": 72,
                "revid": 234,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Dominic",
                "timestamp": "2026-02-02T16:46:44Z",
                "comment": "Created page with \"== Dual Host Setup ==  In certain situations, you may want to deploy Eden with a database on a separate host. Follow these steps for Debian/Linux:  === Terminology ===  This guideline assumes that you have two hosts running on Debian/Linux - we will use the '''AppHost''' and '''DBHost''' designations here to distinguish between the two.  Further, we assume that each host has a '''public IP''' (exposed to the internet) and a '''private IP''' (local network only). Thus, a...\""
            },
            {
                "logid": 93,
                "ns": 0,
                "title": "Guidelines:SecureOperation",
                "pageid": 71,
                "logpage": 71,
                "revid": 227,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Dominic",
                "timestamp": "2026-02-02T16:27:28Z",
                "comment": "Created page with \"== Secure Server Operation ==  The following steps are recommended to secure your Eden server:  === Unprivileged Account ===  You should use an unprivileged user account for SSH login. To do so, login as root and create a new user, e.g. \"serveradmin\":  <code> adduser serveradmin </code>  Enter a password for the new account when prompted for, and provide additional information as required.   To permit the new user to <code>sudo</code> without password, edit the sudoers c...\""
            },
            {
                "logid": 92,
                "ns": 0,
                "title": "Guidelines:DebianPackages",
                "pageid": 70,
                "logpage": 70,
                "revid": 214,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Dominic",
                "timestamp": "2025-11-25T10:54:46Z",
                "comment": "Created page with \"= Debian Packages =  As of version 6.0, Eden provides packaged releases for installation, setup and server administration. Packages for Debian (*.deb) are currently provided as assets attached to the respective GitHub release:  * https://github.com/sahana/eden/releases  Using packaged releases is the recommended setup method for production servers.  == Prerequisites ==  Before starting the installation, you should have a server machine (virtual or bare metal), installed...\""
            },
            {
                "logid": 91,
                "ns": 0,
                "title": "Guidelines:Deployment",
                "pageid": 69,
                "logpage": 69,
                "revid": 212,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Dominic",
                "timestamp": "2025-11-25T10:17:48Z",
                "comment": "Created page with \"= Installation =  == Installation from Release Package ==  As of version 6.0, Eden provides packaged releases. This is the recommended setup method for production servers. The packages are available as assets attached to the respective GitHub release.  * [[Guidelines:DebianPackages|Installation on Debian/Linux]] * [[Guidelines:Edenctl|Server Setup and Management with edenctl]]  == Installation from GitHub Repository ==  It is also possible to install Eden directly from a...\""
            },
            {
                "logid": 90,
                "ns": 3000,
                "title": "Blueprint:MapViewer",
                "pageid": 68,
                "logpage": 68,
                "revid": 208,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Dominic",
                "timestamp": "2025-11-14T16:38:29Z",
                "comment": "Created page with \"* [[Blueprint:Index|All Blueprints]]  == Integration of a Map Viewing Client ==  === Background ===  Maps are an integral part of an emergency management application, for many use-cases to facilitate situational awareness, geospatial analysis and reporting.  As of version 6.0, Eden is still using the original map viewer based on OpenLayers 2, with its own JS-based back-end integration.  === Problems ===  The original Eden map viewing client (s3.gis.js resp. S3MAP) uses a...\""
            },
            {
                "logid": 89,
                "ns": 2,
                "title": "User:Awjans",
                "pageid": 0,
                "logpage": 0,
                "params": {
                    "oldgroups": [],
                    "newgroups": [
                        "architect"
                    ],
                    "oldmetadata": [],
                    "newmetadata": [
                        {
                            "group": "architect",
                            "expiry": "infinity"
                        }
                    ]
                },
                "type": "rights",
                "action": "rights",
                "user": "Wikiadmin",
                "timestamp": "2025-11-10T18:49:51Z",
                "comment": "should have the ability to create and edit blueprints"
            },
            {
                "logid": 88,
                "ns": 2,
                "title": "User:Awjans",
                "pageid": 0,
                "logpage": 0,
                "params": {
                    "userid": 4
                },
                "type": "newusers",
                "action": "byemail",
                "user": "Wikiadmin",
                "timestamp": "2025-11-10T18:47:32Z",
                "comment": "Collaborator in the Eden project"
            },
            {
                "logid": 87,
                "ns": 3000,
                "title": "Blueprint:FailedLogins",
                "pageid": 67,
                "logpage": 67,
                "revid": 201,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Dominic",
                "timestamp": "2025-10-29T15:53:47Z",
                "comment": "Created page with \"* [[Blueprint:Index|All Blueprints]]  == Handling of Failed Login Attempts ==  === Background ===  As of Eden version 5.x, failed login attempts are logged - but have no further consequences. Users can make an unlimited number of attempts to login to their account.  === Problems ===  Sensitive deployments may want to prevent brute-force attempts to login, and therefore need a way to configure consequences for multiple consecutive login failures (e.g. locking accounts). H...\""
            },
            {
                "logid": 86,
                "ns": 6,
                "title": "File:Clone before merge.png",
                "pageid": 66,
                "logpage": 66,
                "revid": 183,
                "params": {},
                "type": "create",
                "action": "create",
                "user": "Dominic",
                "timestamp": "2025-10-23T18:31:34Z",
                "comment": ""
            }
        ]
    }
}