git-annex/doc/required_content.mdwn

Required content settings can be configured to do more complicated
things than just setting the required number of [[copies]] of your data.
For example, you could require that data be archived in at least two
archival repositories, and also require that one copy be stored offsite.

The format of required content expressions is the same as
[[preferred_content]] expressions.

Required content settings can be edited using `git annex vicfg`
or set using `git annex required`.
Each repository can have its own settings, and other repositories will
try to honor those settings when interacting with it.

While [[preferred_content]] expresses a preference, it can be overridden
by simply using `git annex drop`. On the other hand, required content
settings are enforced; `git annex drop` will refuse to drop a file if
doing so would violate its required content settings.
(Although even this can be overridden using `--force`).

Also, `git-annex fsck` will warn about required contents that are not
present.
Added required content configuration. This includes checking when dropping files that any required content configuration is satisfied. However, it does not yet include an active check on the required content; the location log is trusted when checking the required content expression. 2014-03-29 19:20:55 +00:00			`Required content settings can be configured to do more complicated`
			`things than just setting the required number of [[copies]] of your data.`
			`For example, you could require that data be archived in at least two`
			`archival repositories, and also require that one copy be stored offsite.`

			`The format of required content expressions is the same as`
			`[[preferred_content]] expressions.`

required: New command, like wanted, but for required content. Also refactored some code to reduce duplication. 2015-04-18 20:04:25 +00:00			Required content settings can be edited using `git annex vicfg`
			or set using `git annex required`.
Added required content configuration. This includes checking when dropping files that any required content configuration is satisfied. However, it does not yet include an active check on the required content; the location log is trusted when checking the required content expression. 2014-03-29 19:20:55 +00:00			`Each repository can have its own settings, and other repositories will`
			`try to honor those settings when interacting with it.`

			`While [[preferred_content]] expresses a preference, it can be overridden`
			by simply using `git annex drop`. On the other hand, required content
			settings are enforced; `git annex drop` will refuse to drop a file if
			`doing so would violate its required content settings.`
			(Although even this can be overridden using `--force`).
fsck: Warn when required content is not present in the repository that requires it. This commit was sponsored by Jack Hill on Patreon. 2018-02-08 18:08:41 +00:00
			Also, `git-annex fsck` will warn about required contents that are not
			`present.`