Skip to content

Commit ca8476d

Browse files
author
Juan Gabriel Guzman
committed
doc: #125 Updating documentation
1 parent 1caf8e6 commit ca8476d

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -264,7 +264,7 @@ docker run -p 5000:5000 time_tracker_api:local
264264

265265
## Migrations
266266
Looking for a DB-agnostic migration tool, the only choice I found was [migrate-anything](https://pypi.org/project/migrate-anything/).
267-
An specific requirement file was created to run the migrations in `requirements/migrations.txt`. This way we do not mix
267+
A specific requirement file was created to run the migrations in `requirements/migrations.txt`. This way we do not mix
268268
any possible vulnerable dependency brought by these dependencies to the environment `prod`. Therefore the dependencies
269269
to run the migrations shall be installed this way:
270270

@@ -274,16 +274,16 @@ pip install -r requirements/migrations.txt
274274
```
275275

276276
All the migrations will be handled and created in the python package `migrations`. In order to create a migration we
277-
must do it manually (for now) and prefixed by a number, e.g. `migrations/01-initialize-db.py` in order to warranty the
277+
must do it manually (for now) and prefixed by a number, e.g. `migrations/01-initialize-db.py` in order to guarantee the
278278
order of execution alphabetically.
279279
Inside every migration there is an `up` and `down` method. The `down` method is executed from the persisted migration in
280-
the database. Whe a `down` logic that used external dependencies was tested it failed, whilst I put that same logic in
281-
the an `up` method it run correctly. In general the library seems to present [design issues](https://github.com/Lieturd/migrate-anything/issues/3).
280+
the database. When a `down` logic that used external dependencies was tested, it failed; whilst, I put that same logic in
281+
the `up` method, it run correctly. In general, the library seems to present [design issues](https://github.com/Lieturd/migrate-anything/issues/3).
282282
Therefore, it is recommended to apply changes just in one direction: `up`.
283283
For more information, please check out [some examples](https://github.com/Lieturd/migrate-anything/tree/master/examples)
284-
that illustrates the usage of this migration tool.
284+
that illustrate the usage of this migration tool.
285285

286-
Basically, for running the migrations you must execute
286+
Basically, for running the migrations you must execute:
287287

288288
```bash
289289
migrate-anything migrations

0 commit comments

Comments
 (0)