Upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor.git synced 2025-02-02 21:11:37 +01:00
Code Issues Projects Releases Wiki Activity

update migration guide

Browse Source
This commit is contained in:
Henry Zhang 2016-07-12 18:22:22 +08:00
parent 0461ad3506
commit 65676d089e
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
migration/README.md
View File

@ -16,24 +16,25 @@ When upgrading your existing Habor instance to a newer version, you may need to
cp Deploy/harbor.cfg /tmp/harbor
```
2. Next, stop existing Harbor service if it is still running:
2. Next, stop and remove existing Harbor service if it is still running:
```
cd ../../Deploy/
cd Deploy/
docker-compose down
```
3. Get the lastest source code from Github:
3. Change to the parent directory of Harbor's source code folder (usually is the parent directory of `harbor/` ). Get the lastest source code from Github to overwrite the existing code:
```sh
$ git clone https://github.com/vmware/harbor
cd ../..
git clone https://github.com/vmware/harbor
```
4. Before upgrading Harbor, perform data migration first.
4. Before upgrading Harbor, perform database migration first.
The directory **migration/** contains the tool for migration. The first step is to update values of `db_username`, `db_password`, `db_port`, `db_name` in **migration.cfg** so that they match your system's configuration.
5. The migration tool is delivered as a container, so you should build the image from its Dockerfile:
```
cd migration/harbor-migration
cd migration/
docker build -t migrate-tool .
```