Search Results for "example"

...Remember when running nvm install or nvm use, you must have Windows administrative rights (to create symlinks). There are situations where the ability to switch between different versions of Node.js can be very useful. For example, if you want to test a module you're developing with the latest bleeding edge version without uninstalling the stable version of node, this utility can help. Please note that any global npm modules you may have installed are not shared between the various versions of node.js you have installed. Additionally, some npm modules may not be supported in the version of node you're using, so be aware of your environment as you work.

...You can filter and process the incoming log messages using the flow custom resource of the log forwarder to route them to the appropriate output. The outputs are the destinations where you want to send your log messages, for example, Elasticsearch, or an Amazon S3 bucket. You can also define cluster-wide outputs and flows, for example, to use a centralized output that namespaced users can reference but cannot modify.

Fabio is an HTTP and TCP reverse proxy that configures itself with data from Consul. Traditional load balancers and reverse proxies need to be configured with a config file. The configuration contains the hostnames and paths the proxy is forwarding to upstream services. This process can be automated with tools like consul-template that generate config files and trigger a reload. Fabio works differently since it updates its routing table directly from the data stored in Consul as soon as...

...Rather than reimplementing features, it delegates work to existing tools: a shell command generates output, a pager displays it, and “annotators” attach actions to recognized patterns. 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. ...

This is a small and simple application that runs as a Windows service to record metrics several times per second. Metrics can be very different. For example, memory usage by a process or ping to a host. The application does not require a DBMS. The data is stored in an open binary format. Data viewing is possible in the form of graphs of the history of changes and in tables of current values. The configuration setting is done without editing the config files - everything is available directly in the UI application.

...With the default UDP payload size of 1400 bytes, running on Linux kernel 5.1.20, on a tg3 (so no native XDP support) gigabit NIC, sendudp does around 980 Mb/s, so practically line rate. TL;DR: in the same environment, sending a pre-generated DNS query using an ordinary UDP socket yield around 30 MiB/s whereas sending it using the senddnsqueries example program yields around 77 MiB/s. Connecting a PC with Intel Core i7-7700 CPU running Linux kernel 5.0.17 and igb driver to a laptop with Intel Core i7-5600U CPU running Linux kernel 5.0.9 with e1000e with a cat 5E gigabit ethernet cable.

Evio is a Go networking framework built around a high-performance event loop (much like libuv or libevent) but tailored for Go, bypassing the standard net package to make direct epoll/kqueue syscalls on supported OSes for maximum throughput. The library is used where ultra-low latency and high packet rates matter (for example, proxy servers or real-time packet handling). It supports TCP, UDP, and UNIX sockets, multiple address binding, and built-in load balancing across event loops (loops can run single-threaded or multi-threaded). The API is minimalist and exposes event hooks such as Data, Opened, Closed, Tick, allowing developers full control. Because of its architecture, Evio is not a drop-in replacement for standard Go's net/http or net packages; it’s aimed at network-heavy, performance-critical use-cases.

...Using docker-machine commands, you can start, inspect, stop, and restart a managed host, upgrade the Docker client and daemon, and configure a Docker client to talk to your host. Point the Machine CLI at a running, managed host, and you can run docker commands directly on that host. For example, run docker-machine env default to point to a host called default, follow on-screen instructions to complete env setup, and run docker ps, docker run hello-world, and so forth. Machine was the only way to run Docker on Mac or Windows previous to Docker v1.12.