Open Source Elixir Software Development Software - Page 3

A robust, modular and extendable. User management solution. Pow is a complete authentication and user management library built in Elixir that works out-of-the-box for Phoenix and Plug-based applications while being fully customizable. Pow gives you out-of-the-box authentication and user management for your Phoenix or Plug-based app. Functionally built so it's fully customizable. Strong security is a core tenet of Pow's philosophy, which is why Pow by default uses short lived sessions. If your app requires stateless tokens, the authorization layer can be replaced in minutes. Pow has been used in countless production apps and is a "batteries included" library for production. The cache backend store used for session storage can be replaced with any key-value store of your choice. The built-in Mnesia cache module works both for clusters and single-machine persistence, which can auto-connect to the cluster on startup and self-heal after netsplit.

Pusher server implementation is compatible with Pusher client libraries. Open Pusher implementation compatible with Pusher libraries. It's designed to be used as a single registered app with id, secret, and key defined on start. Poxa is a standalone elixir server implementation of the Pusher protocol. Docker images are automatically built by Docker Hub. They are available at Docker Hub. One can generate it using: docker build -t local/poxa. Poxa uses gproc extensively to register websocket connections as channels. So, when a client subscribes for channel 'example-channel', the websocket connection (which is a elixir process) is "tagged" as {pusher, example-channel}. When a pusher event is triggered on the 'example-channel', every websocket matching the tag receives the event.

Scenic is a UI framework built directly on Elixir/Erlang/OTP for creating polished, fault-tolerant client applications. It targets both embedded/IoT and desktop scenarios, leveraging OpenGL for 2D rendering and embracing the OTP ecosystem for concurrency and reliability.

Semaphore is a continuous integration and delivery platform that streamlines building, testing, and deploying software with an emphasis on speed and developer experience. Pipelines are defined declaratively and support parallel jobs, dependency fan-outs, and matrix builds to exercise many environments at once. First-class Docker and Kubernetes workflows, along with layer caching and artifacts, help keep containerized builds fast and reproducible. Secrets management, environment promotion, and approvals enable robust delivery gates from pull request to production. The system integrates with popular VCS providers and chat tools, surfacing real-time status, logs, and insights so teams can diagnose failures quickly. With autoscaling workers and flexible resource types, Semaphore adapts to small projects and large monorepos alike, turning CI/CD into a reliable, low-friction part of everyday development.

Standard Webhooks is a community-driven specification and set of open-source tools designed to make webhooks consistent, secure, and interoperable across providers. The project defines strict guidelines covering aspects like signature formats, headers, timestamps, replay protection, and forward compatibility. It includes reference implementations for signature verification and signing across multiple languages such as Python, JavaScript/TypeScript, Go, Rust, Ruby, PHP, C#, Java, and Elixir, along with additional community SDKs. The initiative is guided by a technical steering committee with members from companies like Zapier, Twilio, Mux, ngrok, Supabase, Svix, and Kong. Standard Webhooks matters because it eliminates the fragmentation of webhook implementations, reducing consumer effort and enabling seamless verification in apps or even directly in API gateways. By unifying best practices, it improves developer experience, enhances security, and enables new ecosystem tools.

Surface is a component-based UI library for Phoenix LiveView that brings a declarative, template-driven approach to building interactive interfaces. Inspired by frameworks like React, it introduces components with typed properties, slots, and macros to simplify complex UIs. Developers can create reusable, encapsulated components that integrate seamlessly with LiveView’s server-rendered real-time model. Surface emphasizes readability, making templates feel closer to HTML while retaining Elixir’s functional power. It also provides form helpers, event bindings, and a growing ecosystem of ready-to-use UI components. By combining the productivity of declarative components with LiveView’s real-time updates, Surface enables rich, interactive apps without requiring a separate frontend framework like React or Vue.

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.

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.

Ueberauth is a two-phase authentication framework that provides a clear API, allowing for many strategies to be created and shared within the community. It is heavily inspired by Omniauth. You could call it a port but it is significantly different in operation, but almost the same concept. Huge hat tip to Intridea. Ueberauth provides only the initial authentication challenge, (initial OAuth flow, collecting the information from a login form, etc). It does not authenticate each request, that's up to your application. You could issue a token or put the result into a session for the needs of your application. Libraries like Guardian can help you with that aspect of authentication. Strategies implement the two phases and then may allow the request to flow through to your downstream plugs. Implementing the request and callback phases is optional depending on the strategies requirements. If a strategy does not redirect, the request will be decorated with Ueberauth information.