Skip to content

Commit 4b42fbe

Browse files
authored
Merge pull request #172 from creativecommons/doc-run-scripts
Add Running the scripts section to repository README
2 parents dc5ede3 + 5c5cc04 commit 4b42fbe

File tree

1 file changed

+18
-5
lines changed

1 file changed

+18
-5
lines changed

README.md

Lines changed: 18 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -122,10 +122,9 @@ modules:
122122
[homebrew]: https://brew.sh/
123123

124124

125-
### Running scripts that require client credentials
125+
### Managing client credentials
126126

127-
To successfully run scripts that require client credentials, you will need to
128-
follow these steps:
127+
Client credentials should be stored in an environment file:
129128
1. Copy the contents of the `env.example` file in the script's directory to
130129
`.env`:
131130
```shell
@@ -138,8 +137,22 @@ follow these steps:
138137
GCS_CX = your_pse_id
139138
```
140139
3. Save the changes to the `.env` file.
141-
4. You should now be able to run scripts that require client credentials
142-
without any issues.
140+
141+
You should now be able to run scripts that require client credentials without
142+
any issues. The `.env` file is ignored by git to help ensure sensitive data is
143+
not distributed.
144+
145+
146+
### Running the scripts
147+
148+
All of the scripts should be run from the root of the repository using pipenv. For example:
149+
```bash
150+
pipenv run ./scripts/1-fetch/github_fetch.py -h
151+
```
152+
153+
When run this way, the shared library (`scripts/shared.py`) provides easy access
154+
to all of the necessary paths and all of the modules managed by pipenv are
155+
available.
143156
144157
145158
### Static analysis

0 commit comments

Comments
 (0)