More linking

This commit is contained in:
Stuart Clements 2019-12-17 15:22:30 +01:00
parent 6fed9b5b88
commit ea84990551
10 changed files with 58 additions and 5 deletions

View File

@ -47,7 +47,7 @@ This section describes how to use and maintain Harbor after deployment. These da
- [Garbage Collection](administration/garbage_collection/_index.md)
- [Upgrading Harbor](administration/upgrade/_index.md)
- [Upgrade Harbor and Migrate Data](administration/upgrade/upgrade_migrate_data.md)
- [Roll Back an Upgrade](administration/upgrade/roll_back_upgrade.md)
- [Roll Back an Upgrade](administration/upgrade/roll_back_upgrade.md)
- [Manage the Harbor Instance](administration/manage_harbor/_index.md)
- [Access Harbor Logs](administration/manage_harbor/access_logs.md)

View File

@ -1,3 +1,11 @@
# Build, Customize, and Contribute to Harbor
This section describes how developers can build from Harbor source code, customize their deployments, and contribute to the open-source Harbor project.
- [Build Harbor from Source Code](compile_guide.md)
- [Developing the Harbor Frontend](ui_contribution_get_started.md)
- [Customize the Harbor Look & Feel ](customize_look_feel.md)
- [Developing for Internationalization](developer_guide_i18n.md)
- [Using Make](use_make.md)
- [View and test Harbor REST API via Swagger](configure_swagger.md)
- [Registry Landscape](registry_landscape.md)

View File

@ -6,3 +6,7 @@ After you have deployed Harbor, you must perform certain post-deployment configu
- [Configure Notary Content Trust](configure_notary_content_trust.md)
- [Reconfigure Harbor and Manage the Harbor Lifecycle](reconfigure_manage_lifecycle.md)
- [Access Harbor Logs](access_logs.md)
----------
[Back to table of contents](../../_index.md)

View File

@ -1,3 +1,7 @@
[Back to table of contents](../../_index.md)
----------
# Authentication Modes and User Accounts
Harbor supports different modes for authenticating users and managing user accounts.
@ -160,3 +164,7 @@ sh docker login -u testuser -p <i>cli_secret</i> jt-test.local.goharbor.io
</pre>
**NOTE**: The CLI secret is associated with the OIDC ID token. Harbor will try to refresh the token, so the CLI secret will be valid after the ID token expires. However, if the OIDC Provider does not provide a refresh token or the refresh fails, the CLI secret becomes invalid. In this case, log out and log back in to Harbor via your OIDC provider so that Harbor can get a new ID token. The CLI secret will then work again.
----------
[Back to table of contents](../../_index.md)

View File

@ -1,3 +1,7 @@
[Back to table of contents](../../_index.md)
----------
# Configure Notary Content Trust
In harbor.yml, make sure https is enabled, and the attributes `ssl_cert` and `ssl_cert_key` are pointed to valid certificates. For more information about generating https certificate please refer to: [Configuring HTTPS for Harbor](configure_https.md)
@ -24,3 +28,7 @@ Because by default the local directory for storing meta files for notary client
alias notary="notary -s https://192.168.0.5:4443 -d ~/.docker/trust --tlscacert /etc/docker/certs.d/192.168.0.5/ca.crt"
```
----------
[Back to table of contents](../../_index.md)

View File

@ -1,3 +1,7 @@
[Back to table of contents](../../_index.md)
----------
# Customize the Harbor Token Service
Harbor requires Docker client to access the Harbor registry with a token. The procedure to generate a token is like [Docker Registry v2 authentication](https://github.com/docker/distribution/blob/master/docs/spec/auth/token.md). Firstly, you should make a request to the token service for a token. The token is signed by the private key. After that, you make a new request with the token to the Harbor registry, Harbor registry will verify the token with the public key in the rootcert bundle. Then Harbor registry will authorize the Docker client to push/pull images.
@ -57,4 +61,6 @@ $ cp /root/cert/root.crt ../registry/root.crt
6.Then you can push/pull images to see if your own certificate works. Please refer [User Guide](https://github.com/goharbor/harbor/blob/master/docs/user_guide.md) for more info.
----------
[Back to table of contents](../../_index.md)

View File

@ -1,3 +1,7 @@
[Back to table of contents](../../_index.md)
----------
# Administrator Options
## Managing Project Creation
@ -22,3 +26,7 @@ The push refers to a repository [10.117.169.182/demo/ubuntu]
0271b8eebde3: Preparing
denied: The system is in read only mode. Any modification is prohibited.
```
----------
[Back to table of contents](../../_index.md)

View File

@ -3,3 +3,6 @@
- [Configure Authentication](configure_authentication.md)
- [Other General Settings](general_settings.md)
----------
[Back to table of contents](../../_index.md)

View File

@ -1,3 +1,7 @@
[Back to table of contents](../../_index.md)
----------
# Reconfigure Harbor and Manage the Harbor Lifecycle
You can use `docker-compose` to manage the lifecycle of Harbor. Some useful commands are listed below. You must run the commands in the same directory as `docker-compose.yml`.
@ -71,3 +75,6 @@ $ sudo docker-compose up -d
Please check the [Docker Compose command-line reference](https://docs.docker.com/compose/reference/) for more on docker-compose.
----------
[Back to table of contents](../../_index.md)

View File

@ -2,5 +2,6 @@
This section describes how users with the developer, master, and project administrator roles manage and participate in Harbor projects. The Harbor administrator can also perform all of these tasks.
- [Project Creation](project_overview.md)
- [Project Configuration](project_configuration.md)
- [Working with Images, Tags, and Helm Charts](working_with_images.md)