Open Source Elixir Frameworks

Ash is a declarative framework for building resource-oriented apps in Elixir. It emphasizes composability, DSL-driven definitions of resources/actions/relationships, and extensibility through plugins for API, database, and UI layers.

Pinchflat is a self-hosted YouTube media manager that automates downloading videos from channels or playlists using yt-dlp. It runs as a lightweight, containerized app and is ideal for archiving or feeding media center setups like Plex, Jellyfin, or Kodi.

Cog brings the power of the command line to the place you collaborate with your team all the time, your chat window. Powerful access control means you can collaborate around even the most sensitive tasks with confidence. A focus on extensibility and adaptability means that you can respond quickly to the unexpected, without your team losing visibility. Use Cog to manage your infrastructure, support peer learning, and conduct collaborative research at the same time, right from chat. Cog is easy to install and simple to operate while remaining powerful enough to handle complex enterprise workflows. Cog brings the power of the command line to the place you collaborate with your team all the time, your chat window. Powerful access control means you can collaborate around even the most sensitive tasks with confidence. A focus on extensibility and adaptability means that you can respond quickly to the unexpected, without your team losing visibility.

Commanded is an Elixir framework for implementing CQRS (Command Query Responsibility Segregation) and Event Sourcing patterns. It provides domain-driven design tools—aggregates, commands, events, and projections—backed by an event store (e.g. PostgreSQL).

The Gun library doesn't have a full 2.0 release yet, so we depend on :grcp_gun 2.0.1 for now. This is the same as :gun 2.0.0-rc.2, but Hex doesn't let us depend on RC versions for releases. Generate Elixir code from the proto file as protobuf-elixir shows(especially the gRPC Support section). Implement the server-side code and remember to return the expected message types. You can start the gRPC server as a supervised process. First, add GRPC.Server.Supervisor to your supervision tree.

Mix tasks to simplify use of Dialyzer in Elixir projects. Elixir 1.6 is required, to support the new pretty printing feature. If your project is not yet on 1.6, continue to specify 0.5 in your mix deps. Warning messages have been greatly improved, but are filtered through the legacy formatter to support your existing ignore files. You can optionally use the new Elixir term format for ignore files. You may want to use the --format short argument in your CI pipelines. There are several formats, also there is a new explain feature - for details see CLI options. If you are planning to use Dialyzer with an application built with the Phoenix Framework, check out the Quickstart wiki. Use dialyxir from the directory of the mix project you want to analyze; a PLT file will be created or updated if required and the project will be automatically compiled.

ExAdmin is an auto-administration package for Elixir and the Phoenix Framework. This version has been updated to support both Ecto 1.1 and Ecto 2.0. ExAdmin is an auto-administration package for Elixir and the Phoenix Framework, a port/inspiration of ActiveAdmin for Ruby on Rails. Checkout the Live Demo. The source code can be found at ExAdmin Demo. Checkout this Additional Live Demo for examples of many-to-many relationships, nested attributes, and authentication. ExAdmin is an add on for an application using the Phoenix Framework to create a CRUD administration tool with little or no code. By running a few mix tasks to define which Ecto Models you want to administer, you will have something that works with no additional code. ExAdmin will use your schema's changesets. By default we call the changeset function on your schema, although you can configure the changeset we use for update and create separately.

Kitto is a framework for interactive dashboards written in Elixir. The source for the demo dashboards can be found at: kittoframework/demo. Jobs are supervised processes running concurrently. Widgets are coded in the popular React library. Uses a modern asset tool-chain, Webpack. Allows streaming SSE to numerous clients concurrently with low memory/CPU footprint. Easy to deploy using the provided Docker images, Heroku (guide) or Distillery (guide). Can serve assets in production. Keeps stats about defined jobs and comes with a dashboard to monitor them (demo). Can apply exponential back-offs to failing jobs. Reloads code upon change in development. Kitto is a framework to help you create dashboards, written in Elixir / React. Widgets live in widgets/ are compiled using Webpack and are automatically loaded in the dashboards. Assets are rebuilt upon a change in development but have to be compiled for production.

Nebulex provides support for transparently adding caching into an existing Elixir application. Similar to Ecto, the caching abstraction allows consistent use of various caching solutions with minimal impact on the code. Nebulex cache abstraction shields developers from directly dealing with the underlying caching implementations, such as Redis, Memcached, or even other Elixir cache implementations like Cachex. Additionally, it provides totally out-of-box features such as cache usage patterns, declarative annotation-based caching, and distributed cache topologies, among others. For intensive workloads, you may want to use :shards as the backend for the local adapter and having partitioned tables. In such a case, you have to add :shards to the dependency list. For enabling the usage of declarative annotation-based caching via decorators, you have to add :decorator to the dependency list.

Sobelow is a security-focused static analysis tool for the Phoenix framework. For security researchers, it is a useful tool for getting a quick view of points-of-interest. For project maintainers, it can be used to prevent the introduction of a number of common vulnerabilities. Potential vulnerabilities are flagged in different colors according to confidence in their insecurity. High confidence is red, medium confidence is yellow, and low confidence is green. A finding is typically marked "low confidence" if it looks like a function could be used insecurely, but it cannot reliably be determined if the function accepts user-supplied input. That is to say, if a finding is marked green, it may be critically insecure, but it will require greater manual validation. This project is in constant development, and additional vulnerabilities will be flagged as time goes on. If you encounter a bug, or would like to request additional features or security checks, please open an issue!