Search Results for "hts-engine"

Plug is a specification and set of utilities for building composable modules in Elixir web applications. It defines a standard connection interface, allowing developers to create “plugs” that act as middleware for handling requests and responses. Examples include parsing parameters, managing sessions, logging, or authentication, all of which can be plugged into a pipeline. Plug serves as the foundation for the Phoenix framework, which builds on it to deliver a full-featured web stack. The...

...The approach keeps application logic on the BEAM—supervised, fault-tolerant, and hot-reload-friendly—while rendering an HTML/CSS/JS interface inside the system’s embedded browser engine. It offers conveniences for packaging and distribution on Windows, macOS, and Linux, including app metadata, icons, and startup integration. The library exposes desktop-specific affordances such as system tray menus, window management, and notifications, so applications feel native rather than like generic web wrappers. Because LiveView drives the UI, state lives on the server process, enabling real-time updates without heavy client frameworks. ...

An Elixir implementation of Facebook's GraphQL. This is the core GraphQL query parsing and execution engine whose goal is to be transport, server and datastore agnostic. In order to setup an HTTP server (ie Phoenix) to handle GraphQL queries you will need plug_graphql. Examples for Phoenix can be found at hello_graphql_phoenix, so look here for a starting point for writing your own schemas. Other ways of handling queries will be added in due course.