Go to file
Steven Zou 0227a1315a Keep the chart server related configurations in adminserver
append chart server related config options to the supporting list of adminserver
provide chart server related config access method in the API layer
update prepare script and ui env template file to enable cache driver config for chart server API
append flag info in the systeminfo API to indicate if chart server is deployed with Harbor
refactor the response rewriting logic to return structual error object
add api init method to initilizing objects required in API handlers
chage owner of the storage folder
update offline/online package scripts in Harbor-Util.robot
2018-07-20 19:40:33 +08:00
.github
contrib Fix the mismatch of property used in helm chart 2018-07-18 17:56:52 +08:00
docs
make Keep the chart server related configurations in adminserver 2018-07-20 19:40:33 +08:00
src Keep the chart server related configurations in adminserver 2018-07-20 19:40:33 +08:00
tests Keep the chart server related configurations in adminserver 2018-07-20 19:40:33 +08:00
tools
.drone.ova.yml
.drone.yml
.gitignore
.gitmessage Update README and .gitmessage 2018-07-17 16:42:03 +08:00
.travis.yml Keep the chart server related configurations in adminserver 2018-07-20 19:40:33 +08:00
AUTHORS
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md
LICENSE
Makefile Keep the chart server related configurations in adminserver 2018-07-20 19:40:33 +08:00
NOTICE
open_source_license Update Makefile and OSL (#5337) 2018-07-19 15:47:37 +08:00
partners.md
README.md Update README and .gitmessage 2018-07-17 16:42:03 +08:00
ROADMAP.md
VERSION

Harbor

Build Status Coverage Status

Note: The master branch may be in an unstable or even broken state during development. Please use releases instead of the master branch in order to get stable binaries.

Harbor

Project Harbor is an an open source trusted cloud native registry project that stores, signs, and scans content. Harbor extends the open source Docker Distribution by adding the functionalities usually required by users such as security, identity and management. Having a registry closer to the build and run environment can improve the image transfer efficiency. Harbor supports replication of images between registries, and also offers advanced security features such as user management, access control and activity auditing.

Features

  • Role based access control: Users and repositories are organized via 'projects' and a user can have different permission for images under a project.
  • Policy based image replication: Images can be replicated (synchronized) between multiple registry instances, with auto-retry on errors. Great for load balancing, high availability, multi-datacenter, hybrid and multi-cloud scenarios.
  • Vulnerability Scanning: Harbor scans images regularly and warns users of vulnerabilities.
  • LDAP/AD support: Harbor integrates with existing enterprise LDAP/AD for user authentication and management.
  • Image deletion & garbage collection: Images can be deleted and their space can be recycled.
  • Notary: Image authenticity can be ensured.
  • Graphical user portal: User can easily browse, search repositories and manage projects.
  • Auditing: All the operations to the repositories are tracked.
  • RESTful API: RESTful APIs for most administrative operations, easy to integrate with external systems.
  • Easy deployment: Provide both an online and offline installer.

Install & Run

System requirements:

On a Linux host: docker 1.10.0+ and docker-compose 1.6.0+ .

Download binaries of Harbor release and follow Installation & Configuration Guide to install Harbor.

Refer to User Guide for more details on how to use Harbor.

Community

Twitter: @project_harbor
User Group: Join Harbor user email group: harbor-users@googlegroups.com to get update of Harbor's news, features, releases, or to provide suggestion and feedback. To subscribe, send an email to harbor-users+subscribe@googlegroups.com .
Developer Group: Join Harbor developer group: harbor-dev@googlegroups.com for discussion on Harbor development and contribution. To subscribe, send an email to harbor-dev+subscribe@googlegroups.com.
Slack: Join Harbor's community for discussion and ask questions: VMware {code}, channel: #harbor.

Demo Server: Harbor provides a demo environment with the latest Harbor stable build installed. If you want to have a try, please refer to Demo Server for more details.

More info on partners and users.

Contribution

We welcome contributions from the community. If you wish to contribute code and you have not signed our contributor license agreement (CLA), our bot will update the issue when you open a pull request. For any questions about the CLA process, please refer to our FAQ. Contact us for any questions: email.

Demos

License

Harbor is available under the Apache 2 license.

This project uses open source components which have additional licensing terms. The official docker images and licensing terms for these open source components can be found at the following locations:

Commercial Support

If you need commercial support of Harbor, please contact us for more information: email.