You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: atr/docs/storage-interface.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,7 @@ Only a small number of subdirectories of the state directory are written to by t
150
150
*`attestable`, configured by `ATTESTABLE_STORAGE_DIR`
151
151
*`downloads`, configured by `DOWNLOADS_STORAGE_DIR`
152
152
*`finished`, configured by `FINISHED_STORAGE_DIR`
153
-
*`svn`, configured by `SVN_STORAGE_DIR`
153
+
*`subversion`, configured by `SVN_STORAGE_DIR`
154
154
*`tmp`, which is unconfigurable
155
155
*`unfinished`, configured by `UNFINISHED_STORAGE_DIR`
156
156
@@ -159,15 +159,15 @@ And the purposes of these directories is as follows. Note that "immutable" here
159
159
*`attestable`[**immutable**] holds JSON files of data that ATR has automatically verified and which must now be held immutably. (We could store this data in the database, but the aim is to eventually write attestation files here, so this prepares for that approach.)
160
160
*`downloads`[**mutable**] are hard links to released artifacts in the `finished` directory. The `finished` directory contains the files exactly as they were arranged by the release managers upon announcing the release, separated strictly into one directory per release. The `downloads` folder, on the other hand, has no restrictions on its organisation and can be rearranged.
161
161
*`finished`[**immutable**, except for moving to external archive] contains, as mentioned above, all of the files of a release as they were when announced. This therefore constitutes an historical record and allows us to rewrite the hard links in the `downloads` directory without having to consider not accidentally deleting files by removing all references, etc.
162
-
*`svn`[**mutable**] is designed to mirror two subdirectories, `dev` and `release`, of `https://dist.apache.org/repos/dist`. This is currently unused.
162
+
*`subversion`[**mutable**] is designed to mirror two subdirectories, `dev` and `release`, of `https://dist.apache.org/repos/dist`. This is currently unused.
163
163
*`tmp`[**mutable**] holds temporary files during operations where the data cannot be modified in place. One important example is when creating a staging directory of a new revision. A subdirectory with a random name is made in this directory, and then the files in the prior version are hard linked into it. The modifications take place in this staging area before the directory is finalised and moved to `unfinished`.
164
164
*`unfinished`[**immutable**, except for moving to `finished`] contains all of the files in a release before it is announced. In other words, when the release managers compose a release, when the committee votes on the release, and when the release has been voted on but not yet announced, the files for that release are in this directory.
165
165
166
166
This list does not include any configuration files, logs, or log directories.
167
167
168
168
## How should the filesystem be backed up?
169
169
170
-
Only the `attestable`, `downloads`, `finished`, and `unfinished` directories need to be backed up. The `svn` directory is unused, and the `tmp` directory is for temporary staging.
170
+
Only the `attestable`, `downloads`, `finished`, and `unfinished` directories need to be backed up. The `subversion` directory is unused, and the `tmp` directory is for temporary staging.
171
171
172
172
The structure of the directories that need backing up is as follows. An ellipsis, `...`, means any number of further files or subdirectories containing subdirectories or files recursively.
0 commit comments