utils
Budibase backend core libraries used in server and worker
Devpunks Backend Core
Auri spectrum's backend core
Juicyllama Backend Core
Meshwatch backend core services.
Database-Agnostic Backend Core for Rebase
Backend core
Postgres Backend Core files
Aqago Backend Core common code
Local e-commerce backend core
Backend core library for App Catalog
Micro-backend core plugin
Backend core library for Env Hopper
XBG Backend Core - Base classes, middleware, config, and code generator
vibeOS backend core: API server, MCP server, web dashboard, and API client
Backend Core - Core backend utilities and services
Micro-backend core GraphQL plugin
commentami-backend-core
CLI to generate the mm-backend-core backend template
Budibase backend core libraries used in server and worker
Common functionalities for the dp-dynamic-plugin-backend-core
backend core kit library
Maybe Framework Backend Core
An opinionated framework to work with Elasticsearch.
Pure parser backend selection primitives.
Cmor Core Module.
Ecm::CoreInfo::Backend Module.
Libsaml makes the creation of SAML 2.0 messages easy. The object structure is modeled after the SAML Core 2.0 specification from OASIS. Supported bindings are HTTP-Post, HTTP-Redirect, HTTP-Artifact and SOAP. Features include XML signing, XML verification and a pluggable backend for providers (FileStore backend included).
R18n backend for Rails I18n and R18n filters and loader to support Rails translation format. R18n has nice Ruby-style syntax, filters, flexible locales, custom loaders, translation support for any classes, time and number localization, several user language support, agnostic core package with out-of-box support for Rails, Sinatra and desktop applications.
Background per-core CPU monitoring for Ruby/Rails applications. Reads /proc/stat on Linux (Heroku) or top on macOS. Writes a rotating 1 MB JSON-lines log per dyno. On single dynos the file backend is used; on multi-dyno Heroku deployments the Redis backend aggregates all dynos into a single CpuInspectCore.status view. Ships with a Rails Railtie for zero-config boot and a CLI executable for bash usage.
treestore stores two different types of data: 1) values, which are stored according to their SHA-1 hashcode 2) trees, which are sets of values and/or other trees, stored via a SHA-1 hashcode In addition, there are references that allow you to 'bookmark' a SHA-1 hashcode for easier lookup. If you think of the core git, but on any key-value backend store (like the included Redis one), you've got the right idea.
Spur allows developers to setup a highly configurable ecommerce backend. The aim of this gem is to provide some of the core features that you might find inside of Solidus or the legacy project, Spree. If you are in need of a simple payment backend to sell some products (either physical, downloadable, or subscribable), Spur may be the best choice for you. Spur works best as an _integration_ with a SaaS product and for smaller stores that don't need the weight of Solidus. Checkout the guides for more details on getting setup. Spur will allow you to be able to: * Setup a very robust subscription platform. * Sell downloadable content. * Ship products to and from locations. * Accept payments without worrying about money management. * Provide order management for users.
pikuri-vectordb gives a pikuri-core agent a +vectordb_search+ tool over a local document corpus — agentic search, the agent decides when to retrieve. Ships a swappable backend (a pure-Ruby +Backend::InMemory+ for teaching and a thin +Backend::Chroma+ HTTP client for persistence), a chunker, an embedder wrapper over +RubyLLM.embed+, and an optional +Reranker::LlamaServer+ that speaks +/v1/rerank+ against a cross-encoder model. Text extraction goes through +Pikuri::FileType.read_as_text+ in pikuri-core, which handles plain text / Markdown / PDF; HTML extraction is a deferred follow-up. Hosts wire the feature via +c.add_extension Pikuri::VectorDb::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-skills+. The bundled +Pikuri::VectorDb::LIBRARIAN+ persona is the privilege-separated sub-agent counterpart for hosts that want recall to flow through a child rather than the parent's context. Three model endpoints in the full setup — chat (via ruby_llm), an embedder (via +RubyLLM.embed+), and an optional reranker (HTTP +/v1/rerank+). A single +llama-server+ in router mode serves all three by default, loading each cached GGUF on demand; see the gem's README for details.
Mokio is a Content Management System that allows creation of sophisticated websites. It consists maily of administration panel for your desired website. It provides the following types of content: Article (piece of text with pictures, lists, links, etc.), Picture Gallery (easily managed article with a number of photos - thumbs and edition provided), Movie Gallery (article with links to Dailymotion, Vimeo and Youtube movies - thumbs and edition provided), Contact Page with Google map and contact form. Apart from content it is possible to manage menu structure of your website for each language and defined position (part of the screen). If this is not enough for what you need, you can also include pieces of HTML code that should be shared by some (or all) subpages - called HTML Blocks. You can define on which part of the page, these blocks should be displayed. Mokio provides also administration panel for javascripts, languages and backend users. Beside Mokio itself, there are various gems dedicated for Mokio, that extends its core functionality. Visit: http://www.mokio.org Folow us on facebook: https://www.facebook.com/mokioCMS
== Ruby Data Objects If you're building something in Ruby that needs access to a database, you may opt to use an ORM like ActiveRecord, DataMapper or Sequel. But if your needs don't fit well with an ORM—maybe you're even writing an ORM—then you'll need some other way of talking to your database. RDO provides a common interface to a number of RDBMS backends, using a clean Ruby syntax, while supporting all the functionality you'd expect from a robust database connection library: * Consistent API to connect to various DBMS's * Type casting to Ruby types * Time zone handling (via the DBMS, not via some crazy time logic in Ruby) * Native bind values parameterization of queries, where supported by the DBMS * Retrieve query info from executed commands (e.g. affected rows) * Access RETURNING values just like any read query * Native prepared statements where supported, emulated where not * Results given using simple core Ruby data types == RDBMS Support Support for each RDBMS is provided in separate gems, so as to minimize the installation requirements and to facilitate the maintenace of each driver. Many gems are maintained by separate users who work more closely with those RDBMS's. Due to the nature of this gem, most of the nitty-gritty code is actually written in C. See the official README for full details.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.