-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improving the quick start documentation #52
Conversation
Codecov Report
@@ Coverage Diff @@
## master #52 +/- ##
=======================================
Coverage 56.35% 56.35%
=======================================
Files 14 14
Lines 598 598
Branches 81 81
=======================================
Hits 337 337
Misses 254 254
Partials 7 7
Continue to review full report at Codecov.
|
docs/quickstart.rst
Outdated
@@ -1,6 +1,68 @@ | |||
Quickstart | |||
========== | |||
|
|||
Use *septentrion* as your migration tool in 2 easy steps: | |||
1. Write your migrations. | |||
2. Run your migrations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
README.rst
Outdated
│ ├── fixtures_0.1.sql | ||
│ └── fixtures_1.0.sql | ||
└── schemas | ||
└── schema_0.1.sql |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could prune the tree a bit. I'm not sure it needs to be this long to understand.
(We could skip the fixtures too)
The final version you target is a required argument (it might change in the future). | ||
|
||
# TODO : do we want to add something about dry-run here? | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we put a conclusion sentence here, summarizing what the user did (congratulations could be nice too)
Nicely done, a very successful start. Congratulations, @SdgJlbl ! |
|
||
- Either your environment variables `PGHOST`, `PGPORT` and `PGUSER` are properly set. | ||
- Or you can set the environment variables `SEPTENTRION_HOST`, `SEPTENTRION_PORT`, `SEPTENTRION_USERNAME`. | ||
- configuration file `septentrion.ini` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like this bullet point is not done :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WIP commit is WIP indeed :D
|
||
.. code-block:: console | ||
|
||
[VERSION]-[MIGRATION]-[ORDER]-[TYPE].sql |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An example would be great I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here. All of the "how-to" content has been put there hastily, but we'll get a better look at it later.
|
||
.. code-block:: console | ||
|
||
$ septentrion --target-version 1.0 migrate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We currently can't run the first migration wthout a schema and a version. And the schema isn't visible in the show-migrations
output :-(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Related issue for discussion #54
Co-authored-by: samuelhamard <[email protected]>
b66529b
to
691a7de
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking sharp! It seems it will soon be out of WIP. Good luck for the next steps, and congrats already.
This is a first draft concerning the quick start guide in documentation.
I have some questions (as "comments") in the rst. I'm struggling a bit with the level of details we want to provide here (minimal I guess, but I'm not familiar enough with SQL migration to know how much is needed).
Comments welcome :)
Stuff remaining to do:
Successful PR Checklist: