6cccfeb97a
Factor code and reorganize location of go cache and go paths such that subsequent invocations reuse both dirs. |
||
|---|---|---|
| cmd/ooniprobe | ||
| config | ||
| data | ||
| docs | ||
| internal | ||
| nettests | ||
| scripts | ||
| testdata | ||
| utils | ||
| version | ||
| .dockerignore | ||
| .gitignore | ||
| .travis.yml | ||
| build.sh | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE.md | ||
| ooni_test.go | ||
| ooni.go | ||
| Readme.md | ||
OONI Probe CLI
The next generation OONI Probe Command Line Interface.
User setup
-
Go into the releases and download the release for your architecture and platform
-
Extract the tarball with
tar xvzf ooniprobe_*.tar.gz -
Copy the
ooniprobebinary into a location in your$PATH, for example/usr/local/bin/ooniprobe -
Run
ooniprobe runto perform all the tests
Optional:
Add a crontab entry (on linux) to run ooniprobe daily at a random time:
(crontab -l 2>/dev/null; echo "$(( ( RANDOM % 60 ) + 1 )) $(( ( RANDOM % 24 ) + 1 )) * * * ooniprobe run") | crontab -
Development setup
Be sure you have golang >= 1.13. We use Go modules. Make sure you don't have GOPATH set.
Run
./build.sh help
to get information on the supported systems as well as to get instructions on how to install dependencies.
Releasing
./build.sh release
and follow instructions.