https://github.com/germancoding/le_version_info
Simple program to keep track of Let's Encrypts deployed version of Boulder
https://github.com/germancoding/le_version_info
Last synced: about 1 month ago
JSON representation
Simple program to keep track of Let's Encrypts deployed version of Boulder
- Host: GitHub
- URL: https://github.com/germancoding/le_version_info
- Owner: GermanCoding
- License: mit
- Created: 2022-06-15T21:23:02.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2024-03-05T16:21:00.000Z (over 2 years ago)
- Last Synced: 2025-01-10T01:29:02.379Z (over 1 year ago)
- Language: Rust
- Homepage: https://germancoding.com/boulder-version-history/
- Size: 563 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# le_version_info
Small utility to simply record at which point in time which Boulder version was deployed.
A live version of this can be found on my site: https://germancoding.com/boulder-version-history/
To build this program, you'll need:
1. Rust + Cargo (https://rustup.rs/)
2. If compiling under Linux: OpenSSL + OpenSSL development headers (see [this](https://github.com/seanmonstar/reqwest#requirements))
3. build-essential/native compiler (probably?)
Then, simply run cargo build --release to build the program (Cargo builds to the ./target directory).
## Example usage
./le_version_info file.json https://acme-v02.api.letsencrypt.org/build
Note that file.json must already exist and must contain a valid JSON array (empty is fine).
echo "[]" > file.json
Each invocation tries to contact the given URL, treating the output as a build. The JSON file is then updated accordingly.
You'll probably need to run this periodically to be useful.
## Web component
The web directory hosts the website that can be used as an example frontend
for this tool and is also what is running on my hosted version of this tool.
Too bootstrap this, you need to fetch a few dependencies, which can be done
automatically using the WEB_DEPENDENCY_DOWNLOAD.sh script
(requires a POSIX-compatible shell and wget). You will also need to ensure
that the web frontend can access the files generated by the tool
(the frontend expects files prod.json and staging.json
respectively).