Create a Repository

In order to create a new repository, go to Repositories by clicking the corresponding entry in the left menu.

alt text

Open the New repository dialog by clicking the blue Create + button in the top right corner of the page.

alt text

Fill in the blanks correctly:

  • Name: a unique identifier for this repository. Even when this repository is deleted, this name is still unique and cannot be reused by other repositories.
  • Publication URI: the external facing URL that users will see. It will be used in UI pages that RDepot users see. In our local demo deployment, this tends to be http://localhost/repo/<repository-name> (as the included web proxy will redirect /repo/ requests to the associated repository web server).
  • Server address: the (internal) URL that the RDepot manager uses when synchronizing changes to the repository. This should be set to the location of the RDepot Repo API. In our local demo deployment, this tends to be http://oa-rdepot-repo:8080/<technology>/<repository-name> (oa-rdepot-repo is the hostname of the RDepot Repo API Docker container in the demo docker-compose.yaml). The icon button next to it will run a check to see whether the RDepot manager can reach the specified server address of the RDepot Repo API.
  • Technology: one of the supported technologies, e.g. R or Python.
  • (R only) Redirect to source: when installing binary R packages, the repository web server will try to redirect missing binary R packages to the same (or newer) source R package within the same repository instead, before failing with a HTTP 404. This also may require additional configuration in the web proxy or web server, depending on your deployment. This additional configuration is already included in our local demo deployment.
  • Requires authentication: checking this will cause the RDepot UI to show the install command to use when a repository requires authentication. For R repositories, installing packages requires using crane and for Python repositories, installing packages requires using crane-pip.

Additional notes on the Publication URI: the /repo/ part of the Publication URI depends on the deployment. When hosting RDepot and the repository under the same domain, using a subpath will most likely be necessary (but another subpath can be used, as this is used to route traffic to the repository web server). When hosting both RDepot and the repository on separate domains (for example, rdepot.example.com for RDepot and repos.example.com for the repository web server) it is not necessary to use a subpath, as routing can be done based on the (sub)domain.

Additional notes on the Server address: since RDepot v2.6.0 it is recommended to include the technology (r/python) as part of the URL. Not doing so will cause a deprecation warning to be shown in the UI. From RDepot v3.0, this will be mandatory.

Then create the repository by clicking the corresponding blue submit button.

alt text

Your repository will be displayed as a new entry in the repositories table.