The JFrog Platform hosts local, remote. virtual and federated repositories. Local and remote repositories are true physical repositories, while a virtual repository is actually an aggregation of these repositories, which is used to create controlled domains for search and resolution of artifacts. For more information, see Repository Management.
Rules and guidelines when working with repositories:
Platform Admins can both create new repositories and assign existing resources, whereas Project Admins can only create new repositories.
Working with Federated Repositories in Projects
Federated Repositories are first created under the Assigned tab, and can then be assigned to a project, by the Platform Admin
Local and remote repositories can be created in one project and assigned to other projects.
Each repository is assigned to a single environment. If an environment is not chosen when creating the repository, it is assigned to the DEV environment by default.
Multiple environments can be created within a project. In addition, global environments can also be used within a project. See Environments.
You can assign a set of roles to project members for each environment, providing you with an additional layer of role-based access granularity. See Managing Project Roles and Members.
Repositories created in the project receive the Project Key added as a prefix to the repository name.
The following example shows how to assign the Docker-Local and Generic-local repositories to the US_Dev project.
The following example shows how to create a remote Docker repository and set the environment to DEV within the US Dev project. Note that the us-dev project prefix was added to the docker_remote repository.
