From 30cc54da0fb297437cf6d0e7f4ae980ec71f8834 Mon Sep 17 00:00:00 2001 From: Marco Franssen Date: Mon, 23 Dec 2019 11:56:58 +0100 Subject: [PATCH] Update repository link for migration-tool --- notary/content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/notary/content.md b/notary/content.md index f354e6d60..dccccf7ee 100644 --- a/notary/content.md +++ b/notary/content.md @@ -75,6 +75,6 @@ For more details on how to configure your Notary signer, please read the [docs]( ## Database Migrations -Notary server and signer both use the [migrate tool](https://github.com/mattes/migrate) to manage database updates. The migration files can be found [here](https://github.com/theupdateframework/notary/tree/master/migrations/) and are an ordered list of plain SQL files. The migrate tool manages schema versions to ensure that migrations start and end at the correct point. +Notary server and signer both use the [migrate tool](https://github.com/golang-migrate/migrate) to manage database updates. The migration files can be found [here](https://github.com/theupdateframework/notary/tree/master/migrations/) and are an ordered list of plain SQL files. The migrate tool manages schema versions to ensure that migrations start and end at the correct point. We strongly recommend you create separate databases and users with restricted permissions such that the server cannot access the signer's database and vice versa.