ripinfo
banner
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ripinfo
-
What's everyone working on this week (12/2023)?
As a little grasshopper learning the ways of the crab I humbly share that I'm working on ripinfo and zenode
banner
-
What’s everyone working on this week (19/2023)?
Turns out I’ve been hacking on https://github.com/rustl3rs/banner; a CI/CD system; for 3 months now. Haven’t been this into an out of work project in decades. I just keep setting really small goals, and if the animals wake me up early, I hack on that goal until it’s ready. Commit; repeat. Very happy with the progress. Some of the current progress has seen the capability to set env vars and use host directories in a task. Next step is to be able to pass the state from one task to another; at which point it will pretty much be able to dogfood itself. 🐶🦴
-
What's everyone working on this week (12/2023)?
I'll be continuing to think and hack on Banner; my thoughts, and now code on how a CICD system should work. It has come a surprisingly long way in such a short time. It's certainly not feature complete, but it has been capable of running a test (unit-test; which could conceivably run unit-tests) for a little while. My current focus is constructing event handlers for simple cases, and allowing them to be executed when a matching event is emitted. Thinking to write the handler as a rhai script, and execute the compiled ast. But rhai isn't particularly async friendly, so may have to shift my thinking. Just started looking at Rune and it looks promising.
-
What's everyone working on this week (6/2023)?
I’m starting to formulate some ideas I’ve had for a long time around CI/CD. No guarantees it’ll go anywhere, but I find it pretty hypocritical that we advocate for testing the skin off our code before we accept it as production ready, but then basically test in production the pipelines that deliver that automation. There just aren’t easy ways to test a pipeline before you merge it or before you make the change in production. Your pretty much forced into a practice we all dislike. Anyway, thoughts here: https://github.com/rustl3rs/banner
What are some alternatives?
local-ip-address - Retrieve system's local IP address and Network Interfaces/Adapters on FreeBSD, Linux, macOS and Windows
rust-s3-async-ffi - Asynchronous streaming of AWS S3 objects in C and C++ powered by rust-s3
ipmap - An interactive map that shows connected IP addresses.
envio - Envio is a command-line tool that simplifies the management of environment variables across multiple profiles. It allows users to easily switch between different configurations and apply them to their current environment [Moved to: https://github.com/envio-cli/envio]
dependency-suggest
mkvdump - MKV and WebM parser CLI tool
fcidr - Fragmented Classless Inter-Domain Routing (FCIDR)
tesseract-wasm - JS/WebAssembly build of the Tesseract OCR engine for use in browsers and Node
ngrok-rust - Embed ngrok secure ingress into your Rust apps with a single line of code.
MyIP - The best IP Toolbox. Easy to check what's your IPs, IP geolocation, check for DNS leaks, examine WebRTC connections, speed test, ping test, MTR test, check website availability and more! || 🇨🇳 可能是最好用的IP工具箱。轻松检查你的 IP,IP 地理位置,检查DNS泄漏,检查 WebRTC 连接,速度测试,ping 测试,MTR测试,检查网站可用性等等。
rustapi - 🚀 RESTful Rust API Template / Boilerplate