Open Source Elixir Software for Mac - Page 5

This is community style guide for the Elixir programming language. Please feel free to make pull requests and suggestions, and be a part of Elixir's vibrant community. If you're looking for other projects to contribute to please see the Hex package manager site. Elixir v1.6 introduced a Code Formatter and Mix format task. The formatter should be preferred for all new projects and source code. The rules in this section are applied automatically by the code formatter, but are provided here as examples of the preferred style. Use Unix-style line endings (*BSD/Solaris/Linux/OSX users are covered by default, Windows users have to be extra careful). Use spaces around operators, after commas, colons and semicolons. Do not put spaces around matched pairs like brackets, parentheses, etc. Whitespace might be (mostly) irrelevant to the Elixir runtime, but its proper use is the key to writing easily readable code.

Timex is a rich, comprehensive Date/Time library for Elixir projects, with full timezone support via the :tzdata package. If you need to manipulate dates, times, datetimes, timestamps, etc., then Timex is for you! It is very easy to use Timex types in place of default Erlang types, as well as Ecto types via the timex_ecto package. If you are coming from an earlier version of Timex, it is recommended that you evaluate whether or not the functionality provided by the standard library Calendar API is sufficient for your needs, as you may be able to avoid the dependency entirely. Timex now delegates to the standard library where possible, and provides backward compatibility to Elixir 1.8 for APIs which are used. This is to avoid duplicating effort, and to ease the maintenance of this library in the future. Take a look at the documentation to see what APIs are available and how to use them.

Wallaby helps you test your web applications by simulating realistic user interactions. By default, it runs each test case concurrently and manages browsers for you. Here's an example test for a simple Todo application. Because Wallaby manages multiple browsers for you, it's possible to test several users interacting with a page simultaneously. Read on to see what else Wallaby can do or check out the Official Documentation. Wallaby also requires bash to be installed. Generally, bash is widely available, but it does not come pre-installed on Alpine Linux. If you're testing a Phoenix application with Ecto and a database that supports sandbox mode, you can enable concurrent testing by adding the Phoenix.Ecto.SQL.Sandbox plug to your Endpoint. It's important that this is at the top of endpoint.ex before any other plugs.

Witchcraft brings algebraic and category-theoretic abstractions—like semigroups, monoids, functors, applicatives, and monads—to Elixir in a pragmatic, protocol-driven way. It introduces a set of typeclass-style protocols and laws so data types can declare the operations they support and have those behaviors verified. The library encourages composability and pure transformations, letting you build pipelines where effects are modeled explicitly rather than hidden in ad-hoc helpers. Because the implementation leans on Elixir protocols, you can extend Witchcraft’s abstractions to your own structs without invasive inheritance hierarchies. It promotes predictable, law-abiding behavior through property-based testing helpers and a focus on algebraic reasoning. Teams reach for Witchcraft when they want to structure business logic with reusable, mathematically grounded patterns that remain idiomatic to the BEAM.

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.

libcluster provides automatic cluster formation and node discovery for Erlang/Elixir applications, removing the manual steps typically required to connect distributed nodes. It ships with multiple pluggable strategies—such as DNS polling, Kubernetes integration, EC2 metadata/tag discovery, UDP gossip, and EPMD helpers—so you can adapt clustering to your runtime environment. The library supervises a topology process that continually discovers peers and joins or prunes nodes as they become available or disappear. Its design embraces OTP principles: strategies implement a behavior, can be composed, and run under supervision for resilience. libcluster also emits events on nodeup/nodedown, allowing applications to react (for example, rebalance work or update registries) when membership changes. Because it relies on the BEAM’s native distribution, it integrates cleanly with Phoenix PubSub, Horde, Oban, or any other distributed Elixir tooling.

Observer CLI is a library to be dropped into any beam nodes, to be used to assist DevOps people to diagnose problems in production nodes. Provide a high-performance tool usable both in development and production settings. Focus on important and detailed information about real-time running systems. Keep minimal consumption. Increments are values that are mostly useful when compared to a previous one to have an idea of what they're doing because otherwise, they'd never stop increasing: bytes in and out of the node, number of garbage collector runs, words of memory that were garbage collected, and the global reductions count for the node. Total scheduler utilization will equal 1.0 when all schedulers have been active all the time between the two refresh intervals. The result being that there is a decent chunk of CPU usage that would be mostly free for scheduling actual Erlang work (assuming the schedulers are busy waiting more than trying to select tasks to run).