documentation groups

With InterDiode, one can create groups of HTMl archives. These archives will be transferred to your internal network and can be browsed online.

Creation

Usage

Accepted archives are zip, tar, tar.bz2, tar.gz, tar.xz, tar.zst, and tar.lzma files. Uploaded files are automatically transferred to your internal network, uncompressed and can be browsed online. Common index files are detected and are used as starting point for browsing: index.html, index.htm, index.md, index.txt, contents.html, README.html, readme.html or README.md.

Access Control

Several permission levels are available and can be assigned to users individually or by groups. The accesses granted by default to anonymous or simply authenticated users can also be selected.

  • no access: has no access at all..

  • reader: can only read pages..

  • proposer: can propose new files that must be reviewed..

  • simple writer: can also add new documents and change its own data..

  • admin: can change settings and access controls..

Only local administrators can change access controls, and default permissions for anonymous and simply authenticated users are transferred to the red side only during the first synchronization.

User preferences

Each user can set their own preferences, like pining it as a favorite source or creating a authentication token specific to it.

Resolve transfer issues

If a problem occurred during a transfer and both sides are out of sync, it is possible to force a resynchronization by sending all or part of the data again.

Deletion

If you want to delete this source, you must delete on both sides, starting with the black side to avoid any risk of data transfer to the red side after deletion. Once deleted, the source will no longer be available, and the related data will be removed during background cleanup tasks.

File integrity verification

Each file is stored along with its SHA256 digest, allowing to verify the integrity of the file and to detect any changes or corruption.

When you download a file, you can check its digest against the expected value to ensure that the file has not been tampered with or corrupted during transfer. This digest is provided in the HTTP headers, both Content-Digest (following the RFC 9530) and Digest. This can be done using various tools, such as command-line utilities or programming libraries that support digest verification. The digest is calculated using the SHA-256 algorithm and is encoded in Base64 format.

curl -L -v -I [URL]
# the -I option retrieves only the headers, and the -v option shows the details of the request and response, including the headers
Digest: sha-256=VqiR0u1OsX0ZGPCDVG9mlRjei0DC76I6r1+FXEhmuIs=
Content-Digest: sha-256=:VqiR0u1OsX0ZGPCDVG9mlRjei0DC76I6r1+FXEhmuIs=:

Propositions

A user with the appropriate permission can make a proposition, which must be validated by an administrator.

Any user with sufficient permissions can also propose new elements, which must be validated by a local administrator to be added to the synchronization. Such permission can be granted to users individually or by groups, and the list of users and groups with this permission is visible in the settings panel.