Adding 'Remote migration files' sub-section.
This commit is contained in:
12
README.md
12
README.md
@@ -158,6 +158,18 @@ $ migrate -path=./migrations -database=$EXAMPLE_DSN force 1
|
||||
|
||||
Once you force the version, the database is considered 'clean' and you should be able to run migrations again without any problem.
|
||||
|
||||
### Remote migration files
|
||||
|
||||
The migrate tool also supports reading migration files from remote sources including Amazon S3 and GitHub repositories. For example :
|
||||
|
||||
```bash
|
||||
$ migrate -source="s3://<bucket>/<path" -database=$EXAMPLE_DSN up
|
||||
$ migrate -source="github://owner/repo/path#ref" -database=$EXAMPLE_DSN up
|
||||
$ migrate -source="github://user:personal-access-token@owner/repo/path#ref" -database=$EXAMPLE_DSN up
|
||||
```
|
||||
|
||||
More information about this functionality and a full list of the supported remote resources can be [found here](https://github.com/golang-migrate/migrate#migration-sources).
|
||||
|
||||
## Additional Information
|
||||
|
||||
### How different Go Types are encoded
|
||||
|
||||
Reference in New Issue
Block a user