Dat.json site manifest

Sites and applications served over dat:// can include a manifest file to set metadata and configure the site/application/archive. The file should be located at /dat.json in the root of the site. Beaker automatically manages the manifest for archives created via the Dat Web API.

{
  "url": "dat://4483a2..66/",
  "title": "Application Title",
  "description": "A short description of the app",
  "forkOf": ["dat://00fdc3..7a/"],
  "createdBy": {
    "title": "My Dat App",
    "url": "dat://15f17e..6a/"
  }
}

.url

The URL of the archive.

.title

A short but descriptive human friendly title.

.description

A one- or two-line description of the archive.

.forkOf

An array of URLs describing the fork history of the archive, starting from the oldest ancestor to the most recent. The first entry in the array is the URL of the original, and the last entry in the array is the URL of the most-recently forked.

If you fork a fork, there will be 2 items in the array:

forkOf: [grandparent-url (the original), parent-url]

If you fork again, there will be 3 items in the array:

forkOf: [great-grandparent-url (the original), grandparent-url, parent-url]

.createdBy

An object of {url:, title:} describing the application that created the archive.