5aa8c4211e
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEc4h3qmyCnyakMcX0gLaRJ3cz2VsFAmBPa/oACgkQgLaRJ3cz 2Vu4qQ/+NKzgVlYLsS0JHmFCB2JGFy7LusCQhrNGapZfdw1nj5q+OaJ7q2whkT62 pdciRdV8sa7rYe4jnf5a1DGj1F0ijV0Zvpx1oJPAwlyY1XhIdlSD3S1N6eS6mpW7 6fxvMjQKErsZrZkTB9oIU1b70Tl6nCZUnSep0Y2eMwJg2/RtoT4JCyh4yBeq0iQ9 Mb+b85Q8wHIlUryPz8vvNEx5pI48m7M9o5sl+Rp1HCUdPNmO5zUrrAzyFch9H6+I Qr0OOz0YHZHYESJ0gpuJ2lvQNMH6J/f8omv8kGVuVw9NaU2yM7hh2NJmXunfp9C3 lPIGK1tFIb+kPRYtEzDy8eZ3Y+49WcOUmKl4d+O4FIi/T/issswaXRNMSBhr5//8 QVw0FxCIXKjV9tzHK5c4JmLeQtR/OpYLlr420pSvn7uZ9h9WYjtkzVzl5wLqd45E w8/LBUAWa1rKD+OnHqVpP+A359s5QqIZkiBzxOpYZBRX4k1VzsBiK+JvF095O/AP KjS1xmVn5w9RTUESKamNdMwf4fJBFs8TbHxOdfCa7lD26H63UPGtoJE3kurbyRGK DVJRnNwWE32au3PupuCvkqDkIJWXPrjzx3i+i4ryNPxv2ZXM+Lmwl0GM/qZyyV5N JAlCiIf0J4V8yQOiVsyUWJ0PfGqjASG2rQxzMsHHnLcIAvrnzIM= =ywZe -----END PGP SIGNATURE----- Merge tag 'v3.8.0' into mobile-staging ooni/probe-cli v3.8.0 |
||
---|---|---|
.github/workflows | ||
CLI | ||
cmd | ||
debian | ||
docs | ||
E2E | ||
internal | ||
MOBILE | ||
pkg | ||
QA | ||
.gitignore | ||
build-android.bash | ||
build-ios.bash | ||
build-miniooni.sh | ||
build.sh | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
go.mod | ||
go.sum | ||
LICENSE.md | ||
publish-android.bash | ||
publish-ios.bash | ||
Readme.md | ||
smoketest.sh | ||
testjafar.bash |
OONI Probe Client Library and CLI
The next generation OONI Probe: client library and Command Line Interface.
User setup
Please, follow the instructions at ooni.org/install/cli
to install ooniprobe
. If we do not support your use case, please let us know.
Once ooniprobe
is installed, try ooniprobe help
to get interactive help.
Reporting issues
Please, report issues with this codebase at github.com/ooni/probe.
Please, make sure you tag such issues using the ooni/probe-cli
label.
Repository organization
Every top-level directory contains an explanatory README file.
Development setup
Be sure you have golang >= 1.16 and a C compiler (when developing for Windows, you need Mingw-w64 installed).
You need to download assets first using:
go run ./internal/cmd/getresources
Then you can build using:
go build -v ./cmd/ooniprobe
This will generate a binary called ooniprobe
in the current directory.
Android bindings
./build-android.bash
We automatically build Android bindings whenever commits are pushed to the
mobile-staging
branch. Such builds could be integrated by using:
implementation "org.ooni:oonimkall:VERSION"
Where VERSION is like 2020.03.30-231914
corresponding to the
time when the build occurred.
iOS bindings
./build-ios.bash
We automatically build iOS bindings whenever commits are pushed to the
mobile-staging
branch. Such builds could be integrated by using:
pod 'oonimkall', :podspec => 'https://dl.bintray.com/ooni/ios/oonimkall-VERSION.podspec'
Where VERSION is like 2020.03.30-231914
corresponding to the
time when the build occurred.
Updating dependencies
go get -u -v ./... && go mod tidy
Releasing
-
update binary data as described above;
-
update
internal/version/version.go
; -
make sure you have updated dependencies;
-
run
./build.sh release
and follow instructions.