MediaWiki API 结果
这是JSON格式的HTML实现。HTML对调试很有用，但不适合应用程序使用。
指定format参数以更改输出格式。要查看JSON格式的非HTML实现，设置format=json。
{
"batchcomplete": "",
"continue": {
"lecontinue": "20260504060015|43",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 53,
"ns": 600,
"title": "\u57fa\u790e\u539f\u7406:\u5bb9\u5668\u6280\u672f/Docker/Concepts/image",
"pageid": 41,
"logpage": 41,
"revid": 156,
"params": {},
"type": "create",
"action": "create",
"user": "Johnson",
"timestamp": "2026-05-08T09:04:10Z",
"comment": "\u521b\u5efa\u9875\u9762\uff0c\u5185\u5bb9\u4e3a\u201c== Explanation == Seeing as a container is an isolated process, where does it get its files and configuration? How do you share those environments? That's where container images come in. A container image is a standardized package that includes all of the files, binaries, libraries, and configurations to run a container. For a PostgreSQL image, that image will package the database binaries, config files, and other dependencies. For a Python web app, it'll inc\u2026\u201d"
},
{
"logid": 52,
"ns": 600,
"title": "\u57fa\u790e\u539f\u7406:\u958b\u6e90\u5354\u8b70",
"pageid": 40,
"logpage": 40,
"revid": 145,
"params": {},
"type": "create",
"action": "create",
"user": "Johnson",
"timestamp": "2026-05-06T14:36:44Z",
"comment": "\u521b\u5efa\u9875\u9762\uff0c\u5185\u5bb9\u4e3a\u201c\ud83d\udcd6 \u958b\u6e90\u5354\u8b70\uff1a\u6578\u4f4d\u6642\u4ee3\u7684\u5951\u7d04\u57fa\u77f3 \u4e00\u3001 \u4ec0\u9ebc\u662f\u958b\u6e90\u5354\u8b70\uff1f \u958b\u6e90\u5354\u8b70\u662f\u4e00\u7a2e\u6cd5\u5f8b\u8a31\u53ef\u5408\u540c\u3002\u5b83\u5b9a\u7fa9\u4e86\u8edf\u9ad4\u8457\u4f5c\u6b0a\u4eba\u8207\u4f7f\u7528\u8005\u4e4b\u9593\u7684\u6b0a\u5229\u8207\u7fa9\u52d9\u3002\u672c\u8cea\u4e0a\uff0c\u5b83\u4e26\u975e\u653e\u68c4\u7248\u6b0a\uff0c\u800c\u662f\u900f\u904e\u9810\u5148\u6388\u6b0a\u7684\u65b9\u5f0f\uff0c\u5141\u8a31\u4ed6\u4eba\u9032\u884c\u8907\u88fd\u3001\u4fee\u6539\u53ca\u5206\u767c\u3002\u5982\u679c\u6c92\u6709\u9019\u4e9b\u5354\u8b70\uff0c\u6839\u64da\u50b3\u7d71\u8457\u4f5c\u6b0a\u6cd5\uff0c\u4efb\u4f55\u672a\u7d93\u660e\u78ba\u6388\u6b0a\u7684\u4ee3\u78bc\u4f7f\u7528\u7686\u5c6c\u9055\u6cd5\uff0c\u9019\u5c07\u6975\u5927\u5730\u963b\u7919\u6280\u8853\u5354\u4f5c\u3002 \u958b\u6e90\u5354\u2026\u201d"
},
{
"logid": 51,
"ns": 600,
"title": "\u57fa\u790e\u539f\u7406:\u5bb9\u5668\u6280\u672f/Docker/Concepts/container",
"pageid": 39,
"logpage": 39,
"revid": 141,
"params": {},
"type": "create",
"action": "create",
"user": "Johnson",
"timestamp": "2026-05-06T13:59:33Z",
"comment": "\u521b\u5efa\u9875\u9762\uff0c\u5185\u5bb9\u4e3a\u201c== Explanation == Imagine you're developing a killer web app that has three main components - a React frontend, a Python API, and a PostgreSQL database. If you wanted to work on this project, you'd have to install Node, Python, and PostgreSQL. How do you make sure you have the same versions as the other developers on your team? Or your CI/CD system? Or what's used in production? How do you ensure the version of Python (or Node or the database) your app needs\u2026\u201d"
},
{
"logid": 50,
"ns": 600,
"title": "\u57fa\u790e\u539f\u7406:\u5bb9\u5668\u6280\u672f/Docker/Concepts",
"pageid": 38,
"logpage": 38,
"revid": 137,
"params": {},
"type": "create",
"action": "create",
"user": "Johnson",
"timestamp": "2026-05-06T13:37:55Z",
"comment": "\u521b\u5efa\u9875\u9762\uff0c\u5185\u5bb9\u4e3a\u201c\u57fa\u7840\u6982\u5ff5 * \u4ec0\u4e48\u662f\u5bb9\u5668 * \u4ec0\u4e48\u662f\u955c\u50cf * \u4ec0\u4e48\u662f\u6ce8\u518c\u673a\u6784 * \u4ec0\u4e48\u662fDocker Compose \u521b\u5efa\u955c\u50cf \u8fd0\u884c\u5bb9\u5668\u201d"
},
{
"logid": 49,
"ns": 6,
"title": "\u6587\u4ef6:Docker-architecture.png",
"pageid": 37,
"logpage": 37,
"revid": 120,
"params": {},
"type": "create",
"action": "create",
"user": "Johnson",
"timestamp": "2026-05-04T16:53:09Z",
"comment": ""
},
{
"logid": 48,
"ns": 6,
"title": "\u6587\u4ef6:Docker-architecture.png",
"pageid": 37,
"logpage": 37,
"revid": 120,
"params": {
"img_sha1": "2iw1noi8493tb4kbjwdo0dove1ru1vs",
"img_timestamp": "2026-05-04T16:53:09Z"
},
"type": "upload",
"action": "upload",
"user": "Johnson",
"timestamp": "2026-05-04T16:53:09Z",
"comment": ""
},
{
"logid": 47,
"ns": 6,
"title": "\u6587\u4ef6:Docker-architecture.webp",
"pageid": 0,
"logpage": 35,
"params": {},
"type": "delete",
"action": "delete",
"user": "Johnson",
"timestamp": "2026-05-04T16:52:13Z",
"comment": "\u5185\u5bb9\u4e3a\uff1a\u201cDocker-architecture\u201d\uff0c\u552f\u4e00\u8d21\u732e\u8005\u662f\u201c[[Special:Contributions/Johnson|Johnson]]\u201d\uff08[[User talk:Johnson|\u8ba8\u8bba]]\uff09"
},
{
"logid": 46,
"ns": 600,
"title": "\u57fa\u790e\u539f\u7406:\u5bb9\u5668\u6280\u672f/Docker/Architecture",
"pageid": 36,
"logpage": 36,
"revid": 119,
"params": {},
"type": "create",
"action": "create",
"user": "Johnson",
"timestamp": "2026-05-04T16:47:49Z",
"comment": "\u521b\u5efa\u9875\u9762\uff0c\u5185\u5bb9\u4e3a\u201c= What is Docker? = Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. With Docker, you can manage your infrastructure in the same ways you manage your applications. By taking advantage of Docker's methodologies for shipping, testing, and deploying code, you can significantly reduce the delay between writing code and running\u2026\u201d"
},
{
"logid": 45,
"ns": 6,
"title": "\u6587\u4ef6:Docker-architecture.webp",
"pageid": 0,
"logpage": 35,
"revid": 118,
"params": {},
"type": "create",
"action": "create",
"user": "Johnson",
"timestamp": "2026-05-04T16:47:19Z",
"comment": ""
},
{
"logid": 44,
"ns": 6,
"title": "\u6587\u4ef6:Docker-architecture.webp",
"pageid": 0,
"logpage": 35,
"revid": 118,
"params": {
"img_sha1": "8plkknwx30120azvpk56jqfx82xzgpg",
"img_timestamp": "2026-05-04T16:47:19Z"
},
"type": "upload",
"action": "upload",
"user": "Johnson",
"timestamp": "2026-05-04T16:47:19Z",
"comment": ""
}
]
}
}