-
Notifications
You must be signed in to change notification settings - Fork 98
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
docs: restructure readme #46
Conversation
This looks fine to me, but probably needs a closer look from someone closer to the project @shalinnijel2 @tropxy |
poetry install | ||
|
||
poetry-shell: | ||
poetry shell |
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.
As this could fail if poetry is not available, would it perhaps be better if there is a 'pip install poetry' before 'poetry install'?
The following command provides a helper for the script usage: | ||
|
||
```bash | ||
$ cd iso15118/shared/pki/ |
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.
Nice...helps with copy pasting to terminal from readme...
9c4e0d6
to
9f2ef0a
Compare
9f2ef0a
to
f103a78
Compare
This PR reorganizes the readme so that it better presents the information the user needs to get up and running locally.
It also changes one of the make commands to use Poetry rather than pip, and adds a recommendation to use
poetry shell
in local development -- this automatically activates the appropriate virtual environment once it is created.One question @tropxy @shalinnijel2 : Was docker-compose.prod.yml intended to be used for production at some point? I understand we're not going to be deploying with Docker -- is this obsolete?