Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
Remove use of Dockerfile to force build from source
  • Loading branch information
maximilien authored Sep 28, 2023
1 parent 3c09584 commit 76cc1e6
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ There are two things you need to get started with the ghtrack CLI. From now on c

First, you need to get a developer, or admin account, for your `GitHub` ID. [Register](https://developer.github.com/program/), it's free. When you do, you can then create an access token in order to use the GitHub APIs v3 (or later).

Second, you need to setup your [environment](#Environment). See that section for details. However, note also that you can either setup your local machine with Python3 and the dependencies, or, alternatively, use the included [`Dockerfile`](Dockerfile) to create a container with the latest version and all the dependencies setup for you.
Second, you need to setup your [environment](#Environment). See that section for details. However, note also that you can either setup your local machine with Python3 and the dependencies.

You can also use one of my published images, or best, the latest one here: `docker.io/drmax/ghtrack:latest`. And then run the image locally and start an interactive BASH session with:

Expand Down Expand Up @@ -386,4 +386,4 @@ The following are immediate next steps:
1. add some common workflows (e.g., get reviews in last two months for k8s or knative)
2. look how to speed up some of the operations by caching intermediary data or Github APIs calls
3. make e2e tests faster (which might get there with solution for 2)
3. make e2e tests faster (which might get there with solution for 2)

0 comments on commit 76cc1e6

Please sign in to comment.