Open Source Elixir Formats and Protocols

Elixir is a dynamic, functional language for building scalable and maintainable applications. Elixir leverages the Erlang VM, known for running low-latency, distributed, and fault-tolerant systems. Elixir is successfully used in web development, embedded software, data ingestion, and multimedia processing, across a wide range of industries. All Elixir code runs inside lightweight threads of execution (called processes) that are isolated and exchange information via messages. Due to their lightweight nature, it is not uncommon to have hundreds of thousands of processes running concurrently in the same machine. Isolation allows processes to be garbage collected independently, reducing system-wide pauses, and using all machine resources as efficiently as possible (vertical scaling). Processes are also able to communicate with other processes running on different machines in the same network.

The flexible HTTP client library for Elixir, with support for middleware and multiple adapters. Tesla is an HTTP client loosely based on Faraday. It embraces the concept of middleware when processing the request/response cycle. Define module with use Tesla and choose from a variety of middleware. Tesla is built around the concept of composable middlewares. This is very similar to how Plug Router works. All HTTP functions, such as Tesla.get/3 and Tesla.post/4, can take a dynamic client as the first argument. This allows using convenient syntax for modifying the behavior in runtime. Tesla supports multiple HTTP adapter that do the actual HTTP request processing. Each piece of the stream will be encoded as JSON and sent as a new line (conforming to JSON stream format). You can set the adapter to Tesla.Mock in tests.

Implementing features such as auto-complete or go-to-definition for a programming language is not trivial. Traditionally, this work had to be repeated for each development tool and it required a mix of expertise in both the targeted programming language and the programming language internally used by the development tool of choice. The Elixir Language Server (ElixirLS) provides a server that runs in the background, providing IDEs, editors, and other tools with information about Elixir Mix projects. It adheres to the LSP, a standard for frontend-independent IDE support. Debugger integration is accomplished through a similar VS Code Debug Protocol. These pages contain all the information needed to configure your favorite text editor or IDE and to work with the ElixirLS. You will also find instructions on how to configure the server to recognize the structure of your projects and to troubleshoot your installation when things do not work as expected.

Floki is a simple HTML parser that enables search for nodes using CSS selectors. Floki needs the :leex module in order to compile. Normally this module is installed with Erlang in a complete installation. By default, Floki uses a patched version of mochiweb_html for parsing fragments due to its ease of installation (it's written in Erlang and has no outside dependencies). fast_html is generally faster, according to the benchmarks conducted by its developers.

A blazing-fast JSON parser and generator in pure Elixir. The parser and generator are at least twice as fast as other Elixir/Erlang libraries (most notably Poison). The performance is comparable to jiffy, which is implemented in C as a NIF. Jason is usually only twice as slow. Both the parser and generator fully conform to RFC 8259 and ECMA 404 standards. The parser is tested using JSONTestSuite. The package can be installed by adding jason to your list of dependencies in mix.exs. Jason follows the JSON spec more strictly, for example, it does not allow unescaped newline characters in JSON strings - e.g. "\"\n\"" will produce a decoding error. No support for decoding into data structures (the as: option). No built-in encoders for MapSet, Range and Stream. No support for encoding arbitrary structs - explicit implementation of the Jason.Encoder protocol is always required. Different pretty-printing customization options (default pretty: true works the same).

Livebook is a web application for writing interactive and collaborative code notebooks. Write notebooks in Livebook then securely deploy and share them with your team and company with Livebook Hub/Enterprise. Code notebooks with Markdown support and Code cells where Elixir code is evaluated on demand. Rich code editor through Monaco: with support for autocompletion, inline documentation, code formatting, etc. Interactive results via Kino: display Vega-Lite charts, tables, maps, and more. Automation: use Smart cells to perform high-level tasks and write notebooks faster than ever. Query databases, plot charts, build maps, and more directly from Livebook's UI. Reproducible: Livebook ensures your code runs in a predictable order, all the way down to package management. It also tracks your notebook state, annotating which parts are stale. Collaboration: multiple users can work on the same notebook at once, no additional setup is required.

Plausible is lightweight and open-source web analytics. No cookies and fully compliant with GDPR, CCPA and PECR. Made and hosted in the EU, powered by European-owned cloud infrastructure. Frustrated with Google Analytics? So are we and that's why we built Plausible Analytics, a simple, lightweight (< 1 KB), open source, and privacy-friendly alternative that doesn't come from the adtech world. Web analytics went from a simple, fun and useful practice for site owners to a data-grabbing machine for surveillance capitalism. Google Analytics is frustrating to use, difficult to understand, slow to load and privacy-invasive too. Plausible Analytics is built for privacy-conscious site owners. You get valuable and actionable stats to help you improve your efforts while your visitors keep having a nice and enjoyable experience. Plausible is simple analytics. It is easy to understand and it cuts through the noise.

Web based metrics, monitoring, and observer. Drop-in monitoring though web interface. Metrics endpoint (/metrics) for system monitoring. (Default: Prometheus) Monitoring automation through JSON API. Node management and discovery behind firewalls and load balancers. Easy to extend. Add custom metrics and pages for your project, just by adding them in the config. Just 3 lines of code to add pages/metrics for your library when users have :wobserver installed. Wobserver does not support being included directly from GitHub. The required assets are not included in the repo in build form and can therefore not be used. It is possible to build locally and use the generated package. (See Build manually for more information.) To view the web interface just enter http://<host>[:<port>]/ in the browser and it should show the :wobserver interface. The default port is 4001, but the port can be changed in the configuration.