From 89bcdb70fc387e6a47b673197ba91a70e775bb50 Mon Sep 17 00:00:00 2001 From: Kirill Bobykin Date: Wed, 8 May 2024 18:44:32 +0400 Subject: [PATCH] change --migration to --migrate in README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a01b027..a4140db 100644 --- a/README.md +++ b/README.md @@ -103,7 +103,7 @@ Args and environment variables can be tailored to a specific build phase by addi There may be times where feature detection plus flags just aren't enough. As an example, you may wish to configure and run multiple processes. * `--instructions=path` - a dockerfile fragment to be inserted into the final document. -* `--migration=cmd` - a replacement (generally a script) for `db:prepare`/`db:migrate`. +* `--migrate=cmd` - a replacement (generally a script) for `db:prepare`/`db:migrate`. * `--procfile=path` - a [Procfile](https://github.com/ddollar/foreman#foreman) to use in place of launching Rails directly. Like with environment variables, packages, and build args, `--instructions` can be tailored to a specific build phase by adding `-base`, `-build`, or `-deploy` after the flag name, with the default being `-deploy`.