This topic describes the Hex local and remote repositories layout and permissions you can apply.
Hex Local Repository Layout
The following is the Hex Local Repository Layout.
Note
All the uploaded tar files must be under the tarballs directory as tarballs/[name]-[version].tar.
<repository name>
├── names
├── versions
├── installs
|-- hex-1.x.csv
├── packages
|-- <package-name>
├── tarballs
|-- <package-name>-<package-version>.tarrepository name - Name of the repository
names - Name details of a package
versions - Version details of a package
installs - Metadata uploaded for the package
packages - Metadata of packages uploaded in the local
tarballs - Packages uploaded in the local repository
Hex Remote Repository Layout
<REPOSITORY_NAME>
├── installs
|-- hex-1.x.csv
├── packages
|-- <package-name>
├── tarballs
|-- <package-name>-<package-version>.tarInstalls - Metadata pulled from the remote
packages - The package metadata pulled from the remote
tarballs - Redistributable binaries for each package pulled from the remote
Permissions on Hex Remote Repository Directories
You can provide granular permissions for users to specific packages. To limit access, apply permissions to each of the layout folders.
For example, to exclude packages that start with abc in the hex repository, add Exclude Patterns for each layout folder as:
installs/abc*
tarballs/abc*
packages/abc*
To learn more, refer to the following: