From eb0dea9d346701ed2746d7c0ef94f45be002301e Mon Sep 17 00:00:00 2001 From: Docker Library Bot Date: Mon, 23 Dec 2019 19:11:54 +0000 Subject: [PATCH] Run update.sh --- notary/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/notary/README.md b/notary/README.md index 711426149..f6ca4f136 100644 --- a/notary/README.md +++ b/notary/README.md @@ -121,7 +121,7 @@ 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.