Jasper Vaneessen 9a5fc674f3
style: Enforce linting rules on markdown files
* chore: add markdownlint-cli2 and config for mkdocs

* style: enforce linting rules on mkdocs md files

* chore: tweaks to markdownlint rules

* style: linting changelog

* style: linting release notes

* style: linting .github md files

* style: further linting of docs

* style: linting readmes

* chore: update linting script entries

* docs: tweak release after rebase

* chore: simplify root md linting config

* chore: extend base config

* chore: implement requested changes

* chore: remove unnecessary exception

* chore: fix comment type

* styling: single config + list spacing

* chore: implement requested changes

* chore: use .cjs files for markdownlint config

* chore: implement requested changes
2022-08-25 11:32:09 +02:00

1004 B

How to seed Accounts and Pods

If you need to seed accounts and pods, the --seededPodConfigJson command line option can be used with as value the path to a JSON file containing configurations for every required pod. The file needs to contain an array of JSON objects, with each object containing at least a podName, email, and password field.

For example:

[
  {
    "podName": "example",
    "email": "hello@example.com",
    "password": "abc123"
  }
]

You may optionally specify other parameters as described in the Identity Provider documentation.

For example, to set up a pod without registering the generated WebID with the Identity Provider:

[
  {
    "podName": "example",
    "email": "hello@example.com",
    "password": "abc123",
    "webId": "https://id.inrupt.com/example",
    "register": false
  }
]

This feature cannot be used to register pods with pre-existing WebIDs, which requires an interactive validation step.