The dashboard is seen upon login to the Admin Portal. It provides you with an overview of your account, based on what you have permissions to see.
Here is an example view of a dashboard for an organization who just signed up and has created two repositories and three users.
CloudRepo support all maven based build tools using standard configuration options (no plugins or add ons required).
Supported build tools include:
- Simple Build Tool (SBT)
CloudRepo provides support for Python (PiP) based repositories by providing a Python Package Index (PyPi) compatible API.
If you have private artifacts that you don’t want to store in the public PyPi instance, CloudRepo can provide you with a private place to store them.
The core feature of CloudRepo is Repository Management. We allow you to Management as many repositories as your team needs.
Looking for additional information? See the detailed documentation on Repository Management.
Public Repositories are used when you want to widely distribute artifacts that your team produces to the rest of the world.
Examples of use cases that benefit from public artifact repositories:
- Open Source Libraries
- SDK Publishers
Read access to public repositories is available to anyone with an internet connection. No authentication is performed and so your artifacts are made available to the public.
Write access always requires authentication and occurs on a separate URL than the public read URL.
If you attempt to publish artifacts to the repository’s public URL, the publish event will fail.
Private Repositories are the default repository type in CloudRepo. They are used for internal software development and distribution.
Private Repositories require authenticated access for both read and write operations.
Proxy repositories allow you to proxy access to a publicly accessible Maven Repository (like Maven Central). This allows you to store a copy of all your dependencies within CloudRepo automatically.
Proxy Repositories are available for Maven Repositories and more details can be found in the Proxy Repositories documentation.
In order to provide access to your repositories, you’ll have to manage your users in User Management.
Additional information can be found in the User Management Documentation.
Access is controlled through two types of users: Read Only and Read/Write.
We are currently building a more robust version of access control, including groups and permissions. Please Contact Us if you have a particular use case you’d like to share.
Read Only Users¶
Read Only Users are for those who don’t want to allow public access to their repositories but still want to allow read only access to a CloudRepo repository.
A read only user must still authenticate when retrieving artifacts but they are limited to reading from the repositories - ie they many not publish or upload artifacts.
A typical usage of read only users is to create read only users for your developers, who only need to download artifacts. Publishing of new artifacts can be restricted to your Continuous Integration process to ensure that there is only one path for new artifacts to enter your system.
Read/Write users have full access to repositories. They can read all the artifacts as well as upload and delete existing ones.
Most customers restrict who has access to read/write by granting read only to developers and read/write to their continuous deployment pipelines.
Custom Domain Names¶
Custom domain names enable you to access your repositories via a domain you control.
For example, you may prefer to have a branded repository such as repo.mydomain.com.
Custom Domains are only available to our business tier customers.