Search Results for "act"

...If a datastore is missing, the simple SDK allows you to extend Conduit where you need it. Conduit pipelines listen for changes to a database, data warehouse, etc., and allows your data applications to act upon those changes in real-time. Run it in a way that works for you; use it as a standalone service or orchestrate it within your infrastructure.

...CoreDNS can listen for DNS requests coming in over UDP/TCP (go'old DNS), TLS (RFC 7858), also called DoT, DNS over HTTP/2 - DoH - (RFC 8484) and gRPC (not a standard). Serve zone data from a file; both DNSSEC (NSEC only) and DNS are supported (file and auto). Retrieve zone data from primaries, i.e., act as a secondary server (AXFR only) (secondary). Sign zone data on-the-fly (dnssec). Load balancing of responses (loadbalance). Allow for zone transfers, i.e., act as a primary server (file + transfer). Automatically load zone files from disk (auto).

...For example, a mode might run git log --graph and annotate commit hashes so hitting a key can open a diff, check out a branch, or run a follow-up command. Another mode could list files or search results and let you act on selected lines, chaining shell operations together. The design encourages small, composable behaviors that feel like browsing within structured terminal output, while retaining the power of the underlying CLI. It’s a hacker-friendly approach to interactive workflows: leverage the ecosystem of commands you already trust, add a thin layer of annotations, and turn static listings into a navigable, actionable interface.

glider is a forward proxy with multiple protocols support, and also a dns/dhcp server with ipset management features(like dnsmasq). We can set up local listeners as proxy servers, and forward requests to internet via forwarders. Act as both proxy client and proxy server(protocol converter). Flexible proxy & protocol chains. Load balancing with the following scheduling algorithm, rr: round robin, ha: high availability, lha: latency based high availability, dh: destination hashing. Rule & priority based forwarder choosing: Config Examples. DNS forwarding server. ...

...The codebase is roughly 1,000 lines while supporting replication, multiple machines, and multiple drives per machine. It is optimized for comparatively large values between about 1 MB and 1 GB and is intended to scale to very large collections. Standard nginx instances act as volume servers, while filesystem storage holds blobs and LevelDB maintains the index. A simple HTTP API handles reads, writes, deletes, virtual deletes, and key listing, with partial S3 compatibility. The system can rebuild its index and rebalance data when storage volumes are added or removed.