url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://rubygems.org/gems/asciidoctor/versions/2.0.26?locale=nl | asciidoctor | RubyGems.org | De gem host voor de community ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Gems Zoeken… Releases Blog Gems Handleidingen Inloggen Registreren asciidoctor 2.0.26 A fast, open source text processor and publishing toolchain for converting AsciiDoc content to HTML 5, DocBook 5, and other formats. Gemfile: = Installeer: = Versies: 2.0.26 October 24, 2025 (278 KB) 2.0.25 October 16, 2025 (278 KB) 2.0.24 October 13, 2025 (278 KB) 2.0.23 May 17, 2024 (277 KB) 2.0.22 March 08, 2024 (276 KB) Toon alle versies (78 totaal) Development afhankelijkheden (9): concurrent-ruby ~> 1.1.0 cucumber ~> 3.1.0 erubi ~> 1.10.0 haml ~> 6.3.0 minitest ~> 5.22.0 nokogiri ~> 1.13.0 rake ~> 12.3.0 slim ~> 4.1.0 tilt ~> 2.0.0 Show all transitive dependencies Eigenaren: Pushed by: Authors: Dan Allen, Sarah White, Ryan Waldron, Jason Porter, Nick Hengeveld, Jeremy McAnally SHA 256 checksum: = ← Previous version Total downloads 52.497.923 Voor deze versie 363.442 Versie vrijgegeven: October 24, 2025 1:49am Licentie: MIT Required Ruby Version: >= 0 Links: Startpagina Changelog Broncode Mailing-list Bug-tracker Download Funding Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Statistieken Bijdragen Over ons Hulp API Policies Support Us Security RubyGems.org is de gem hosting service van de Ruby community. Publiceer en installeer je gems direct. Gebruik de API om meer informatie over beschikbare gems te vinden. Word een deelnemer en verbeter de site met jouw aanpassingen. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Ontwerp DockYard Hosting AWS DNS DNSimple Monitoring Datadog Gems served by Fastly Monitoring Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://bundler.io/v4.0/man/bundle-pristine.1.html | Bundler: bundle pristine Bundler Docs Team Blog Repository bundle pristine bundle-pristine - Restores installed gems to their pristine condition bundle pristine Description pristine restores the installed gems in the bundle to their pristine condition using the local gem cache from RubyGems. For git gems, a forced checkout will be performed. For further explanation, bundle pristine ignores unpacked files on disk. In other words, this command utilizes the local .gem cache or the gem's git repository as if one were installing from scratch. Note: the Bundler gem cannot be restored to its original state with pristine . One also cannot use bundle pristine on gems with a 'path' option in the Gemfile, because bundler has no original copy it can restore from. When is it practical to use bundle pristine ? It comes in handy when a developer is debugging a gem. bundle pristine is a great way to get rid of experimental changes to a gem that one may not want. Why use bundle pristine over gem pristine --all ? Both commands are very similar. For context: bundle pristine , without arguments, cleans all gems from the lockfile. Meanwhile, gem pristine --all cleans all installed gems for that Ruby version. If a developer forgets which gems in their project they might have been debugging, the Rubygems gem pristine [GEMNAME] command may be inconvenient. One can avoid waiting for gem pristine --all , and instead run bundle pristine . Choose version v4.0 v2.7 v2.6 v2.5 v2.4 v2.3 v2.2 v2.1 v2.0 v1.17 v1.16 v1.15 General Release notes Primary Commands bundle install bundle update bundle cache bundle exec bundle config bundle help Utilities bundle bundle add bundle binstubs bundle check bundle clean bundle console bundle doctor bundle env bundle fund bundle gem bundle info bundle init bundle issue bundle licenses bundle list bundle lock bundle open bundle outdated bundle platform bundle plugin bundle pristine bundle remove bundle show bundle version gemfile Edit this document on GitHub if you caught an error or noticed something was missing. Docs Team Blog About Repository | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/read-document-tree/ | Read the Document Tree | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Read the Document Tree 3.0 3.0 2.5 Edit this Page Read the Document Tree Instead of converting an AsciiDoc document, you may want to parse the document to read information it contains or navigate the document’s structure. AsciidoctorJ lets you do this! AsciidoctorJ provides a model of the abstract syntax tree of the document. These objects are directly linked to the internal representation. To load a document, use the load or loadFile methods. import org.asciidoctor.ast.Document; //... Document document = asciidoctor.load(DOCUMENT, Options.builder().build()); (1) assertThat(document.doctitle(), is("Document Title")); (2) 1 Document from a String is loaded into Document object. 2 Title of the document is retrieved. But also all blocks that conforms the document can be retrieved. Currently there are support for three kinds of blocks. Blocks itself, Section for sections of the document and StructuralNode which is the base type where all kind of blocks (including those not mapped as Java class) are mapped. import org.asciidoctor.ast.Document; import org.asciidoctor.ast.Section; //... Document document = asciidoctor.load(DOCUMENT, Options.builder().build()); (1) Section section = (Section) document.getBlocks().get(1); (2) assertThat(section.index(), is(0)); (3) assertThat(section.sectname(), is("sect1")); assertThat(section.special(), is(false)); 1 Document from a String is loaded into Document object. 2 All blocks are get and because in this example the first block is a Section block, we cast it directly. 3 Concrete methods for sections can be called. Blocks can also be retrieved from query using findBy method. Document document = asciidoctor.load(DOCUMENT, Options.builder().build()); Map<Object, Object> selector = new HashMap<>(); (1) selector.put("context", ":image"); (2) List<StructuralNode> findBy = document.findBy(selector); assertThat(findBy, hasSize(2)); (3) 1 Queries are defined in a map estructure. 2 In this example all blocks with context as image is returned. Notice that the colon ( : ) must be added in the value part. 3 Document used as example contains two images. Logs Handling API Write a Custom Converter Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://rubygems.org/gems/minitest-parallel_fork | minitest-parallel_fork | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up minitest-parallel_fork 2.1.1 minitest-parallel_fork adds fork-based parallelization to Minitest. Each test/spec suite is run in one of the forks, allowing this to work correctly when using before_all/after_all/around_all hooks provided by minitest-hooks. Using separate processes via fork can significantly improve spec performance when using MRI, and can work in cases where Minitest's default thread-based parallelism do not work, such as when specs modify the constant namespace. Gemfile: = install: = Versions: 2.1.1 December 18, 2025 (9.5 KB) 2.1.0 July 02, 2025 (9 KB) 2.0.0 November 08, 2023 (8.5 KB) 1.3.1 September 25, 2023 (7.5 KB) 1.3.0 July 05, 2022 (7.5 KB) Show all versions (12 total) Runtime Dependencies (1): minitest >= 5.15.0 Development Dependencies (2): minitest-global_expectations >= 0 minitest-hooks >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 322,423 For this version 4,803 Version Released: December 18, 2025 8:15pm License: MIT Required Ruby Version: >= 2.2 Links: Homepage Changelog Source Code Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/ast-introduction/ | Understanding the AST Classes | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Understanding the AST Classes 3.0 3.0 2.5 Edit this Page Understanding the AST Classes To write extensions or converters for AsciidoctorJ understanding the AST ( abstract syntax tree ) classes is key. The AST classes are the intermediate representation of the document that Asciidoctor creates before rendering to the target format. The following example document demonstrates how an AST will look like to give you an idea how the document and the AST are connected. Example document for the AST = Test document Foo Bar <foo@bar.com> This document demonstrates the AST of an Asciidoctor document == The first section A section has some nice paragraphs and maybe lists: === A subsection - One - Two - Three Or even tables |=== | Key | Value |=== and sources as well [source,ruby] ---- puts 'Hello, World!' ---- The following image shows the AST and some selected members of the node objects. The indentation of a line visualizes the nesting of the nodes like a tree. AST for the example document Document context: document Block context: preamble Block context: paragraph This document demon... Section context: section level: 1 Block context: paragraph A section has some ... Section context: section level: 2 List context: ulist ListItem context: list_item One ListItem context: list_item Two ListItem context: list_item Three Block context: paragraph Or even tables Table context: table style: table Block context: paragraph and sources as well Block context: listing style: source puts 'Hello, World!' The AST is built from the following types: org.asciidoctor.ast.Document This is always the root of the document. It owns the blocks and sections that make up the document and holds the document attributes. org.asciidoctor.ast.Section This class models sections in the document. The member level indicates the nesting level of this section, that is if level is 1 the section is a section, with level 2 it is a subsection, etc. org.asciidoctor.ast.Block Blocks are content in a section, like paragraphs, source listings, images, etc. The concrete form of the block is available in the field context . Among the possible values are: paragraph listing literal open example pass org.asciidoctor.ast.List The list node is the container for ordered and unordered lists. The type of list is available in the field context , ulist for unordered lists and olist for ordered lists. org.asciidoctor.ast.ListItem A list item represents a single item of a list. org.asciidoctor.ast.DescriptionList The description list node is the container for description lists. The context of the node is dlist . org.asciidoctor.ast.DescriptionListEntry A list entry represents a single item of a description list. It has multiple terms that are again instances of org.asciidoctor.ast.ListItem and a description that is also an instance of org.asciidoctor.ast.ListItem . org.asciidoctor.ast.Table This represents a table and is probably the most complex node type. It owns a list of columns and lists of header, body and footer rows. org.asciidoctor.ast.Column A column defines the style for the column of a table, the width and alignments. org.asciidoctor.ast.Row A row in a table is only a simple owner of a list of table cells. org.asciidoctor.ast.Cell A cell in a table holds the cell content and formatting attributes like colspan, rowspan and alignment as appropriate. A special case are cells that have the asciidoctor style. These do not contain simple text content, but have another full Document in their member innerDocument . org.asciidoctor.ast.PhraseNode This type is a special case. It does not appear in the AST itself as Asciidoctor does not really parse into the block itself. Phrase nodes are usually created by inline macro extensions that process macros like issue:1234[] and create links from them. Nodes are in general only created from within extensions. Therefore the abstract base class of all extensions, org.asciidoctor.extension.Processor , has factory methods for every node type. Now that you have learned about the AST structure you can go into the details of writing the extensions. AsciidoctorJ Conversion Process Overview Block Macro Processor Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://rubygems.org/gems/minitest-hooks | minitest-hooks | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up minitest-hooks 1.5.3 minitest-hooks adds around and before_all/after_all/around_all hooks for Minitest. This allows you do things like run each suite of specs inside a database transaction, running each spec inside its own savepoint inside that transaction, which can significantly speed up testing for specs that share expensive database setup code. Gemfile: = install: = Versions: 1.5.3 December 18, 2025 (8.5 KB) 1.5.2 August 14, 2024 (8.5 KB) 1.5.1 July 27, 2023 (8.5 KB) 1.5.0 May 21, 2018 (11 KB) 1.4.2 September 12, 2017 (10.5 KB) Show all versions (12 total) Runtime Dependencies (1): minitest > 5.3 Development Dependencies (4): minitest-global_expectations >= 0 rake >= 0 sequel > 4 sqlite3 >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 12,494,404 For this version 13,526 Version Released: December 18, 2025 6:06pm License: MIT Required Ruby Version: >= 1.8 Links: Homepage Changelog Source Code Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://stdapi.ai/use_cases_continue/ | IDE integration (Continue.dev & others) - stdapi.ai Skip to content stdapi.ai IDE integration (Continue.dev & others) Initializing search stdapi-ai/stdapi.ai Home Documentation API Reference stdapi.ai stdapi-ai/stdapi.ai Home Documentation Documentation API API Overview OpenAI Compatible Operations Operations Getting started Configuration Licensing Logging & Monitoring Use cases Use cases Overview OpenWebUI integration N8N integration IDE integration (Continue.dev & others) IDE integration (Continue.dev & others) Table of contents Why IDE Integration + stdapi.ai? About Continue.dev Prerequisites 🚀 Quick Start Configuration Step 1: Open Continue Configuration Step 2: Configure Chat Model Step 3: Configure Autocomplete (Optional but Recommended) Step 4: Add Multiple Models (Optional) Step 5: Configure Embeddings for Codebase Context (Optional) 🎯 What You Can Do Now 💬 AI Chat for Code ✨ Tab Autocomplete 📝 Code Actions 🔍 Codebase Understanding 📊 Model Recommendations by Task 💡 Pro Tips & Best Practices 🔧 Complete Configuration Example 🚀 Next Steps & Resources Getting Started Learn More Community & Support ⚠️ Important Considerations LibreChat integration LangChain / LlamaIndex integration Note-taking apps (Obsidian & Notion) Chat bots (Slack, Discord & Teams) Autonomous agents (AutoGPT & more) Roadmap & Changelog API Reference Table of contents Why IDE Integration + stdapi.ai? About Continue.dev Prerequisites 🚀 Quick Start Configuration Step 1: Open Continue Configuration Step 2: Configure Chat Model Step 3: Configure Autocomplete (Optional but Recommended) Step 4: Add Multiple Models (Optional) Step 5: Configure Embeddings for Codebase Context (Optional) 🎯 What You Can Do Now 💬 AI Chat for Code ✨ Tab Autocomplete 📝 Code Actions 🔍 Codebase Understanding 📊 Model Recommendations by Task 💡 Pro Tips & Best Practices 🔧 Complete Configuration Example 🚀 Next Steps & Resources Getting Started Learn More Community & Support ⚠️ Important Considerations Home Documentation Use cases IDE Integration — Continue.dev & Others ¶ Get AI-powered assistance in your IDE with Amazon Bedrock models through stdapi.ai. Code completion, generation, and chat directly in VS Code, JetBrains IDEs, and more. Why IDE Integration + stdapi.ai? ¶ For Developers Many IDE extensions and AI-powered IDEs are designed for the OpenAI API, making stdapi.ai a drop-in replacement to access coding models like Claude Sonnet and Amazon Nova. This guide uses Continue.dev as the primary example, but the same configuration approach works for many other tools. Compatible IDE Tools & Extensions Popular IDE Extensions: Continue.dev ( GitHub ) — Open-source, 15,000+ stars, VS Code & JetBrains Cline — Autonomous coding agent for VS Code Twinny — Privacy-focused AI assistant for VS Code JetBrains AI Assistant — Official JetBrains AI plugin CodeGPT ( Docs ) — Multi-provider AI assistant for various IDEs AI-First IDEs: Cursor — AI-first fork of VS Code with OpenAI integration Windsurf — AI-native IDE by Codeium Zed — High-performance editor with AI features All these tools support custom OpenAI-compatible API endpoints, making them compatible with stdapi.ai using the same configuration pattern demonstrated in this guide. About Continue.dev ¶ 🔗 Links: Website | GitHub | Documentation | Discord Continue.dev is an open-source AI code assistant chosen for this guide because of its: Wide adoption - 15,000+ GitHub stars, active community Multi-IDE support - Works in VS Code and all JetBrains IDEs Open source - Transparent, extensible, and privacy-focused Simple configuration - JSON-based config for stdapi.ai integration Key Benefits: Code models - Claude Sonnet and other Bedrock models for coding, debugging, and technical tasks Privacy & control - Your code stays in your AWS environment Cost efficient - AWS pricing instead of OpenAI rates IDE integration - Works in VS Code and JetBrains IDEs Simple setup - Configuration change, no extension modifications needed Enterprise ready - For teams with security and compliance requirements Work in Progress This integration guide is actively being developed and refined. While the configuration examples are based on documented APIs and best practices, they are pending practical validation. Complete end-to-end deployment examples will be added once testing is finalized. Prerequisites ¶ What You'll Need Before you begin, make sure you have: ✓ VS Code or a JetBrains IDE (IntelliJ, PyCharm, WebStorm, etc.) ✓ Continue.dev extension installed ( VS Code / JetBrains ) ✓ Your stdapi.ai server URL (e.g., https://api.example.com ) ✓ An API key (if authentication is enabled) ✓ AWS Bedrock access configured with coding-capable models 🚀 Quick Start Configuration ¶ Step 1: Open Continue Configuration ¶ Continue.dev stores its configuration in a JSON file that you can edit directly from your IDE. Opening the Config File In VS Code: Open Command Palette: Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac) Type: Continue: Open config.json Press Enter In JetBrains IDEs: Open Settings/Preferences: Ctrl+Alt+S (Windows/Linux) or Cmd+, (Mac) Navigate to: Tools → Continue Click Edit config.json Alternatively, find the config file at: - VS Code: ~/.continue/config.json - JetBrains: ~/.continue/config.json Step 2: Configure Chat Model ¶ Update the chat model configuration to use stdapi.ai with your preferred Bedrock model. config.json - Chat Configuration { "models" : [ { "title" : "Claude 4.5 Sonnet" , "provider" : "openai" , "model" : "anthropic.claude-sonnet-4-5-20250929-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" } ] } Available Models: All Amazon Bedrock chat models work with Continue.dev. Popular choices for coding include Claude Sonnet (best for complex coding tasks), Claude Haiku (fast, efficient for quick queries), Amazon Nova Pro (strong reasoning, long context), and Amazon Nova Lite (balanced performance and cost). Model Selection for Coding Claude Sonnet is highly recommended for coding tasks. It excels at: - Understanding complex codebases - Generating production-quality code - Debugging and refactoring - Explaining technical concepts - Multi-file code changes Step 3: Configure Autocomplete (Optional but Recommended) ¶ For real-time code completions as you type, configure a fast model optimized for autocomplete. config.json - Autocomplete Configuration { "models" : [ { "title" : "Claude 4.5 Sonnet" , "provider" : "openai" , "model" : "anthropic.claude-sonnet-4-5-20250929-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" } ], "tabAutocompleteModel" : { "title" : "Nova Lite Autocomplete" , "provider" : "openai" , "model" : "amazon.nova-lite-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" } } Autocomplete Model Choice Use faster, smaller models for autocomplete to get instant suggestions: Amazon Nova Lite — amazon.nova-lite-v1:0 (balanced, good quality) Amazon Nova Micro — amazon.nova-micro-v1:0 (fastest, most cost-effective) Claude Haiku — Fast Claude model for quick completions Step 4: Add Multiple Models (Optional) ¶ You can configure multiple models and switch between them based on your task. config.json - Multiple Models { "models" : [ { "title" : "Claude 4.5 Sonnet (Complex Tasks)" , "provider" : "openai" , "model" : "anthropic.claude-sonnet-4-5-20250929-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" }, { "title" : "Claude 3.5 Haiku (Quick Questions)" , "provider" : "openai" , "model" : "anthropic.claude-3-5-haiku-20241022-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" }, { "title" : "Nova Pro (Long Context)" , "provider" : "openai" , "model" : "amazon.nova-pro-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" } ], "tabAutocompleteModel" : { "title" : "Nova Lite Autocomplete" , "provider" : "openai" , "model" : "amazon.nova-lite-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" } } Model Switching Continue.dev lets you switch models during a conversation using the dropdown in the chat interface. Set up multiple models with descriptive titles to quickly choose the right tool for each task. Step 5: Configure Embeddings for Codebase Context (Optional) ¶ Enable Continue to use embeddings for better codebase understanding and retrieval. config.json - Embeddings Configuration { "models" : [ { "title" : "Claude 4.5 Sonnet" , "provider" : "openai" , "model" : "anthropic.claude-sonnet-4-5-20250929-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" } ], "embeddingsProvider" : { "provider" : "openai" , "model" : "amazon.titan-embed-text-v2:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" } } Available Embedding Models: Amazon Titan Embed Text v2 — amazon.titan-embed-text-v2:0 (recommended, 8192 dimensions) Amazon Titan Embed Text v1 — amazon.titan-embed-text-v1 (legacy, 1536 dimensions) Cohere Embed — If enabled in your AWS region Why Use Embeddings? Embeddings enable Continue to: - Search your entire codebase semantically - Find relevant code automatically based on your question - Provide better context-aware suggestions - Understand relationships between files and functions 🎯 What You Can Do Now ¶ Once configured, Continue.dev with stdapi.ai unlocks powerful coding capabilities: 💬 AI Chat for Code ¶ Ask Questions: "How does the authentication system work?" Generate Code: "Write a function to validate email addresses" Refactor: "Refactor this function to use async/await" Debug: "Why is this throwing a NullPointerException?" Explain: "Explain what this regex pattern does" Document: "Add comprehensive JSDoc comments to this function" ✨ Tab Autocomplete ¶ Real-time Suggestions: Get inline code completions as you type Context Aware: Completions understand your codebase style and patterns Multi-line: Generate entire functions or code blocks Smart: Learns from your project structure and imports 📝 Code Actions ¶ Highlight & Edit: Select code and ask AI to modify it Multi-file Changes: Make coordinated changes across multiple files Test Generation: Generate unit tests for selected functions Documentation: Auto-generate docstrings and comments 🔍 Codebase Understanding ¶ Semantic Search: "@codebase how do we handle user authentication?" Architecture Questions: "What's the overall structure of the backend?" Dependency Tracking: "Where is this function used?" API Discovery: "Show me examples of using the database client" 📊 Model Recommendations by Task ¶ Choose the right model for each coding task to optimize performance and cost. These are suggestions —experiment to find what works best for your workflow. Task Recommended Model Why Complex Refactoring anthropic.claude-sonnet-4-5-20250929-v1:0 Superior code understanding and generation Quick Questions anthropic.claude-3-5-haiku-20241022-v1:0 Fast responses for simple queries Long Context amazon.nova-pro-v1:0 Large context window for big files Code Review anthropic.claude-sonnet-4-5-20250929-v1:0 Detailed analysis and suggestions Autocomplete amazon.nova-lite-v1:0 Fast, cost-effective inline suggestions Documentation anthropic.claude-sonnet-4-5-20250929-v1:0 Clear, comprehensive explanations Bug Hunting anthropic.claude-sonnet-4-5-20250929-v1:0 Deep debugging and root cause analysis 💡 Pro Tips & Best Practices ¶ Context is Key Tag relevant files: Use @filename to include specific files in your context Use @codebase: Ask questions about your entire project with @codebase Highlight code: Select the exact code you're asking about for precise answers Optimize for Speed Fast models for quick tasks: Use Haiku or Nova Lite for simple questions Premium models for complex work: Use Claude Sonnet for refactoring and architecture Autocomplete with lightweight models: Keep completions fast with Nova Lite/Micro Better Prompts = Better Code Be specific: "Add error handling for network timeouts" vs "improve this" Provide context: Mention frameworks, languages, patterns you're using Iterate: Start broad, then refine with follow-up questions Team Configuration Share config: Commit a template config.json (without API keys) to your repo Environment variables: Use ${env:STDAPI_KEY} to reference environment variables Consistent models: Standardize on models across your team for predictable results 🔧 Complete Configuration Example ¶ Full config.json Template { "models" : [ { "title" : "Claude 4.5 Sonnet (Primary)" , "provider" : "openai" , "model" : "anthropic.claude-sonnet-4-5-20250929-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" , "contextLength" : 200000 }, { "title" : "Claude 3.5 Haiku (Fast)" , "provider" : "openai" , "model" : "anthropic.claude-3-5-haiku-20241022-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" , "contextLength" : 200000 }, { "title" : "Nova Pro (Long Context)" , "provider" : "openai" , "model" : "amazon.nova-pro-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" , "contextLength" : 300000 } ], "tabAutocompleteModel" : { "title" : "Nova Lite Autocomplete" , "provider" : "openai" , "model" : "amazon.nova-lite-v1:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" }, "embeddingsProvider" : { "provider" : "openai" , "model" : "amazon.titan-embed-text-v2:0" , "apiKey" : "YOUR_STDAPI_KEY" , "apiBase" : "https://YOUR_SERVER_URL/v1" }, "allowAnonymousTelemetry" : false } 🚀 Next Steps & Resources ¶ Getting Started ¶ Test Your Setup: Ask Continue a simple question like "What does this file do?" Try Autocomplete: Start typing a function and wait for suggestions Explore Features: Use @codebase , @file , and /edit commands Customize: Adjust models based on your workflow and budget Share: Help your team set up Continue with stdapi.ai Learn More ¶ Additional Resources Continue.dev Documentation — Official Continue.dev guides API Overview — Complete list of available Bedrock models Chat Completions API — Detailed chat API documentation Configuration Guide — Advanced stdapi.ai configuration options Community & Support ¶ Need Help? 💬 Join the Continue.dev Discord for tips and troubleshooting 📖 Review Amazon Bedrock documentation for model-specific details 🐛 Report issues on the GitHub repository 🔧 Consult AWS Support for infrastructure and model access questions ⚠️ Important Considerations ¶ Model Availability Regional Differences: Not all Amazon Bedrock models are available in every AWS region. Verify model availability in your configured region before setting up Continue.dev. Check availability: See the API Overview for supported models by region. Performance Tips Context Length: Larger context windows allow more code to be analyzed but increase latency and cost. Adjust based on your needs. Autocomplete Frequency: Faster models provide better autocomplete experience. Nova Lite/Micro are recommended over premium models. Caching: Continue.dev caches embeddings locally. First-time codebase indexing may take a few minutes. Cost Optimization Right-size models: Use Haiku or Nova Lite for simple questions to reduce costs Monitor token usage: Large file selections consume more tokens—be selective Autocomplete wisely: Autocomplete can generate many requests; use efficient models Share knowledge: Document good prompts and patterns for your team to reduce trial-and-error Back to top Previous N8N integration Next LibreChat integration JGoutin-dev SARL - 994495422 R.C.S. Aix-en-Provence, France | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/roda-route_list/actions/workflows/ci.yml | CI · Workflow runs · jeremyevans/roda-route_list · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / roda-route_list Public Notifications You must be signed in to change notification settings Fork 3 Star 27 Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights Actions: jeremyevans/roda-route_list Actions --> All workflows Workflows CI CI Show more workflows... Management Caches CI CI Actions Loading... Loading Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> will be ignored since log searching is not yet available Show workflow options Create status badge Create status badge Loading Uh oh! There was an error while loading. Please reload this page . ci.yml --> will be ignored since log searching is not yet available 7 workflow runs 7 workflow runs Event Filter by Event Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching events. Status Filter by Status Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching statuses. Branch Filter by Branch Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching branches. Actor Filter by Actor Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching users. Add Ruby 4.0 to CI CI #22: Commit 41fb337 pushed by jeremyevans 12m 13s master master 12m 13s View workflow file Use SimpleCov.add_filter block instead of string CI #21: Commit f9e0182 pushed by jeremyevans 57s master master 57s View workflow file Add JRuby 10.0 to CI CI #20: Commit ea59d62 pushed by jeremyevans 4m 14s master master 4m 14s View workflow file Switch rdoc task to normal rake task, avoid rdoc/task require CI #19: Commit 76d3d5b pushed by jeremyevans 1m 0s master master 1m 0s View workflow file Work with ubuntu-latest using 24.04 by default in CI CI #18: Commit 5289a79 pushed by jeremyevans 1m 1s master master 1m 1s View workflow file Add Ruby 3.4 to CI CI #17: Commit 27d751a pushed by jeremyevans 1m 33s master master 1m 33s View workflow file Use -W:strict_unused_block when running tests on Ruby 3.4+ CI #16: Commit 8d90fb9 pushed by jeremyevans 1m 1s master master 1m 1s View workflow file You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://rubygems.org/gems/hanna | hanna | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up hanna 1.5.1 RDoc generator designed with simplicity, beauty and ease of browsing in mind Gemfile: = install: = Versions: 1.5.1 May 12, 2025 (16 KB) 1.5.0 August 10, 2023 (16 KB) 0.1.12 October 16, 2009 (44.5 KB) Runtime Dependencies (1): rdoc >= 4, != 6.13.0 Development Dependencies (2): minitest-global_expectations >= 0 minitest-hooks >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans, Erik Hollensbe, James Tucker, Mislav Marohnic SHA 256 checksum: = ← Previous version Total downloads 37,888 For this version 5,787 Version Released: May 12, 2025 8:10pm License: MIT Required Ruby Version: >= 2.2 Links: Homepage Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/register-extensions/ | Register Extensions | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Register Extensions 3.0 3.0 2.5 Edit this Page Register Extensions Now that we have our extensions ready, we only need to register them. There are 3 ways to do so, and all of them can combined freely to suit your needs. Two are manual and one automatic. Also, at any moment, you can clear the configuration using unregisterAllExtensions() : Asciidoctor asciidoctor = Asciidoctor.Factory.create(); asciidoctor.unregisterAllExtensions(); Docinfo Processor Manually Registering Extensions with javaExtensionRegistry Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/register-extensions-bulk/ | Bulk Extension Registration (Extension Groups) | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Register Extensions Bulk Extension Registration ( Extension Groups ) 3.0 3.0 2.5 Edit this Page Bulk Extension Registration ( Extension Groups ) As an alternative method to register extensions in bulk or groups. Using the ExtensionGroup API it is possible to define a set of extension grouped under a name to be registered later. final String groupName = "my-extensions"; ExtensionGroup extensionGroup = asciidoctor.createGroup(groupName) .blockMacro(GistBlockMacroProcessor.class) .includeProcessor(LsIncludeProcessor.class) .postprocessor(ByePostprocessor.class); (1) ... extensionGroup.register(); (2) 1 Multiple extensions can be added together using the fluent API. 2 Complete registration, otherwise extensions won’t be enabled. If you don’t need or want to set a specific name, you can just use asciidoctor.createGroup() , and a randomly generated name will be assigned automatically. Calling createGroup(String) + register() more than once will override any pre-existing group with the same name. Effectively REMOVING (and disabling) the previously set extensions. This does not apply to createGroup() , different calls will create different extension groups with random names. Manually Registering Extensions with javaExtensionRegistry Automatically Loading Extensions Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://rubygems.org/gems/asciidoctor/versions/2.0.26?locale=zh-TW | asciidoctor | RubyGems.org | Ruby 社群 Gem 套件管理平台 ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> 搜尋 Gems… Releases 部落格 Gems 教學文件 登入 註冊 asciidoctor 2.0.26 A fast, open source text processor and publishing toolchain for converting AsciiDoc content to HTML 5, DocBook 5, and other formats. Gemfile: = 安裝: = 版本列表: 2.0.26 October 24, 2025 (278.0 KB) 2.0.25 October 16, 2025 (278.0 KB) 2.0.24 October 13, 2025 (277.5 KB) 2.0.23 May 17, 2024 (276.5 KB) 2.0.22 March 08, 2024 (276.0 KB) 顯示所有版本（共 78） Development 相依性套件 (9): concurrent-ruby ~> 1.1.0 cucumber ~> 3.1.0 erubi ~> 1.10.0 haml ~> 6.3.0 minitest ~> 5.22.0 nokogiri ~> 1.13.0 rake ~> 12.3.0 slim ~> 4.1.0 tilt ~> 2.0.0 Show all transitive dependencies 擁有者: 推送者: 作者: Dan Allen, Sarah White, Ryan Waldron, Jason Porter, Nick Hengeveld, Jeremy McAnally SHA 256 總和檢查碼: = ← 上一版本 總下載次數 52,497,923 這個版本 363,442 版本发布: October 24, 2025 1:49am 授權: MIT Ruby 版本需求: >= 0 相關連結: 首頁 更新日誌 原始碼 郵件群組 Bug 追蹤 下載 Funding Review changes 徽章 訂閱 RSS 檢舉濫用 反向依賴 狀態 上線時間 原始碼 資料 統計 貢獻 關於 說明 API Policies Support Us 安全 RubyGems.org 是 Ruby 社群的 Gem 套件管理服務，讓您能立即地 發佈 及 安裝 您的 Gem 套件，並且利用 API 查詢及操作 可用 Gem 的詳細資訊。 現在就 成為貢獻者 ，貢獻一己之力來改善本站。 RubyGems.org 透過與廣大的 Ruby 社群合作而誕生。 Fastly 提供頻寬和 CDN 支援， Ruby Central 支付設備費用，並為進行中的開發和營運工作提供資金。 進一步了解我們的贊助商和它們是如何合作的 。 Operated by Ruby Central 設計 DockYard 托管 AWS 解析 DNSimple 監控 Datadog 服務 Fastly 監控 Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/capybara-restore_state | GitHub - jeremyevans/capybara-restore_state: Restore capybara state after block execution Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / capybara-restore_state Public Notifications You must be signed in to change notification settings Fork 0 Star 0 Restore capybara state after block execution 0 stars 0 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights jeremyevans/capybara-restore_state master Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 23 Commits .github/ workflows .github/ workflows lib/ capybara lib/ capybara spec spec .ci.gemfile .ci.gemfile .gitignore .gitignore CHANGELOG CHANGELOG MIT-LICENSE MIT-LICENSE README.rdoc README.rdoc Rakefile Rakefile capybara-restore_state.gemspec capybara-restore_state.gemspec View all files Repository files navigation README License capybara-restore_state capybara-restore_state offers the ability to execute a block where the initial capybara state on entering the block is returned after the block is executed. This makes it possible to test things like clicking on the same button twice. This only works for the rack-test driver, other drivers can use the back buttons provided by the browser. Installation gem install capybara - restore_state Source Code Source code is available on GitHub at github.com/jeremyevans/capybara-restore_state Examples require 'capybara' require 'capybara/restore_state' describe Capybara :: RestoreState do include Rack :: Test :: Methods include Capybara :: DSL include Capybara :: RestoreState def app MyRackApp end it "should allow restoring of state" do # Assume Submit button takes you /a visit '/' page . current_path # => '/' restore_state do page . current_path # => '/' click_button 'Submit' page . current_path # => '/a' end page . current_path # => '/' click_button 'Submit' page . current_path # => '/a' end end License MIT Author Jeremy Evans <code@jeremyevans.net> About Restore capybara state after block execution Resources Readme Uh oh! There was an error while loading. Please reload this page . Activity Stars 0 stars Watchers 1 watching Forks 0 forks Report repository Releases 2 tags Packages 0 No packages published Uh oh! There was an error while loading. Please reload this page . Languages Ruby 100.0% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/enum_csv | GitHub - jeremyevans/enum_csv: Create CSV from Enumerables Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / enum_csv Public Notifications You must be signed in to change notification settings Fork 0 Star 9 Create CSV from Enumerables License MIT license 9 stars 0 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights jeremyevans/enum_csv master Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 43 Commits .github/ workflows .github/ workflows lib lib spec spec .ci.gemfile .ci.gemfile .gitignore .gitignore CHANGELOG CHANGELOG MIT-LICENSE MIT-LICENSE README.rdoc README.rdoc Rakefile Rakefile enum_csv.gemspec enum_csv.gemspec View all files Repository files navigation README MIT license EnumCSV EnumCSV exposes a single method, csv, for easily creating CSV output/files from enumerable objects. It is a simple wrapper class for ruby’s csv library. Installation gem install enum_csv Source Code Source code is available on GitHub at github.com/jeremyevans/enum_csv Examples The default behavior just expects an enumerable of arrays (such as an array of arrays), and returns a string containing the CSV output: EnumCSV . csv ([[ 1 , 2 ]]) => "1,2\n" You can use the :headers option to set custom headers: EnumCSV . csv ([[ 1 , 2 ], [ 3 , "4,5" ]], :headers => [ 'A' , 'B' ]) => "A,B\n1,2\n3,\"4,5\"\n" EnumCSV . csv ([[ 1 , 2 ], [ 3 , "4,5" ]], :headers => 'A,B' ) => "A,B\n1,2\n3,\"4,5\"\n" The :file option can be used to output to a file: EnumCSV . csv ([[ 1 , 2 ]], :file => 'foo.csv' ) => nil # output written to foo.csv If a block is passed to the method, all items in the enumerable are yielded to the block, and the block should return an array with the data to use in the CSV output: EnumCSV . csv ([{ :a => 1 , :b => 2 }, { :a => 3 , :b => 4 }]){ | l | [ l [ :b ], l [ :a ] + 10 ]} => "2,11\n4,13\n" License MIT Author Jeremy Evans <code@jeremyevans.net> About Create CSV from Enumerables Resources Readme License MIT license Uh oh! There was an error while loading. Please reload this page . Activity Stars 9 stars Watchers 1 watching Forks 0 forks Report repository Releases 4 tags Packages 0 No packages published Uh oh! There was an error while loading. Please reload this page . Languages Ruby 100.0% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/2.5/ | AsciidoctorJ: Java Bindings for Asciidoctor | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 2.5 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ AsciidoctorJ: Java Bindings for Asciidoctor 2.5 3.0 2.5 Edit this Page AsciidoctorJ: Java Bindings for Asciidoctor Asciidoctor is an implementation of the AsciiDoc format in Ruby. Thanks to the JRuby , an implementation of the Ruby runtime in Java, Asciidoctor can also be executed on a JVM. AsciidoctorJ bundles all gems that are required for executing Asciidoctor and wraps it into a Java API so that Asciidoctor can be used in Java like any other Java library. Additionally, there is a distribution that you can simply download, unzip and execute without worrying about installing the right Ruby runtime, installing gems etc. Distribution Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://wiki.freenode.net | freenode wiki Main Page From freenode wiki Jump to: navigation , search Contents 1 ¸¸♬·¯·♪·¯·♫¸¸ Welcome To freenode ¸¸♫·¯·♪¸♩·¯·♬¸¸ 2 Getting Started 2.1 clients 3 Resources and Tools 3.1 Guides 3.2 Network News 4 Help and Support 4.1 FAQ 5 Community Corner 5.1 freenode User Corner 5.2 Community Spotlight 6 Gaming Corner 7 Finding staff 8 Contact Information ¸¸♬·¯·♪·¯·♫¸¸ Welcome To freenode ¸¸♫·¯·♪¸♩·¯·♬¸¸ Maintainers: f Welcome to the freenode Wiki! This collaborative platform is dedicated to providing a wealth of information on various topics related to freenode, an IRC (Internet Relay Chat) network supporting discussions on open source and free software projects. Here, users like you can find valuable resources, guides, and documentation to enhance your experience on freenode. Thank you for visiting, and we hope you find the information here useful! Getting Started Freenode is an IRC (Internet Relay Chat) network that serves as a hub for open source and free software communities. To get started on Freenode, you'll need an IRC client, such as HexChat, mIRC, or IRCCloud. Once you have your client set up, connect to the Freenode network and choose a nickname (usually with the command /nick yournickname). Join channels related to your interests or projects by using the command /join #channelname. Remember to follow the network's guidelines and etiquette to have a positive experience interacting with others. clients Webchat Hexchat mIRC weechat konversation AdIRC Resources and Tools Guides Cloaks Nick Registration Channel Registration Channel Takeover Policy Network News Freenode has launched an exciting new feature: Freenode Radio! Tune in to #freenode-radio to enjoy a variety of music and shows while chatting with the Freenode community. Whether you're looking for background music while you work or want to discover new tunes, Freenode Radio has something for everyone. Join the channel and start listening today! Help and Support This is the section you will find the FAQs or troubleshooting guides or any helpful information. FAQ 1. What is Freenode? Freenode is an IRC (Internet Relay Chat) network used for discussing peer-directed projects and collaboration between individuals and communities interested in free and open-source software (FOSS) and related topics. 2. How do I connect to Freenode? You can connect to Freenode using an IRC client. Set your client to connect to chat.freenode.net on port 6667 (or port 6697 for SSL/TLS connections). You can also use Freenode's webchat service available at https://webchat.freenode.net/ . 3. Do I need to register my nickname on Freenode? While registration is not mandatory, it is recommended. Registering your nickname helps protect it from being used by others and allows you to access additional services such as joining channels that require registered nicknames. 4. How do I register my nickname on Freenode? To register your nickname, use the command /msg NickServ REGISTER password email, replacing password with your desired password and email with your email address. Follow the instructions sent to your email to complete the registration. 5. What are channels on Freenode? Channels on Freenode are chat rooms dedicated to specific topics or communities. Users can join channels to participate in discussions and interact with others who share similar interests. 6. How do I join a channel on Freenode? To join a channel, use the command /join #channel-name, replacing #channel-name with the name of the channel you want to join. For example, /join #freenode. 7. Are there any guidelines or rules for using Freenode? Yes, Freenode has a set of guidelines called the Freenode Charter, which outlines the expectations for behavior and interactions on the network. It is important to familiarize yourself with these guidelines to ensure a positive experience for yourself and others. 8. How can I get help or support on Freenode? If you need help or have questions about using Freenode, you can join the #freenode channel and ask for assistance. There are also several other channels dedicated to providing support for specific topics or services on Freenode. Community Corner The FreeNode Community Guidelines are designed to ensure a respectful and welcoming environment for all users. freenode User Corner Freenode channels Community Spotlight This section will be dedicated to a community that is active on freenode. Could be changed weekly or monthly. Gaming Corner Gaming Corner on Freenode is a vibrant community hub where gamers gather to explore new and exciting games. Our corner features a modern take on classics like Duckhunt , offering an enhanced and immersive experience that keeps players engaged and entertained. Additionally, we host exciting trivia games that test your knowledge and offer a fun way to compete with fellow gamers. If you have a game channel that you'd like to see featured on our corner, please reach out to either F or End3r to get your channel added to our wiki. Join us at Gaming Corner on Freenode and dive into a world of endless gaming possibilities! Finding staff Staff Contact Information - Name: Foxy - Email: foxy@freenode.net Notice: We reserve the right to deny access to the network at any time and for any reason. Whenever possible, a reason will be provided to you, however, we are under no obligation to do so. Retrieved from ‘ https://wiki.freenode.net/index.php?title=Main_Page&oldid=406 ’ Navigation menu Personal tools Log in Namespaces Main page Discussion Variants Views Read View source View history More Search Navigation Main page Network Info Network Information Community Guidelines Staff IRCd Info (inspircd) Channel Modes Basic User Commands Basic User Modes Services Anope MemoServ BotServ HostServ ChanServ NickServ HostServ Guides Cloaks Nick Registration Channel Registration Help about MediaWiki Tools What links here Related changes Special pages Printable version Permanent link Page information This page was last modified on 19 March 2025, at 16:23. Privacy policy About freenode wiki Disclaimers | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctor/latest/migrate/docbook-xml/ | Migrate from DocBook XML to Asciidoctor | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets Asciidoctor Features What’s New in 2.0 Install and Update Supported Platforms Install Using Ruby Packaging Install Using Linux Packaging Install on macOS Install on Windows Convert Your First File Converters Available Converters Custom Converter Converter Templates Convertible Contexts Generate HTML Stylesheets Default Stylesheet Stylesheet Modes Apply a Custom Stylesheet Embed a CodeRay or Pygments Stylesheet Manage Images Use Local Font Awesome Add a Favicon Verbatim Block Line Wrapping Skip Front Matter Generate DocBook Generate Manual Pages Process AsciiDoc Using the CLI asciidoctor(1) Specify an Output File Process Multiple Source Files Pipe Content Through the CLI Set Safe Mode CLI Options Process AsciiDoc Using the API Load and Convert Files Load and Convert Strings Generate an HTML TOC Set Safe Mode Enable the Sourcemap Catalog Assets Find Blocks API Options Safe Modes Safe Mode Specific Content AsciiDoc Tooling Syntax Highlighting Highlight.js Rouge CodeRay Pygments Custom Adapter STEM Processing MathJax and HTML Asciidoctor Mathematical STEM Support in the DocBook Toolchain AsciiMath Gem Extensions Register Extensions Log from an Extension Preprocessor Tree Processor Postprocessor Docinfo Processor Block Processor Compound Block Processor Block Macro Processor Inline Macro Processor Include Processor Localization Support Errors and Warnings Migration Guides Upgrade from Asciidoctor 1.5.x to 2.0 Migrate from AsciiDoc.py Migrate from DocBook XML Migrate from Markdown Migrate from Confluence XHTML Migrate from MS Word Asciidoctor 2.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community Asciidoctor Migration Guides Migrate from DocBook XML Edit this Page Migrate from DocBook XML to Asciidoctor A task Asciidoctor excels at is converting AsciiDoc source into valid and well-formed DocBook XML content. But what if you’re in the position where you need to go the other way, to migrate your legacy DocBook XML content to AsciiDoc? The prescription (℞) you need to get rid of your DocBook pains could be DocBookRx . DocBookRx DocBookRx is an early version of a DocBook to AsciiDoc converter written in Ruby. This converter is far from perfect at the moment, but it improves with each document it converts. The plan is to evolve it into a robust library for performing this conversion in a reliable way. You can read more about this initiative in the README . The best thing about this tool is all the active users who are putting it through its paces. The more advanced the DocBook XML this tool tackles, and the more feedback we receive, the better the tool will become. Use it today to escape from XML hell! From doxygen Doxygen can generate documentation in various output formats. One of those formats is (DocBook) XML. That means there’s a pathway from doxygen to AsciiDoc by way of DocBookRx. To enable this feature (off by default), set the GENERATE_DOCBOOK tag to YES in the Doxygen configuration file. When enabled, Doxygen will generate XML files that capture the structure of the code including all documentation. To begin the migration, first run the doxygen command to generate the DocBook XML output. Then run DocBookRx on the XML files to generate AsciiDoc files. You can now use Asciidoctor to convert the AsciiDoc files to a consumable output format such as HTML. Note that some post processing of the generated AsciiDoc may be necessary. Migrate from AsciiDoc.py Migrate from Markdown Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/include-processor/ | Include Processor | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Write an Extension Include Processor 3.0 3.0 2.5 Edit this Page Include Processor Asciidoctor supports including other documents via the include directive. With it, you can simply write include::other.adoc[] to include the contents of the file other.adoc . Include Processors allow to intercept this mechanism and for instance include the content over the network. For example, similar to the *unix ls command, an Include Processor could resolve the include directive include::ls[] , and insert the contents of the current directory in the document. Our example will replace the include directive include::ls[] with the directory contents, adding one line for every file found. ls-include.adoc ---- include::ls[] ---- The processor could look like this: LsIncludeProcessor.java import org.asciidoctor.ast.Document; import org.asciidoctor.extension.IncludeProcessor; import org.asciidoctor.extension.PreprocessorReader; import java.io.File; import java.util.Map; public class LsIncludeProcessor extends IncludeProcessor { (1) @Override public boolean handles(String target) { (2) return "ls".equals(target); } @Override public void process(Document document, (3) PreprocessorReader reader, String target, Map<String, Object> attributes) { StringBuilder sb = new StringBuilder(); for (File f: new File(".").listFiles()) { sb.append(f.getName()).append("\n"); } reader.pushInclude( (4) sb.toString(), target, new File(".").getAbsolutePath(), 1, attributes); } } 1 Every Include Processor must extend the class org.asciidoctor.extension.IncludeProcessor . 2 Asciidoctor calls the method handles() with the target for every include directive it finds. The method must return true if it feels responsible for this directive. In our case it returns true if the target is ls . 3 The implementation of the method process() lists the directory contents of the current directory and creates a string with one line per file. 4 Finally the call to the method push_include inserts the contents. The second and third parameters contain the 'file name' of the include content. In our example this will be basically the name ls and the path of the current directory. The parameter 1 is the line number of the first line of the included content. This makes the most sense when partial content is included. Block Processor Preprocessor Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/rodauth | GitHub - jeremyevans/rodauth: Ruby's Most Advanced Authentication Framework Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / rodauth Public Notifications You must be signed in to change notification settings Fork 105 Star 1.9k Ruby's Most Advanced Authentication Framework rodauth.jeremyevans.net License MIT license 1.9k stars 105 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights jeremyevans/rodauth master Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 1,399 Commits .github/ workflows .github/ workflows demo-site demo-site dict dict doc doc javascript javascript lib lib spec spec templates templates www www .ci.gemfile .ci.gemfile .gitignore .gitignore CHANGELOG CHANGELOG CONTRIBUTING CONTRIBUTING MIT-LICENSE MIT-LICENSE README.rdoc README.rdoc Rakefile Rakefile SECURITY.md SECURITY.md rodauth.gemspec rodauth.gemspec View all files Repository files navigation README Contributing MIT license Security Rodauth Rodauth is Ruby’s most advanced authentication framework, designed to work in any rack application. It’s built using Roda and Sequel, but it can be used with other web frameworks, database libraries, and databases. When used with PostgreSQL, MySQL, and Microsoft SQL Server in the default configuration, it offers additional security for password hashes by protecting access via database functions. Rodauth supports multiple multifactor authentication methods, multiple passwordless authentication methods, and offers both an HTML and JSON API for all supported features. Design Goals Security: Ship in a maximum security by default configuration Simplicity: Allow for easy configuration via a DSL Flexibility: Allow for easy overriding of any part of the framework Feature Documentation The options/methods for the supported features are listed on a separate page per feature. If these links are not active, please view the appropriate file in the doc directory. Base (this feature is autoloaded) Login Password Requirements Base (this feature is autoloaded by features that set logins/passwords) Email Base (this feature is autoloaded by features that send email) Two Factor Base (this feature is autoloaded by 2 factor authentication features) Account Expiration Active Sessions Audit Logging Argon2 Change Login Change Password Change Password Notify Close Account Confirm Password Create Account Disallow Common Passwords Disallow Password Reuse Email Authentication HTTP Basic Auth Internal Request JSON JWT CORS JWT Refresh JWT Lockout Login Logout OTP OTP Lockout Email OTP Modify Email OTP Unlock Password Complexity Password Expiration Password Grace Period Password Pepper Path Class Methods Recovery Codes Remember Reset Password Reset Password Notify Session Expiration Single Session SMS Codes Update Password Hash Verify Account Verify Account Grace Period Verify Login Change WebAuthn WebAuthn Autofill WebAuthn Login WebAuthn Modify Email WebAuthn Verify Account Resources Website rodauth.jeremyevans.net Demo Site rodauth-demo.jeremyevans.net Source github.com/jeremyevans/rodauth Bugs github.com/jeremyevans/rodauth/issues Discussion Forum (GitHub Discussions) github.com/jeremyevans/rodauth/discussions Alternate Discussion Forum (Google Groups) groups.google.com/forum/#!forum/rodauth Dependencies There are some dependencies that Rodauth uses depending on the features in use. These are development dependencies instead of runtime dependencies in the gem as it is possible to run without them: tilt Used by all features unless in JSON API only mode or using :render=>false plugin option. rack_csrf Used for CSRF support if the csrf: :rack_csrf plugin option is given (the default is to use Roda’s route_csrf plugin, as that allows for more secure request-specific tokens). bcrypt Used by default for password hashing, can be skipped if password_match? is overridden for custom authentication. argon2 Used by the argon2 feature as alternative to bcrypt for password hashing. mail Used by default for mailing in the reset_password, verify_account, verify_login_change, change_password_notify, lockout, and email_auth features. rotp Used by the otp feature rqrcode Used by the otp feature jwt Used by the jwt feature webauthn Used by the webauthn feature You can use gem install --development rodauth to install the development dependencies in order to run tests. Security Password Hash Access Via Database Functions By default on PostgreSQL, MySQL, and Microsoft SQL Server, Rodauth uses database functions to access password hashes, with the user running the application unable to get direct access to password hashes. This reduces the risk of an attacker being able to access password hashes and use them to attack other sites. The rest of this section describes this feature in more detail, but note that Rodauth does not require this feature be used and works correctly without it. There may be cases where you cannot use this feature, such as when using a different database or when you do not have full control over the database you are using. Passwords are hashed using bcrypt by default, and the password hashes are kept in a separate table from the accounts table, with a foreign key referencing the accounts table. Two database functions are added, one to retrieve the salt for a password, and the other to check if a given password hash matches the password hash for the user. Two database accounts are used. The first is the account that the application uses, which is referred to as the app account. The app account does not have access to read the password hashes. The other account handles password hashes and is referred to as the ph account. The ph account sets up the database functions that can retrieve the salt for a given account’s password, and check if a password hash matches for a given account. The ph account sets these functions up so that the app account can execute the functions using the ph account’s permissions. This allows the app account to check passwords without having access to read password hashes. While the app account is not be able to read password hashes, it is still be able to insert password hashes, update passwords hashes, and delete password hashes, so the additional security is not that painful. By disallowing the app account access to the password hashes, it is much more difficult for an attacker to access the password hashes, even if they are able to exploit an SQL injection or remote code execution vulnerability in the application. The reason for extra security in regards to password hashes stems from the fact that people tend to choose poor passwords and reuse passwords, so a compromise of one database containing password hashes can result in account access on other sites, making password hash storage of critical importance even if the other data stored is not that important. If you are storing other sensitive information in your database, you should consider using a similar approach in other areas (or all areas) of your application. Tokens Account verification, password resets, email auth, verify login change, remember, and lockout tokens all use a similar approach. They all provide a token, in the format “account-id_long-random-string”. By including the id of the account in the token, an attacker can only attempt to bruteforce the token for a single account, instead of being able to bruteforce tokens for all accounts at once (which would be possible if the token was just a random string). Additionally, all comparisons of tokens use a timing-safe comparison function to reduce the risk of timing attacks. HMAC By default, for backwards compatibility, Rodauth does not use HMACs, but you are strongly encouraged to use the hmac_secret configuration method to set an HMAC secret. Setting an HMAC secret will enable HMACs for additional security, as described below. email_base feature All features that send email use this feature. Setting hmac_secret will make the tokens sent via email use an HMAC, while the raw token stored in the database will not use an HMAC. This will make it so if the tokens in the database are leaked (e.g. via an SQL injection vulnerability), they will not be usable without also having access to the hmac_secret . Without an HMAC, the raw token is sent in the email, and if the tokens in the database are leaked, they will be usable. To allow for an graceful transition, you can set allow_raw_email_token? to true temporarily. This will allow the raw tokens in previous sent emails to still work. This should only be set temporarily as it removes the security that hmac_secret adds. Most features that send email have tokens that expire by default in 1 day. The exception is the verify_account feature, which has tokens that do not expire. For the verify_account feature, if the user requested an email before hmac_secret was set, after allow_raw_email_token is no longer set, they will need to request the verification email be resent, in which case they will receive an email with a token that uses an HMAC. remember feature Similar to the email_base feature, this uses HMACs for remember tokens, while storing the raw tokens in the database. This makes it so if the raw tokens in the database are leaked, the remember tokens are not usable without knowledge of the hmac_secret . The raw_remember_token_deadline configuration method can be set to allow a previously set raw remember token to be used if the deadline for the remember token is before the given time. This allows for graceful transition to using HMACs for remember tokens. By default, the deadline is 14 days after the token is created, so this should be set to 14 days after the time you enable the HMAC for the remember feature if you are using the defaults. otp feature Setting hmac_secret will provide HMACed OTP keys to users, and would store the raw OTP keys in the database. This will make so if the raw OTP keys in the database are leaked, they will not be usable for two factor authentication without knowledge of the hmac_secret . Unfortunately, there can be no simple graceful transition for existing users. When introducing hmac_secret to a Rodauth installation that already uses the otp feature, you will have to either revoke and replace all OTP keys, set otp_keys_use_hmac? to false and continue to use raw OTP keys, or override otp_keys_use_hmac? to return false if the user was issued an OTP key before hmac_secret was added to the configuration, and true otherwise. otp_keys_use_hmac? defaults to true if hmac_secret is set, and false otherwise. If otp_keys_use_hmac? is true, Rodauth will also ensure during OTP setup that the OTP key was generated by the server. If otp_keys_use_hmac? is false, any OTP key in a valid format will be accepted during setup. If otp_keys_use_hmac? is true, the jwt and otp features are in use and you are setting up OTP via JSON requests, you need to first send a POST request to the OTP setup route. This will return an error with the otp_secret and otp_raw_secret parameters in the JSON. These parameters should be submitted in the POST request to setup OTP, along with a valid OTP auth code for the otp_secret . webauthn feature Setting hmac_secret is required to use the webauthn feature, as it is used for checking that the provided authentication challenges have not been modified. active_sessions feature Setting hmac_secret is required to use the active_sessions feature, as the database stores an HMAC of the active session ID. single_session feature Setting hmac_secret will ensure the single session secret set in the session will be an HMACed. This does not affect security, as the session itself should at the least by protected by an HMAC (if not encrypted). This is only done for consistency, so that the raw tokens in the database are distinct from the tokens provided to the users. To allow for a graceful transition, allow_raw_single_session_key? can be set to true. PostgreSQL Database Setup In order to get full advantages of Rodauth’s security design on PostgreSQL, multiple database accounts are involved: database superuser account (usually postgres) app account (same name as application) ph account (application name with _password appended) The database superuser account is used to load extensions related to the database. The application should never be run using the database superuser account. Create database accounts If you are currently running your application using the database superuser account, the first thing you need to do is to create the app database account. It’s often best to name this account the same as the database name. You should also create the ph database account which will handle access to the password hashes. Example for PostgreSQL: createuser -U postgres ${DATABASE_NAME} createuser -U postgres ${DATABASE_NAME}_password Note that if the database superuser account owns all of the items in the database, you’ll need to change the ownership to the database account you just created. See gist.github.com/jeremyevans/8483320 for a way to do that. Create database In general, the app account is the owner of the database, since it will own most of the tables: createdb -U postgres -O ${DATABASE_NAME} ${DATABASE_NAME} Note that this is not the most secure way to develop applications. For maximum security, you would want to use a separate database account as the owner of the tables, have the app account not be the owner of any tables, and specifically grant the app account only the minimum access it needs to work correctly. Doing that is beyond the scope of Rodauth, though. Load extensions If you want to use the login features for Rodauth, you need to load the citext extension if you want to support case insensitive logins. Example: psql -U postgres -c "CREATE EXTENSION citext" ${DATABASE_NAME} Note that on Heroku, this extension can be loaded using a standard database account. If you want logins to be case sensitive (generally considered a bad idea), you don’t need to use the PostgreSQL citext extension. Just remember to modify the migration below to use String instead of citext for the email in that case. Grant schema rights (PostgreSQL 15+) PostgreSQL 15 changed default database security so that only the database owner has writable access to the public schema. Rodauth expects the ph account to have writable access to the public schema when setting things up. Temporarily grant that access (it will be revoked after the migration has run) psql -U postgres -c "GRANT CREATE ON SCHEMA public TO ${DATABASE_NAME}_password" ${DATABASE_NAME} Using non-default schema PostgreSQL sets up new tables in the public schema by default. If you would like to use separate schemas per user, you can do: psql -U postgres -c "DROP SCHEMA public;" ${DATABASE_NAME} psql -U postgres -c "CREATE SCHEMA AUTHORIZATION ${DATABASE_NAME};" ${DATABASE_NAME} psql -U postgres -c "CREATE SCHEMA AUTHORIZATION ${DATABASE_NAME}_password;" ${DATABASE_NAME} psql -U postgres -c "GRANT USAGE ON SCHEMA ${DATABASE_NAME} TO ${DATABASE_NAME}_password;" ${DATABASE_NAME} psql -U postgres -c "GRANT USAGE ON SCHEMA ${DATABASE_NAME}_password TO ${DATABASE_NAME};" ${DATABASE_NAME} You’ll need to modify the code to load the extension to specify the schema: psql -U postgres -c "CREATE EXTENSION citext SCHEMA ${DATABASE_NAME}" ${DATABASE_NAME} When running the migration for the ph user you’ll need to modify a couple things for the schema changes: create_table(:account_password_hashes) do foreign_key :id, Sequel[:${DATABASE_NAME}][:accounts], primary_key: true, type: :Bignum String :password_hash, null: false end Rodauth.create_database_authentication_functions(self, table_name: Sequel[:${DATABASE_NAME}_password][:account_password_hashes]) # if using the disallow_password_reuse feature: create_table(:account_previous_password_hashes) do primary_key :id, type: :Bignum foreign_key :account_id, Sequel[:${DATABASE_NAME}][:accounts], type: :Bignum String :password_hash, null: false end Rodauth.create_database_previous_password_check_functions(self, table_name: Sequel[:${DATABASE_NAME}_password][:account_previous_password_hashes]) You’ll also need to use the following Rodauth configuration methods so that the app account calls functions in a separate schema: function_name do |name| "${DATABASE_NAME}_password.#{name}" end password_hash_table Sequel[:${DATABASE_NAME}_password][:account_password_hashes] # if using the disallow_password_reuse feature: previous_password_hash_table Sequel[:${DATABASE_NAME}_password][:account_previous_password_hashes] MySQL Database Setup MySQL does not have the concept of object owners, and MySQL’s GRANT/REVOKE support is much more limited than PostgreSQL’s. When using MySQL, it is recommended to GRANT the ph account ALL privileges on the database, including the ability to GRANT permissions to the app account: CREATE USER '${DATABASE_NAME}'@'localhost' IDENTIFIED BY '${PASSWORD}'; CREATE USER '${DATABASE_NAME}_password'@'localhost' IDENTIFIED BY '${OTHER_PASSWORD}'; GRANT ALL ON ${DATABASE_NAME}.* TO '${DATABASE_NAME}_password'@'localhost' WITH GRANT OPTION; You should run all migrations as the ph account, and GRANT specific access to the app account as needed. Adding the database functions on MySQL may require setting the log_bin_trust_function_creators=1 setting in the MySQL configuration. Microsoft SQL Server Database Setup Microsoft SQL Server has a concept of database owners, but similar to MySQL usage it’s recommended to use the ph account as the superuser for the database, and have it GRANT permissions to the app account: CREATE LOGIN rodauth_test WITH PASSWORD = 'rodauth_test'; CREATE LOGIN rodauth_test_password WITH PASSWORD = 'rodauth_test'; CREATE DATABASE rodauth_test; USE rodauth_test; CREATE USER rodauth_test FOR LOGIN rodauth_test; GRANT CONNECT, EXECUTE TO rodauth_test; EXECUTE sp_changedbowner 'rodauth_test_password'; You should run all migrations as the ph account, and GRANT specific access to the app account as needed. Creating tables Because two different database accounts are used, two different migrations are required, one for each database account. Here are example migrations. You can modify them to add support for additional columns, or remove tables or columns related to features that you don’t need. First migration. On PostgreSQL, this should be run with the app account, on MySQL and Microsoft SQL Server this should be run with the ph account. Note that these migrations require Sequel 4.35.0+. Sequel . migration do up do extension :date_arithmetic # Used by the account verification and close account features create_table ( :account_statuses ) do Integer :id , primary_key: true String :name , null: false , unique: true end from ( :account_statuses ). import ([ :id , :name ], [[ 1 , 'Unverified' ], [ 2 , 'Verified' ], [ 3 , 'Closed' ]]) db = self create_table ( :accounts ) do primary_key :id , type: :Bignum foreign_key :status_id , :account_statuses , null: false , default: 1 if db . database_type == :postgres citext :email , null: false constraint :valid_email , email: /^[^,;@ \r\n]+@[^,@; \r\n]+\.[^,@; \r\n]+$/ else String :email , null: false end if db . supports_partial_indexes? index :email , unique: true , where: { status_id: [ 1 , 2 ]} else index :email , unique: true end end deadline_opts = proc do | days | if database_type == :mysql { null: false } else { null: false , default: Sequel . date_add ( Sequel :: CURRENT_TIMESTAMP , days: days )} end end # Used by the audit logging feature json_type = case database_type when :postgres :jsonb when :sqlite , :mysql :json else String end create_table ( :account_authentication_audit_logs ) do primary_key :id , type: :Bignum foreign_key :account_id , :accounts , null: false , type: :Bignum DateTime :at , null: false , default: Sequel :: CURRENT_TIMESTAMP String :message , null: false column :metadata , json_type index [ :account_id , :at ], name: :audit_account_at_idx index :at , name: :audit_at_idx end # Used by the password reset feature create_table ( :account_password_reset_keys ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :key , null: false DateTime :deadline , deadline_opts [ 1 ] DateTime :email_last_sent , null: false , default: Sequel :: CURRENT_TIMESTAMP end # Used by the jwt refresh feature create_table ( :account_jwt_refresh_keys ) do primary_key :id , type: :Bignum foreign_key :account_id , :accounts , null: false , type: :Bignum String :key , null: false DateTime :deadline , deadline_opts [ 1 ] index :account_id , name: :account_jwt_rk_account_id_idx end # Used by the account verification feature create_table ( :account_verification_keys ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :key , null: false DateTime :requested_at , null: false , default: Sequel :: CURRENT_TIMESTAMP DateTime :email_last_sent , null: false , default: Sequel :: CURRENT_TIMESTAMP end # Used by the verify login change feature create_table ( :account_login_change_keys ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :key , null: false String :login , null: false DateTime :deadline , deadline_opts [ 1 ] end # Used by the remember me feature create_table ( :account_remember_keys ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :key , null: false DateTime :deadline , deadline_opts [ 14 ] end # Used by the lockout feature create_table ( :account_login_failures ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum Integer :number , null: false , default: 1 end create_table ( :account_lockouts ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :key , null: false DateTime :deadline , deadline_opts [ 1 ] DateTime :email_last_sent end # Used by the email auth feature create_table ( :account_email_auth_keys ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :key , null: false DateTime :deadline , deadline_opts [ 1 ] DateTime :email_last_sent , null: false , default: Sequel :: CURRENT_TIMESTAMP end # Used by the password expiration feature create_table ( :account_password_change_times ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum DateTime :changed_at , null: false , default: Sequel :: CURRENT_TIMESTAMP end # Used by the account expiration feature create_table ( :account_activity_times ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum DateTime :last_activity_at , null: false DateTime :last_login_at , null: false DateTime :expired_at end # Used by the single session feature create_table ( :account_session_keys ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :key , null: false end # Used by the active sessions feature create_table ( :account_active_session_keys ) do foreign_key :account_id , :accounts , type: :Bignum String :session_id Time :created_at , null: false , default: Sequel :: CURRENT_TIMESTAMP Time :last_use , null: false , default: Sequel :: CURRENT_TIMESTAMP primary_key [ :account_id , :session_id ] end # Used by the webauthn feature create_table ( :account_webauthn_user_ids ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :webauthn_id , null: false end create_table ( :account_webauthn_keys ) do foreign_key :account_id , :accounts , type: :Bignum String :webauthn_id String :public_key , null: false Integer :sign_count , null: false Time :last_use , null: false , default: Sequel :: CURRENT_TIMESTAMP primary_key [ :account_id , :webauthn_id ] end # Used by the otp feature create_table ( :account_otp_keys ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :key , null: false Integer :num_failures , null: false , default: 0 Time :last_use , null: false , default: Sequel :: CURRENT_TIMESTAMP end # Used by the otp_unlock feature create_table ( :account_otp_unlocks ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum Integer :num_successes , null: false , default: 1 Time :next_auth_attempt_after , null: false , default: Sequel :: CURRENT_TIMESTAMP end # Used by the recovery codes feature create_table ( :account_recovery_codes ) do foreign_key :id , :accounts , type: :Bignum String :code primary_key [ :id , :code ] end # Used by the sms codes feature create_table ( :account_sms_codes ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :phone_number , null: false Integer :num_failures String :code DateTime :code_issued_at , null: false , default: Sequel :: CURRENT_TIMESTAMP end case database_type when :postgres user = get ( Sequel . lit ( 'current_user' )) + '_password' run "GRANT REFERENCES ON accounts TO #{user}" when :mysql , :mssql user = if database_type == :mysql get ( Sequel . lit ( 'current_user' )). sub ( /_password@/ , '@' ) else get ( Sequel . function ( :DB_NAME )) end run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_statuses TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON accounts TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_authentication_audit_logs TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_password_reset_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_jwt_refresh_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_verification_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_login_change_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_remember_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_login_failures TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_email_auth_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_lockouts TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_password_change_times TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_activity_times TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_session_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_active_session_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_webauthn_user_ids TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_webauthn_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_otp_keys TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_otp_unlocks TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_recovery_codes TO #{user}" run "GRANT SELECT, INSERT, UPDATE, DELETE ON account_sms_codes TO #{user}" end end down do drop_table ( :account_sms_codes , :account_recovery_codes , :account_otp_unlocks , :account_otp_keys , :account_webauthn_keys , :account_webauthn_user_ids , :account_session_keys , :account_active_session_keys , :account_activity_times , :account_password_change_times , :account_email_auth_keys , :account_lockouts , :account_login_failures , :account_remember_keys , :account_login_change_keys , :account_verification_keys , :account_jwt_refresh_keys , :account_password_reset_keys , :account_authentication_audit_logs , :accounts , :account_statuses ) end end Second migration, run using the ph account: require 'rodauth/migrations' Sequel . migration do up do create_table ( :account_password_hashes ) do foreign_key :id , :accounts , primary_key: true , type: :Bignum String :password_hash , null: false end Rodauth . create_database_authentication_functions ( self ) case database_type when :postgres user = get ( Sequel . lit ( 'current_user' )). sub ( /_password\z/ , '' ) run "REVOKE ALL ON account_password_hashes FROM public" run "REVOKE ALL ON FUNCTION rodauth_get_salt(int8) FROM public" run "REVOKE ALL ON FUNCTION rodauth_valid_password_hash(int8, text) FROM public" run "GRANT INSERT, UPDATE, DELETE ON account_password_hashes TO #{user}" run "GRANT SELECT(id) ON account_password_hashes TO #{user}" run "GRANT EXECUTE ON FUNCTION rodauth_get_salt(int8) TO #{user}" run "GRANT EXECUTE ON FUNCTION rodauth_valid_password_hash(int8, text) TO #{user}" when :mysql user = get ( Sequel . lit ( 'current_user' )). sub ( /_password@/ , '@' ) db_name = get ( Sequel . function ( :database )) run "GRANT EXECUTE ON #{db_name}.* TO #{user}" run "GRANT INSERT, UPDATE, DELETE ON account_password_hashes TO #{user}" run "GRANT SELECT (id) ON account_password_hashes TO #{user}" when :mssql user = get ( Sequel . function ( :DB_NAME )) run "GRANT EXECUTE ON rodauth_get_salt TO #{user}" run "GRANT EXECUTE ON rodauth_valid_password_hash TO #{user}" run "GRANT INSERT, UPDATE, DELETE ON account_password_hashes TO #{user}" run "GRANT SELECT ON account_password_hashes(id) TO #{user}" end # Used by the disallow_password_reuse feature create_table ( :account_previous_password_hashes ) do primary_key :id , type: :Bignum foreign_key :account_id , :accounts , type: :Bignum String :password_hash , null: false end Rodauth . create_database_previous_password_check_functions ( self ) case database_type when :postgres user = get ( Sequel . lit ( 'current_user' )). sub ( /_password\z/ , '' ) run "REVOKE ALL ON account_previous_password_hashes FROM public" run "REVOKE ALL ON FUNCTION rodauth_get_previous_salt(int8) FROM public" run "REVOKE ALL ON FUNCTION rodauth_previous_password_hash_match(int8, text) FROM public" run "GRANT INSERT, UPDATE, DELETE ON account_previous_password_hashes TO #{user}" run "GRANT SELECT(id, account_id) ON account_previous_password_hashes TO #{user}" run "GRANT USAGE ON account_previous_password_hashes_id_seq TO #{user}" run "GRANT EXECUTE ON FUNCTION rodauth_get_previous_salt(int8) TO #{user}" run "GRANT EXECUTE ON FUNCTION rodauth_previous_password_hash_match(int8, text) TO #{user}" when :mysql user = get ( Sequel . lit ( 'current_user' )). sub ( /_password@/ , '@' ) db_name = get ( Sequel . function ( :database )) run "GRANT EXECUTE ON #{db_name}.* TO #{user}" run "GRANT INSERT, UPDATE, DELETE ON account_previous_password_hashes TO #{user}" run "GRANT SELECT (id, account_id) ON account_previous_password_hashes TO #{user}" when :mssql user = get ( Sequel . function ( :DB_NAME )) run "GRANT EXECUTE ON rodauth_get_previous_salt TO #{user}" run "GRANT EXECUTE ON rodauth_previous_password_hash_match TO #{user}" run "GRANT INSERT, UPDATE, DELETE ON account_previous_password_hashes TO #{user}" run "GRANT SELECT ON account_previous_password_hashes(id, account_id) TO #{user}" end end down do Rodauth . drop_database_previous_password_check_functions ( self ) Rodauth . drop_database_authentication_functions ( self ) drop_table ( :account_previous_password_hashes , :account_password_hashes ) end end To support multiple separate migration users, you can run the migration for the password user using Sequel’s migration API: Sequel . extension :migration Sequel . postgres ( 'DATABASE_NAME' , user: 'PASSWORD_USER_NAME' ) do | db | Sequel :: Migrator . run ( db , 'path/to/password_user/migrations' , table: 'schema_info_password' ) end If the database is not PostgreSQL, MySQL, or Microsoft SQL Server, or you cannot use multiple user accounts, just combine the two migrations into a single migration, removing all the code related to database permissions and database functions. One thing to notice in the above migrations is that Rodauth uses additional tables for additional features, instead of additional columns in a single table. Revoking schema rights (PostgreSQL 15+) If you explicit granted access to the public schema before running the migration, revoke it afterward: psql -U postgres -c "REVOKE CREATE ON SCHEMA public FROM ${DATABASE_NAME}_password" ${DATABASE_NAME} Locking Down (PostgreSQL only) After running the migrations, you can increase security slightly by making it not possible for the ph account to login to the database directly. This can be accomplished by modifying the pg_hba.conf file. You can also consider restricting access using GRANT/REVOKE. You can restrict access to the database itself to just the app account. You can run this using the app account, since that account owns the database: GRANT ALL ON DATABASE ${DATABASE_NAME} TO ${DATABASE_NAME}; REVOKE ALL ON DATABASE ${DATABASE_NAME} FROM public; You can also restrict access to the public schema (this is not needed if you are using a custom schema). Note that by default, the database superuser owns the public schema, so you have to run this as the database superuser account (generally postgres ): GRANT ALL ON SCHEMA public TO ${DATABASE_NAME}; GRANT USAGE ON SCHEMA public TO ${DATABASE_NAME}_password; REVOKE ALL ON SCHEMA public FROM public; If you are using MySQL or Microsoft SQL Server, please consult their documentation for how to restrict access so that the ph account cannot login directly. Usage Basic Usage Rodauth is a Roda plugin and loaded the same way other Roda plugins are loaded: plugin :rodauth do end The block passed to the plugin call uses the Rodauth configuration DSL. The one configuration method that should always be used is enable , which chooses which features you would like to load: plugin :rodauth do enable :login , :logout end Once features are loaded, you can use any of the configuration methods supported by the features. There are two types of configuration methods. The first type are called auth methods, and they take a block which overrides the default method that Rodauth uses. Inside the block, you can call super if you want to get the default behavior, though you must provide explicit arguments to super. There is no need to call super in before or after hooks, though. For example, if you want to add additional logging when a user logs in: plugin :rodauth do enable :login , :logout after_login do LOGGER . info "#{account[:email]} logged in!" end end Inside the block, you are in the context of the Rodauth::Auth instance related to the request. This object has access to everything related to the request via methods: request RodaRequest instance response RodaResponse instance scope Roda instance session session hash flash flash message hash account account hash (if set by an earlier Rodauth method) current_route route name symbol (if Rodauth is handling the route) So if you want to log the IP address for the user during login: plugin :rodauth do enable :login , :logout after_login do LOGGER . info "#{account[:email]} logged in from #{request.ip}" end end The second type of configuration methods are called auth value methods. They are similar to auth methods, but instead of just accepting a block, they can optionally accept a single argument without a block, which will be treated as a block that just returns that value. For example, the accounts_table method sets the database table storing accounts, so to override it, you can call the method with a symbol for the table: plugin :rodauth do enable :login , :logout accounts_table :users end Note that all auth value methods can still take a block, allowing overriding for all behavior, using any information from the request: plugin :rodauth do enable :login , :logout accounts_table do request . ip . start_with? ( "192.168.1." ) ? :admins : :users end end By allowing every configuration method to take a block, Rodauth should be flexible enough to integrate into most legacy systems. Plugin Options When loading the rodauth plugin, you can also pass an options hash, which configures which dependent plugins should be loaded. Options: :csrf Set to false to not load a csrf plugin. Set to :rack_csrf to use the csrf plugin instead of the route_csrf plugin. :flash Set to false to not load the flash plugin :render Set to false to not load the render plugin. This is useful to avoid the dependency on tilt when using alternative view libraries. :json Set to true to load the json and json_parser plugins. Set to :only to only load those plugins and not any other plugins. Note that if you are enabling features that send email, you still need to load the render plugin manually. :name Provide a name for the given Rodauth configuration, used to support multiple Rodauth configurations in a given Roda application. :auth_class Provide a specific Rodauth::Auth subclass that should be set on the Roda application. By default, an anonymous Rodauth::Auth subclass is created. Calling Rodauth in the Routing Tree In general, you will usually want to call r.rodauth early in your route block: route do | r | r . rodauth # ... end Note that will allow Rodauth to run, but it won’t force people to login or add any security to your site. If you want to force all users to login, you need to redirect to them login page if they are not already logged in: route do | r | r . rodauth rodauth . require_authentication # ... end If only certain parts of your site require logins, then you can only redirect if they are not logged in certain branches of the routing tree: route do | r | r . rodauth r . on "admin" do rodauth . require_authentication # ... end # ... end In some cases you may want to have rodauth run inside a branch of the routing tree, instead of in the root. You can do this by setting a :prefix when configuring Rodauth, and calling r.rodauth inside a matching routing tree branch: plugin :rodauth do enable :login , :logout prefix "/auth" end route do | r | r . on "auth" do r . rodauth end rodauth . require_authentication # ... end rodauth Methods Most of Rodauth’s functionality is exposed via r.rodauth , which allows Rodauth to handle routes for the features you have enabled (such as /login for login). However, as you have seen above, you may want to call methods on the rodauth object, such as for checking if the current request has been authenticated. Here are methods designed to be callable on the rodauth object outside r.rodauth : require_login Require the session be logged in, redirecting the request to the login page if the request has not been logged in. require_authentication Similar to require_login , but also requires two factor authentication if the account has setup two factor authentication. Redirects the request to the two factor authentication page if logged in but not authenticated via two factors. require_account Similar to require_authentication , but also loads the logged in account to ensure it exists in the database. If the account doesn’t exist, or if it exists but isn’t verified, the session is cleared and the request redirected to the login page. logged_in? Whether the session has been logged in. authenticated? Similar to logged_in? , but if the account has setup two factor authentication, whether the session has authenticated via two factors. account! Returns the current account record if it has already been loaded, otherwise retrieves the account from session if logged in. authenticated_by An array of strings for successful authentication methods for the current session (e.g. password/remember/webauthn). possible_authentication_methods An array of strings for possible authentication types that can be used for the account. autologin_type If the current session was authenticated via autologin, the type of autologin used. require_two_factor_setup (two_factor_base feature) Require the session to have setup two factor authentication, redirecting the request to the two factor authentication setup page if not. two_factor_partially_authenticated? (two_factor_base feature) Returns true if the session is logged in, the account has setup two factor authentication, but has not yet authenticated with a second factor. uses_two_factor_authentication? (two_factor_base feature) Whether the account for the current session has setup two factor authentication. update_last_activity (account_expiration feature) Update the last activity time for the current account. Only makes sense to use this if you are expiring accounts based on last activity. require_current_password (password_expiration feature) Require a current password, redirecting the request to the change password page if the password for the account has expired. require_password_authentication (confirm_password feature) If not authenticated via password and the account has a password, redirect to the password confirmation page, saving the current location to redirect back to after password has been successfully confirmed. If the password_grace_period feature is used, also redirect if the password has not been recently entered. load_memory (remember feature) If the session has not been authenticated, look for the remember cookie. If present and valid, automatically log the session in, but mark that it was logged in via a remember key. logged_in_via_remember_key? (remember feature) Whether the current session has been logged in via a remember key. For security sensitive actions where you want to require the user to reenter the password, you can use the confirm_password feature. http_basic_auth (http_basic_auth feature) Use HTTP Basic Authentication information to login the user if provided. require_http_basic_auth (http_basic_auth feature) Require that HTTP Basic Authentication be provided in the request. check_session_expiration (session_expiration feature) Check whether the current session has expired, automatically logging the session out if so. check_active_session (active_sessions feature) Check whether the current session is still active, automatically logging the session out if not. check_single_session (single_session feature) Check whether the current session is still the only valid session, automatically logging the session out if not. verified_account? (verify_grace_period feature) Whether the account is currently verified. If false, it is because the account is allowed to login as they are in the grace period. locked_out? (lockout feature) Whether the account for the current session has been locked out. authenticated_webauthn_id (webauthn feature) If the current session was authenticated via webauthn, the webauthn id of the credential used. *_path One of these is added for each of the routes added by Rodauth, giving the relative path to the route. Any options passed to this method will be converted into query parameters. *_url One of these is added for each of the routes added by Rodauth, giving the URL to the route. Any options passed to this method will be converted into query parameters. Calling Rodauth Methods for Other Accounts In some cases, you may want to interact with Rodauth directly on behalf of a user. For example, let’s say you want to create accounts or change passwords for existing accounts. Using Rodauth’s internal_request feature, you can do this by: plugin :rodauth do enable :create_account , :change_password , :internal_request end rodauth . create_account ( login: 'foo@example.com' , password: '...' ) rodauth . change_password ( account_id: 24601 , password: '...' ) Here the rodauth method is called as the Roda class level, which returns the appropriate Rodauth::Auth subclass. You call internal request methods on that class to perform actions on behalf of a user. See the internal request feature documentation for details. Using Rodauth as a Library Rodauth was designed to serve as an authentication framework for Rack applications. However, Rodauth can be used purely as a library outside of a web application. You can do this by requiring rodauth , and using the Rodauth.lib method to return a Rodauth::Auth subclass, which you can call methods on. You pass the Rodauth.lib method an optional hash of Rodauth plugin options and a Rodauth configuration block: require 'rodauth' rodauth = Rodauth . lib do enable :create_account , :change_password end rodauth . create_account ( login: 'foo@example.com' , password: '...' ) rodauth . change_password ( account_id: 24601 , password: '...' ) This supports builds on top of the internal_request support (it implicitly loads the internal_request feature before processing the configuration block), and allows the use of Rodauth in non-web applications. Note that you still have to setup a Sequel::Database connection for Rodauth to use for data storage. With Multiple Configurations Rodauth supports using multiple rodauth configurations in the same application. You just need to load the plugin a second time, providing a name for any alternate configuration: plugin :rodauth do end plugin :rodauth , name: :secondary do end Then in your routing code, any time you call rodauth, you can provide the name as an argument to use that configuration: route do | r | r . on 'secondary' do r . rodauth ( :secondary ) end r . rodauth end To prevent having to specify the name manually in all cases where you are using it, you can define a default_rodauth_name method in your Roda application that returns the name that should be used: attr_reader :default_rodauth_name route do | r | r . on 'secondary' do @default_rodauth_name = :secondary r . rodauth # will use the :secondary configuration end r . rodauth # will use the default configuration end By default, alternate configurations will use the same session keys as the primary configuration, which may be undesirable. To ensure session state is separated between configurations, you can set a session key prefix for alternate configurations. If you are using the remember feature in both configurations, you may also want to set a different remember key in the alternate configuration: plugin :rodauth , name: :secondary do session_key_prefix "secondary_" remember_cookie_key "_secondary_remember" end With Password Hashes Inside the Accounts Table You can use Rodauth if you are storing password hashes in the same table as the accounts. You just need to specify which column stores the password hash: plugin :rodauth do account_password_hash_column :password_hash end When this option is set, Rodauth will do the password hash check in ruby. When Using PostgreSQL/MySQL/Microsoft SQL Server without Database Functions If you want to use Rodauth on PostgreSQL, MySQL, or Microsoft SQL Server without using database functions for authentication, but still storing password hashes in a separate table, you can do so: plugin :rodauth do use_database_authentication_functions? false end Conversely, if you implement the rodauth_get_salt and rodauth_valid_password_hash functions on a database that isn’t PostgreSQL, MySQL, or Microsoft SQL Server, you can set this value to true. With Custom Authentication You can use Rodauth with other authentication types, by using some of Rodauth’s configuration methods. Note that when using custom authentication, using some of Rodauth’s features such as change login and change password either would not make sense or would require some additional custom configuration. The login and logout features should work correctly with the examples below, though. Using LDAP Authentication If you have accounts stored in the database, but authentication happens via LDAP, you can use the simple_ldap_authenticator library: require 'simple_ldap_authenticator' plugin :rodauth do enable :login , :logout require_bcrypt? false password_match? do | password | SimpleLdapAuthenticator . valid? ( account [ :email ], password ) end end If you aren’t storing accounts in the database, but want to allow any valid LDAP user to login, you can do something like this: require 'simple_ldap_authenticator' plugin :rodauth do | 2026-01-13T09:30:25 |
https://www.linkedin.com/login?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fcoreboot&fromSignIn=true&trk=organization_guest_nav-header-signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/minitest-global_expectations/actions/workflows/ci.yml | CI · Workflow runs · jeremyevans/minitest-global_expectations · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / minitest-global_expectations Public Notifications You must be signed in to change notification settings Fork 1 Star 6 Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights Actions: jeremyevans/minitest-global_expectations Actions --> All workflows Workflows CI CI Show more workflows... Management Caches CI CI Actions Loading... Loading Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> will be ignored since log searching is not yet available Show workflow options Create status badge Create status badge Loading Uh oh! There was an error while loading. Please reload this page . ci.yml --> will be ignored since log searching is not yet available 7 workflow runs 7 workflow runs Event Filter by Event Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching events. Status Filter by Status Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching statuses. Branch Filter by Branch Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching branches. Actor Filter by Actor Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching users. Add Ruby 4.0 to CI CI #13: Commit cd5db1f pushed by jeremyevans 14m 34s master master 14m 34s View workflow file Bump version to 1.0.2 CI #12: Commit 4c88bdf pushed by jeremyevans 45s master master 45s View workflow file Add gem metadata and required_ruby_version CI #11: Commit e549a45 pushed by jeremyevans 52s master master 52s View workflow file Add JRuby 10.0 to CI CI #10: Commit b51cef8 pushed by jeremyevans 6m 8s master master 6m 8s View workflow file Work with ubuntu-latest using 24.04 by default in CI CI #9: Commit 7cf392a pushed by jeremyevans 48s master master 48s View workflow file Add Ruby 3.4 to CI CI #8: Commit 7af0c43 pushed by jeremyevans 2m 44s master master 2m 44s View workflow file Use -W:strict_unused_block when running tests on Ruby 3.4+ CI #7: Commit b5ab1a6 pushed by jeremyevans 1m 6s master master 1m 6s View workflow file You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://rubygems.org/gems/forme | forme | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up forme 2.7.0 Forme is a forms library with the following goals: 1) Have no external dependencies 2) Have a simple API 3) Support forms both with and without related objects 4) Allow compiling down to different types of output 5) Integrate easily into web frameworks Gemfile: = install: = Versions: 2.7.0 September 16, 2025 (54.5 KB) 2.6.0 June 18, 2024 (54.5 KB) 2.5.0 February 13, 2024 (54 KB) 2.4.1 September 19, 2023 (53.5 KB) 2.4.0 April 05, 2023 (53.5 KB) Show all versions (30 total) Runtime Dependencies (1): bigdecimal >= 0 Development Dependencies (10): erubi >= 0 i18n >= 0 minitest >= 5.7.0 minitest-global_expectations >= 0 rack_csrf >= 0 rails >= 0 roda >= 0 sequel >= 4 sinatra >= 0 tilt >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 128,312 For this version 4,124 Version Released: September 16, 2025 4:56pm License: MIT Required Ruby Version: >= 1.9.2 Links: Homepage Changelog Source Code Documentation Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://rubygems.org/gems/asciidoctor/versions/2.0.26?locale=ja | asciidoctor | RubyGems.org | コミュニティのgemホスティングサービス ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> gemを検索... リリース ブログ Gems ガイド サインイン 新規登録 asciidoctor 2.0.26 A fast, open source text processor and publishing toolchain for converting AsciiDoc content to HTML 5, DocBook 5, and other formats. Gemfile: = インストール: = バージョン履歴: 2.0.26 October 24, 2025 (278KB) 2.0.25 October 16, 2025 (278KB) 2.0.24 October 13, 2025 (278KB) 2.0.23 May 17, 2024 (277KB) 2.0.22 March 08, 2024 (276KB) 全てのバージョンを表示（全78件） Development依存関係 (9): concurrent-ruby ~> 1.1.0 cucumber ~> 3.1.0 erubi ~> 1.10.0 haml ~> 6.3.0 minitest ~> 5.22.0 nokogiri ~> 1.13.0 rake ~> 12.3.0 slim ~> 4.1.0 tilt ~> 2.0.0 全ての推移的な依存関係を表示 所有者: プッシュ者: 作者: Dan Allen, Sarah White, Ryan Waldron, Jason Porter, Nick Hengeveld, Jeremy McAnally SHA 256チェックサム: = ←前のバージョン 累計ダウンロード数 52,497,923 このバージョンのみ 363,442 このバージョンがリリースされたのは: October 24, 2025 1:49am ライセンス: MIT 必要なRubyのバージョン: >= 0 リンク: ホームページ 変更履歴 ソースコード メーリングリスト バグトラッカー ダウンロード 寄付 差分をレビュー バッジ 購読 RSS 悪用報告 被依存関係 状態 稼働時間 コード データ 統計 貢献 概要 ヘルプ API ポリシー 支援 セキュリティ RubyGems.orgはRubyコミュニティのgemのホスティングサービスです。すぐに gemを公開 して インストール できます。 API を使用して 利用可能なgem の詳細を調べられます。ご自身が 貢献者となり サイトをより良くしてください。 RubyGems.orgのウェブサイトとサービスはRuby Centralの オープンソースプログラムOpen Source Program とRubyGemsチームによって保守・運用されています。 スポンサー、メンバー、インスラへの寄付を通じて、広くRubyコミュニティ全体によって支援されています。 Rubyで開発を行い、私達の理念に共感してくださるのであれば、RubyGems.org、RubyGems、Bundlerを今後も安全で持続可能なものにするために、 こちら からご参加ください。 運営 Ruby Central 設計 DockYard ホスト AWS DNS DNSimple 監視 Datadog gemの提供 Fastly 監視 Honeybadger セキュリティ Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/syntax-highlighting/formatting/ | Format the Source Block Element | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Syntax Highlighter API Format the Source Block Element 3.0 3.0 2.5 Edit this Page Format the Source Block Element highlight.js tries to automatically determine the source language, which might fail or result in wrong matches. To help highlight.js in identifying the correct source language the <code/> element can be annotated with the language as a class. That means instead of simply wrapping the code in <pre/> and <code/> elements we want to wrap it inside <pre> and <code class="java"/> . To allow Asciidoctor to apply the styles to properly embed a source block inside the document, the <pre/> element should also have the class highlight . Therefore we want to wrap the source text inside this construct: <pre class="highlight"> <code class="java"> ... </code> </pre> To allow a syntax highlighter to create this construct it also has to implement the interface org.asciidoctor.syntaxhighlighter.Formatter : import org.asciidoctor.syntaxhighlighter.Formatter; import org.asciidoctor.syntaxhighlighter.SyntaxHighlighterAdapter; import java.util.Map; public class HighlightJsWithLanguageHighlighter implements SyntaxHighlighterAdapter, Formatter { (1) // Methods hasDocInfo() and getDocInfo() @Override public String format(Block node, String lang, Map<String, Object> opts) { return "<pre class='highlight'><code class='" + lang + "'>" (2) + node.getContent() (3) + "</code></pre>"; } } 1 The SyntaxHighlighterAdapter also has to implement the interface Formatter . This interface only requires the implementation of the method format() that receives the org.asciidoctor.ast.Block that is highlighted, the source language, and additional options. 2 The implementation of format() wraps everything in a <pre/> and <code/> element with the required classes. The value for the class of the <code/> element is the source language which is passed as an argument to the method. 3 The source text to be nested into the <pre/> and <code/> elements has to be obtained using node.getContent() . This guarantees that further processing like substitutions work properly. Lifecycle of a SyntaxHighlighterAdapter Link and Copy External Resources Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://rubygems.org/gems/tilt | tilt | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up tilt 2.7.0 Generic interface to multiple Ruby template engines Gemfile: = install: = Versions: 2.7.0 January 09, 2026 (30 KB) 2.6.1 July 07, 2025 (26 KB) 2.6.0 January 13, 2025 (26 KB) 2.5.0 December 20, 2024 (25 KB) 2.4.0 June 27, 2024 (25.5 KB) Show all versions (46 total) Owners: Pushed by: Authors: Ryan Tomayko, Magnus Holm, Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 713,608,026 For this version 131,985 Version Released: January 9, 2026 5:53pm License: MIT Required Ruby Version: >= 2.0 Links: Homepage Changelog Documentation Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctor/latest/install/supported-platforms/ | Supported Platforms and System Requirements | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets Asciidoctor Features What’s New in 2.0 Install and Update Supported Platforms Install Using Ruby Packaging Install Using Linux Packaging Install on macOS Install on Windows Convert Your First File Converters Available Converters Custom Converter Converter Templates Convertible Contexts Generate HTML Stylesheets Default Stylesheet Stylesheet Modes Apply a Custom Stylesheet Embed a CodeRay or Pygments Stylesheet Manage Images Use Local Font Awesome Add a Favicon Verbatim Block Line Wrapping Skip Front Matter Generate DocBook Generate Manual Pages Process AsciiDoc Using the CLI asciidoctor(1) Specify an Output File Process Multiple Source Files Pipe Content Through the CLI Set Safe Mode CLI Options Process AsciiDoc Using the API Load and Convert Files Load and Convert Strings Generate an HTML TOC Set Safe Mode Enable the Sourcemap Catalog Assets Find Blocks API Options Safe Modes Safe Mode Specific Content AsciiDoc Tooling Syntax Highlighting Highlight.js Rouge CodeRay Pygments Custom Adapter STEM Processing MathJax and HTML Asciidoctor Mathematical STEM Support in the DocBook Toolchain AsciiMath Gem Extensions Register Extensions Log from an Extension Preprocessor Tree Processor Postprocessor Docinfo Processor Block Processor Compound Block Processor Block Macro Processor Inline Macro Processor Include Processor Localization Support Errors and Warnings Migration Guides Upgrade from Asciidoctor 1.5.x to 2.0 Migrate from AsciiDoc.py Migrate from DocBook XML Migrate from Markdown Migrate from Confluence XHTML Migrate from MS Word Asciidoctor 2.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community Asciidoctor Install and Update Supported Platforms Edit this Page Supported Platforms and System Requirements Asciidoctor operates on Linux, macOS, and Windows and requires one of the supported Ruby implementations listed in the next section. Our general policy is to align Asciidoctor’s support of a platform version with the upstream project’s lifecycle schedule for that version. When a platform version reaches the end of active support by its maintainers or its end of life—​which ever comes first—​Asciidoctor no longer supports it. Ruby runtimes Asciidoctor requires one of the following implementations of Ruby . Supported Runtime Supported Versions Ruby ≥ 2.3 JRuby ≥ 9.1 TruffleRuby ≥ 20.2 Operating systems Supported OS Supported Versions Ubuntu ≥ 18.04 LTS Fedora ≥ 36 macOS ≥ macOS 11 (Big Sur) Microsoft ≥ Windows 10 Windows Server 2019 While the community tests Asciidoctor on a variety of Linux distributions, it’s only officially tested on Ubuntu and Fedora. System encoding Asciidoctor assumes you’re using UTF-8 encoding. To minimize encoding problems, make sure the default encoding of your system is set to UTF-8. If you’re using a non-English Windows environment, you may bump into an Encoding::UndefinedConversionError when invoking Asciidoctor. To solve this issue, we recommend overriding the default external and internal character encodings to utf-8 . You can do so by setting the RUBYOPT environment variable as follows: RUBYOPT="-E utf-8:utf-8" Once you make this change, all your Unicode headaches should be behind you. If you’re using an IDE like Eclipse, make sure you set the encoding to UTF-8 there as well. Asciidoctor is optimized to work with UTF-8 as the default encoding. Install and Update Install Using Ruby Packaging Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/syntax-highlighting/link-external-resources/ | Link and Copy External Resources | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Syntax Highlighter API Link and Copy External Resources 3.0 3.0 2.5 Edit this Page Link and Copy External Resources In Implement a Syntax Highlighter Adapter we have seen how to implement a basic syntax highlighter that embeds all required resources as DocInfo in the document. When the document is converted with the attributes :linkcss and :copycss we expect though that these resources are also written to disk next to the document, and that the document only references them. Looking at our current example of the highlight.js adapter we referenced the resources from the internet. For scenarios where it should also be possible to read the document while offline, the syntax highlighter can implement the interface org.asciidoctor.syntaxhighlighter.StylesheetWriter : public class HighlightJsWithOfflineStylesHighlighter implements SyntaxHighlighterAdapter, Formatter, StylesheetWriter { (1) @Override public boolean hasDocInfo(LocationType location) { return location == LocationType.FOOTER; } @Override public String getDocinfo(LocationType location, Document document, Map<String, Object> options) { if (document.hasAttribute("linkcss") && document.hasAttribute("copycss")) { (2) return "<link rel=\"stylesheet\" href=\"github.min.css\">\n" + "<script src=\"highlight.min.js\"></script>\n" + "<script>hljs.initHighlighting()</script>"; } else { return "<link rel=\"stylesheet\" href=\"https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.15.6/styles/github.min.css\">\n" + "<script src=\"https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.15.6/highlight.min.js\"></script>\n" + "<script>hljs.initHighlighting()</script>"; } } @Override public String format(Block node, String lang, Map<String, Object> opts) { return "<pre class='highlight'><code class='" + lang + "'>" + node.getContent() + "</code></pre>"; } @Override public boolean isWriteStylesheet(Document doc) { return true; (3) } @Override public void writeStylesheet(Document doc, File toDir) { try { (4) URL url1 = new URL("https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.15.6/styles/github.min.css"); URL url2 = new URL("https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.15.6/highlight.min.js"); try (InputStream in1 = url1.openStream(); OutputStream fout1 = new FileOutputStream(new File(toDir, "github.min.css"))) { IOUtils.copy(in1, fout1); } catch (IOException ioe) { throw new RuntimeException(ioe); } try (InputStream in2 = url2.openStream(); OutputStream fout2 = new FileOutputStream(new File(toDir, "highlight.min.js"))) { IOUtils.copy(in2, fout2); } catch (IOException ioe) { throw new RuntimeException(ioe); } } catch (MalformedURLException e) { throw new RuntimeException(e); } } } 1 A syntax highlighter that writes additional resources to the filesystem next to the document must implement the interface org.asciidoctor.syntaxhighlighter.StylesheetWriter . 2 If the document is converted with the attributes :copycss and :linkcss the DocInfo that is added to the converted document should link to the local resources. 3 The syntax highlighter should return if it wants to write stylesheets in isWriteStylesheet() . This method could for example examine the document if it really needs external resources and return the corresponding result. 4 The method writeStylesheet() gets the org.asciidoctor.ast.Document and the File for the target directory where the document should be written. External resources should be written to this directory as well. This highlighter writes the css and js resources to files in the same directory as the document if it is converted with the attributes :linkcss and :copycss : File toDir = // ... asciidoctor.syntaxHighlighterRegistry() .register(HighlightJsWithOfflineStylesHighlighter.class, "myhighlightjs"); asciidoctor.convertFile(sources_adoc, Options.builder() .standalone(true) .toDir(toDir) (1) .safe(SafeMode.UNSAFE) .attributes(Attributes.builder() .sourceHighlighter("myhighlightjs") .copyCss(true) (1) .linkCss(true) .build()) .build()); File docFile = new File(toDir, "sources.html"); assertTrue(docFile.exists()); File cssFile = new File(toDir, "github.min.css"); assertTrue(cssFile.exists()); File jsFile = new File(toDir, "highlight.min.js"); assertTrue(jsFile.exists()); String html = Files.readString(Path.of(toDir.toURI()).resolve("sources.html")); assertThat(html, containsString("<link rel=\"stylesheet\" href=\"github.min.css\">")); assertThat(html, containsString("<script src=\"highlight.min.js\"></script>")); 1 External stylesheets are only written when converting to a file, not when converting to a stream or a string, and when the attributes :linkcss and :copycss are set. Format the Source Block Element Static Syntax Highlighting During Conversion Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/guides/run-in-wildfly/ | Running AsciidoctorJ on WildFly | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Help & Guides Running in Frameworks Running AsciidoctorJ on WildFly 3.0 3.0 2.5 Edit this Page Running AsciidoctorJ on WildFly If you want to use AsciidoctorJ in an application deployed on WildFly , you have to follow the instruction below: Create an Asciidoctor module for WildFly . Create the following folder tree: $JBOSS_HOME/modules/org/asciidoctor/main . Create the module descriptor file module.xml . Asciidoctor module descriptor for WildFly <?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.0" name="org.asciidoctor"> <resources> <resource-root path="asciidoctorj-api-3.0.0.jar"/> <resource-root path="asciidoctorj-3.0.0.jar"/> <resource-root path="jcommander-1.72.jar"/> <resource-root path="jruby-complete-9.4.1.0.jar"/> </resources> <dependencies> <module name="sun.jdk" export="true"> <imports> <include path="sun/misc/Unsafe" /> </imports> </module> <module name="javax.management.j2ee.api"/> <module name="javax.api"/> <module name="org.slf4j"/> </dependencies> </module> Copy the jar files into the same folder as the module.xml file. Make sure the version numbers of the jar files agree with what’s in the current set. Restart WildFly for the new module to take effect. Add a dependency on your Java archive to this WildFly module using one of the following options: Add the dependency just into the MANIFEST.MF file. MANIFEST.MF file example with dependency to Asciidoctor module Manifest-Version: 1.0 Dependencies: org.asciidoctor ... Or , configure the dependency into the pom.xml with the Maven JAR/WAR plugin . pom.xml file example with Maven WAR plugin configuration to add a dependency ... <dependencies> <dependency> <groupId>org.asciidoctor</groupId> <artifactId>asciidoctorj</artifactId> <version>3.0.0</version> <scope>provided</scope> (1) ... </dependency> </dependencies> ... <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.4</version> <configuration> <archive> <manifestEntries> <Dependencies>org.asciidoctor</Dependencies> (2) </manifestEntries> </archive> </configuration> </plugin> ... 1 The AsciidoctorJ dependency and the transitives dependencies don’t need to be added to the final WAR since all JARs are available through the module. 2 The module dependency will be added to the MANIFEST.MF file. Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ with Spring Boot Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/gradle-plugin/latest/ | Asciidoctor Gradle Plugin Suite | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets Gradle Plugin Suite Compatibility Quick Start Task Configuration Plugins AsciidoctorJ Base Plugin AsciidoctorJ Plugin AsciidoctorJ PDF plugin AsciidoctorJ EPUB plugin AsciidoctorJ Reveal.js plugin AsciidoctorJ GEMs plugin Asciidoctor Editor Config Plugin Using AsciidoctorJ Diagram Adding Custom Extensions Extra content for HTML & Docbook backends Upgrading From Older Versions of Asciidoctor Appendices Working with Asciidoctor.js Tips & Tricks Known Issues Development Gradle Plugin Suite 4.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community Gradle Plugin Suite Introduction 4.0 5.0 4.0 Edit this Page Asciidoctor Gradle Plugin Suite The Asciidoctor Gradle Plugin Suite is the official means of using Asciidoctor to convert all your AsciiDoc documentation using Gradle . This started as a port of the asciidoctor-maven-plugin project founded by Jason Porter and relies on AsciidoctorJ which was founded by Alex Soto . In fact the 1.5.x series of the Asciidoctor Gradle plugin can still be considered a port. However, with 2.x series came a complete departure with functionality far exceeding any lightweight markup plugins for any other build tool. With the 3.x serious allows for even more flexibility and options for the creation of a true DocuOps pipeline by bringing together Gradle as a powerful and generic build tool, and Asciidoctor as an agile and lightweight document generator. Compatibility Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://lists.macports.org/pipermail/macports-dev/2016-December/author.html#start | The macports-dev December 2016 Archive by author December 2016 Archives by author Messages sorted by: [ thread ] [ subject ] [ date ] More info on this list... Starting: Thu Dec 1 01:23:36 CET 2016 Ending: Sat Dec 31 20:08:23 CET 2016 Messages: 333 [macports-ports] branch master updated: pingus: new port submission Brandon Allbery [macports-ports] branch master updated: pingus: new port submission Brandon Allbery port requires c++1y -> use cxx11 portgroup? Brandon Allbery [macports-ports] branch master updated: pingus: new port submission Brandon Allbery `port edit`, local/console vs. remote use Brandon Allbery `port edit`, local/console vs. remote use Brandon Allbery `port edit`, local/console vs. remote use Brandon Allbery `port edit`, local/console vs. remote use Brandon Allbery `port edit`, local/console vs. remote use Brandon Allbery declaring variants/subports in loops and loop variables Brandon Allbery declaring variants/subports in loops and loop variables Brandon Allbery declaring variants/subports in loops and loop variables Brandon Allbery declaring variants/subports in loops and loop variables Brandon Allbery declaring variants/subports in loops and loop variables Brandon Allbery declaring variants/subports in loops and loop variables Brandon Allbery Question about bootstrapping MinGW Brandon Allbery Question about bootstrapping MinGW Brandon Allbery Pasting with the mouse between tabs does not work (anymore) Mark Anderson Unintentional double commits David Bariod Contributed patches for `port environment` and a more generalised `port info --var` René J.V. Bertin Tcl list-related 2.3.4 -> 2.3.5 changes? René J.V. Bertin [RJVB/macstrop] use github ID for maintainer (2fb8aab) René J.V. Bertin [RJVB/macstrop] use github ID for maintainer (2fb8aab) René J.V. Bertin [RJVB/macstrop] use github ID for maintainer (2fb8aab) René J.V. Bertin Tcl list-related 2.3.4 -> 2.3.5 changes? René J.V. Bertin [RJVB/macstrop] use github ID for maintainer (2fb8aab) René J.V. Bertin PR final steps (to squash or not to squash) René J.V. Bertin PR final steps (to squash or not to squash) René J.V. Bertin PR final steps (to squash or not to squash) René J.V. Bertin PR final steps (to squash or not to squash) René J.V. Bertin PR final steps (to squash or not to squash) René J.V. Bertin PR final steps (to squash or not to squash) René J.V. Bertin PR final steps (to squash or not to squash) René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin declaring variants/subports in loops and loop variables René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin `port edit`, local/console vs. remote use René J.V. Bertin declaring variants/subports in loops and loop variables René J.V. Bertin declaring variants/subports in loops and loop variables René J.V. Bertin declaring variants/subports in loops and loop variables René J.V. Bertin declaring variants/subports in loops and loop variables René J.V. Bertin declaring variants/subports in loops and loop variables René J.V. Bertin declaring variants/subports in loops and loop variables René J.V. Bertin Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more René J.V. Bertin Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more René J.V. Bertin Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more René J.V. Bertin Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more René J.V. Bertin Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more René J.V. Bertin Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more René J.V. Bertin Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more René J.V. Bertin Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more René J.V. Bertin Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more René J.V. Bertin qtcurve update failure René J.V. Bertin qtcurve update failure René J.V. Bertin qtcurve update failure René J.V. Bertin qtcurve update failure René J.V. Bertin qtcurve update failure René J.V. Bertin interrupting rev-upgrade with v2.3.5 or a post-v2.3.5 master René J.V. Bertin interrupting rev-upgrade with v2.3.5 or a post-v2.3.5 master René J.V. Bertin interrupting rev-upgrade with v2.3.5 or a post-v2.3.5 master René J.V. Bertin interesting ruby build issue René J.V. Bertin py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup René J.V. Bertin py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup René J.V. Bertin py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup René J.V. Bertin py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup René J.V. Bertin py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup René J.V. Bertin uncompressed .tar distfiles René J.V. Bertin uncompressed .tar distfiles René J.V. Bertin tuning the behaviour of the -u option? René J.V. Bertin [macports-ports] branch master updated: fluid-soundfont, generaluser-soundfont: new ports René J.V. Bertin tuning the behaviour of the -u option? René J.V. Bertin [macports-ports] branch master updated: fluid-soundfont, generaluser-soundfont: new ports René J.V. Bertin tuning the behaviour of the -u option? René J.V. Bertin port:libressl vs port:openssl, path-style variants and prebuilt binaries René J.V. Bertin port:libressl vs port:openssl, path-style variants and prebuilt binaries René J.V. Bertin PR final steps (to squash or not to squash) Eric A. Borisch PR final steps (to squash or not to squash) Eric A. Borisch Best practice for port contributors in github world Luc Bourhis Best practice for port contributors in github world Luc Bourhis Update mono, F#: support "select" Luc Bourhis Update mono, F#: support "select" Luc Bourhis Update mono, F#: support "select" Luc Bourhis octave: make distributable Marcus Calhoun-Lopez rsync server out of date? Marcus Calhoun-Lopez ports using scons build system Ken Cunningham ports using scons build system Ken Cunningham port requires c++1y -> use cxx11 portgroup? Ken Cunningham [macports-ports] branch master updated: pingus: new port submission Ken Cunningham port requires c++1y -> use cxx11 portgroup? Ken Cunningham port requires c++1y -> use cxx11 portgroup? Ken Cunningham review request - glbinding - new C++ bindings for OpenGL Ken Cunningham review request - cpplocate - used by glbinding example apps Ken Cunningham installing an older version of a port in the github era Ken Cunningham installing an older version of a port in the github era -- an answer Ken Cunningham installing an older version of a port in the github era -- an answer Ken Cunningham Unintentional double commits Andrea D'Amore xonsh-devel broken Andrea D'Amore Requiring a specific variant in depends_lib Akim Demaille [MacPorts] #53049: gqrx dependency missing Michael Dickens `port edit`, local/console vs. remote use Bradley Giesbrecht macports-user repos Bradley Giesbrecht Thanks Thomas de Grivel [macports-ports] branch master updated: grass: jump to 7.2RC2 (dubbed 7.1.99.2) Vincent Habchi Packaging an app Vincent Habchi Guidelines about trac tickets and pull requests Arno Hautala Criteria for picking compilers from fallback list ? Chris Jones Criteria for picking compilers from fallback list ? Christopher Jones Criteria for picking compilers from fallback list ? Christopher Jones Update mono, F#: support "select" Russell Jones Some Homebrew commands send data to Google Analytics vs. port mpstats Russell Jones Fwd: Your message to macports-changes awaits moderator approval Zero King Your message to macports-changes awaits moderator approval Zero King PR final steps (to squash or not to squash) Zero King Unintentional double commits Zero King Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Marko Käning Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Marko Käning Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Marko Käning Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Marko Käning Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Marko Käning [macports-ports] branch master updated: phonon-backend-gstreamer(-qt5): update to 4.9.0 and introduce new subport Marko Käning [macports-ports] branch master updated: phonon-backend-gstreamer(-qt5): update to 4.9.0 and introduce new subport Marko Käning Feature Request: Buildbot triggering dependent port rebuilds in a cascade Marko Käning py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup Marko Käning py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup Marko Käning Unintentional double commits Marko Käning xonsh-devel broken Marko Käning xonsh-devel broken Marko Käning KDE4 ports not built on Sierra buildbot? Marko Käning KDE4 ports not built on Sierra buildbot? Marko Käning Central portindex'ing functional at the moment? Marko Käning Central portindex'ing functional at the moment? Marko Käning Central portindex'ing functional at the moment? Marko Käning Central portindex'ing functional at the moment? Marko Käning Central portindex'ing functional at the moment? Marko Käning [RJVB/macstrop] use github ID for maintainer (2fb8aab) Clemens Lang `port edit`, local/console vs. remote use Clemens Lang `port edit`, local/console vs. remote use Clemens Lang Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Clemens Lang Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Clemens Lang Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Clemens Lang Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Clemens Lang Some Homebrew commands send data to Google Analytics vs. port mpstats Clemens Lang tuning the behaviour of the -u option? Clemens Lang Report from the Reproducible Builds World Summit 2016 Clemens Lang Command line switch to say yes to dependencies? Clemens Lang rsync server out of date? Clemens Lang Unintentional double commits Ivan Larionov Unintentional double commits Ivan Larionov `port edit`, local/console vs. remote use Jeremy Lavergne tk not building on 10.6.8: #ifdef question in ticket 52090 Davide Liessi Unintentional double commits Davide Liessi SSL Issues and PortGroup GitHub Daniel J. Luke SSL Issues and PortGroup GitHub Daniel J. Luke xonsh-devel broken Daniel J. Luke xonsh-devel broken Daniel J. Luke Your message to macports-changes awaits moderator approval Mojca Miklavec Your message to macports-changes awaits moderator approval Mojca Miklavec Your message to macports-changes awaits moderator approval Mojca Miklavec PR final steps (to squash or not to squash) Mojca Miklavec PR final steps (to squash or not to squash) Mojca Miklavec Question about bootstrapping MinGW Mojca Miklavec Question about bootstrapping MinGW Mojca Miklavec Question about bootstrapping MinGW Mojca Miklavec Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Mojca Miklavec Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Mojca Miklavec Tickets affecting multiple ports and committers & "annoying" commits Mojca Miklavec Commits that implicitly close PRs do not remember doing so Mojca Miklavec Feature Request: Buildbot triggering dependent port rebuilds in a cascade Mojca Miklavec qtcurve update failure Mojca Miklavec qtcurve update failure Mojca Miklavec qtcurve update failure Mojca Miklavec Update mono, F#: support "select" Mojca Miklavec Update mono, F#: support "select" Mojca Miklavec Update mono, F#: support "select" Mojca Miklavec Requiring a specific variant in depends_lib Mojca Miklavec Tickets affecting multiple ports and committers & "annoying" commits Mojca Miklavec Unintentional double commits Mojca Miklavec A new category of ports: purgatory Mojca Miklavec Unintentional double commits Mojca Miklavec Unintentional double commits Mojca Miklavec Unintentional double commits Mojca Miklavec KDE4 ports not built on Sierra buildbot? Mojca Miklavec KDE4 ports not built on Sierra buildbot? Mojca Miklavec Template for pull requests Mojca Miklavec Mirorring distfiles or enabling libcurl/openssl from MP Mojca Miklavec How to properly add -stdlib=... (and other flags)? Mojca Miklavec Mirorring distfiles or enabling libcurl/openssl from MP Mojca Miklavec [macports-ports] branch master updated: grass: jump to 7.2RC2 (dubbed 7.1.99.2) Mojca Miklavec Central portindex'ing functional at the moment? Mojca Miklavec Central portindex'ing functional at the moment? Mojca Miklavec Guidelines about trac tickets and pull requests Mojca Miklavec Best way to fetch/extract sources of a dependency Mojca Miklavec Guidelines about trac tickets and pull requests Mojca Miklavec Guidelines about trac tickets and pull requests Mojca Miklavec port:libressl vs port:openssl, path-style variants and prebuilt binaries Mojca Miklavec Your message to macports-changes awaits moderator approval Rainer Müller [RJVB/macstrop] use github ID for maintainer (2fb8aab) Rainer Müller [RJVB/macstrop] use github ID for maintainer (2fb8aab) Rainer Müller Your message to macports-changes awaits moderator approval Rainer Müller Your message to macports-changes awaits moderator approval Rainer Müller Request for review and/or commit of #52730 Rainer Müller PR final steps (to squash or not to squash) Rainer Müller PR final steps (to squash or not to squash) Rainer Müller PR final steps (to squash or not to squash) Rainer Müller PR final steps (to squash or not to squash) Rainer Müller PR final steps (to squash or not to squash) Rainer Müller `port edit`, local/console vs. remote use Rainer Müller `port edit`, local/console vs. remote use Rainer Müller `port edit`, local/console vs. remote use Rainer Müller `port edit`, local/console vs. remote use Rainer Müller Branching for 2.4 Rainer Müller Commits that implicitly close PRs do not remember doing so Rainer Müller Update mono, F#: support "select" Rainer Müller Branching for 2.4 Rainer Müller Branching for 2.4 Rainer Müller [macports-ports] branch master updated: hidapi-devel: new port, version 0.8.0-20160920 Rainer Müller Unintentional double commits Rainer Müller Build Failure: cctools, libmacho, libmacho-headers Rainer Müller Unintentional double commits Rainer Müller macports-user repos Rainer Müller Mirorring distfiles or enabling libcurl/openssl from MP Rainer Müller Mirorring distfiles or enabling libcurl/openssl from MP Rainer Müller Best way to fetch/extract sources of a dependency Rainer Müller declaring variants/subports in loops and loop variables Gustaf Neumann SSL Issues and PortGroup GitHub John Patrick SSL Issues and PortGroup GitHub John Patrick SSL Issues and PortGroup GitHub John Patrick Guidelines about trac tickets and pull requests John Patrick [macports-ports] 01/01: Merge branch 'seqan_update' John Patrick Tcl list-related 2.3.4 -> 2.3.5 changes? Joshua Root PR final steps (to squash or not to squash) Joshua Root PR final steps (to squash or not to squash) Joshua Root declaring variants/subports in loops and loop variables Joshua Root declaring variants/subports in loops and loop variables Joshua Root Criteria for picking compilers from fallback list ? Joshua Root declaring variants/subports in loops and loop variables Joshua Root Branching for 2.4 Joshua Root Branching for 2.4 Joshua Root Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more Joshua Root Commits that implicitly close PRs do not remember doing so Joshua Root Best practice for port contributors in github world Joshua Root interrupting rev-upgrade with v2.3.5 or a post-v2.3.5 master Joshua Root Best practice for port contributors in github world Joshua Root interrupting rev-upgrade with v2.3.5 or a post-v2.3.5 master Joshua Root Branching for 2.4 Joshua Root Some Homebrew commands send data to Google Analytics vs. port mpstats Joshua Root Branching for 2.4 Joshua Root py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup Joshua Root py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup Joshua Root py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup Joshua Root py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup Joshua Root py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup Joshua Root py-pyqt4: fix for the depends_lib reset caused by the Python PortGroup Joshua Root SSL Issues and PortGroup GitHub Joshua Root xonsh-devel broken Joshua Root octave: make distributable Joshua Root How to properly add -stdlib=... (and other flags)? Joshua Root installing an older version of a port in the github era -- an answer Joshua Root Command line switch to say yes to dependencies? Joshua Root ports using scons build system Ryan Schmidt [macports-contrib] branch master updated: portfile-gen: update python versions Ryan Schmidt Your message to macports-changes awaits moderator approval Ryan Schmidt How should ports refer to the 2-clause BSD license? Ryan Schmidt How should ports refer to the 2-clause BSD license? Ryan Schmidt [macports-ports] branch master updated: Add myself back as maintainer - I was incorrectly removed in 2007 and just noticed. Ryan Schmidt `port edit`, local/console vs. remote use Ryan Schmidt declaring variants/subports in loops and loop variables Ryan Schmidt declaring variants/subports in loops and loop variables Ryan Schmidt Criteria for picking compilers from fallback list ? Ryan Schmidt Feature Request: Buildbot triggering dependent port rebuilds in a cascade Ryan Schmidt Commits that implicitly close PRs do not remember doing so Ryan Schmidt Build Failure: gstreamer1-gst-plugins-bad, mesa, x265 Ryan Schmidt [MacPorts] #53049: gqrx dependency missing Ryan Schmidt SSL Issues and PortGroup GitHub Ryan Schmidt Requiring a specific variant in depends_lib Ryan Schmidt SSL Issues and PortGroup GitHub Ryan Schmidt uncompressed .tar distfiles Ryan Schmidt Tickets affecting multiple ports and committers & "annoying" commits Ryan Schmidt [macports-ports] branch master updated: hidapi-devel: new port, version 0.8.0-20160920 Ryan Schmidt [macports-ports] 02/03: python34: backport patch from #44288. Part of #51939. Maintainer timeout. Ryan Schmidt [macports-ports] branch master updated: grass: jump to 7.2RC2 (dubbed 7.1.99.2) Ryan Schmidt Unintentional double commits Ryan Schmidt [macports-ports] branch master updated: ocaml-zarith: update to 1.4.1 Ryan Schmidt KDE4 ports not built on Sierra buildbot? Ryan Schmidt [macports-ports] branch master updated: ds9: update to 7.5 Ryan Schmidt [macports-ports] branch master updated: fluid-soundfont, generaluser-soundfont: new ports Ryan Schmidt [macports-ports] branch master updated: grass7: add more patches (__unix__ -> __APPLE__) Ryan Schmidt [macports-ports] branch master updated: fluid-soundfont, generaluser-soundfont: new ports Ryan Schmidt [macports-ports] branch master updated: fluid-soundfont, generaluser-soundfont: new ports Ryan Schmidt [macports-ports] branch master updated: gdal-grass: bump to 2.1.0 Ryan Schmidt Guidelines about trac tickets and pull requests Ryan Schmidt rsync server out of date? Ryan Schmidt rsync server out of date? Ryan Schmidt Criteria for picking compilers from fallback list ? Jeremy Huddleston Sequoia Criteria for picking compilers from fallback list ? Jeremy Huddleston Sequoia Build Failure: cctools, libmacho, libmacho-headers Jeremy Huddleston Sequoia Command line switch to say yes to dependencies? Sterling Smith [MacPorts] #53049: gqrx dependency missing Wilhelm Speck mogenerator update [ticket 53019] review request Aljaž 'g5pw' Srebrnič Review or Commit of #52814 scala2.12 David Strawn mogenerator update [ticket 53019] review request Steven Tondeur Packaging an app Craig Treleaven Packaging an app Craig Treleaven ports using scons build system Lawrence Velázquez Tcl list-related 2.3.4 -> 2.3.5 changes? Lawrence Velázquez [macports-ports] branch master updated: pingus: new port submission Lawrence Velázquez port requires c++1y -> use cxx11 portgroup? Lawrence Velázquez port requires c++1y -> use cxx11 portgroup? Lawrence Velázquez [macports-ports] branch master updated: sqlite3: revert to editline Lawrence Velázquez How should ports refer to the 2-clause BSD license? Lawrence Velázquez How should ports refer to the 2-clause BSD license? Lawrence Velázquez PR final steps (to squash or not to squash) Lawrence Velázquez PR final steps (to squash or not to squash) Lawrence Velázquez PR final steps (to squash or not to squash) Lawrence Velázquez PR final steps (to squash or not to squash) Lawrence Velázquez PR final steps (to squash or not to squash) Lawrence Velázquez Commits that implicitly close PRs do not remember doing so Lawrence Velázquez [macports-ports] branch master updated: phonon-backend-gstreamer(-qt5): update to 4.9.0 and introduce new subport Lawrence Velázquez [macports-ports] branch master updated: phonon-backend-gstreamer(-qt5): update to 4.9.0 and introduce new subport Lawrence Velázquez Best practice for port contributors in github world Lawrence Velázquez Central portindex'ing functional at the moment? Fred Wright installing an older version of a port in the github era -- an answer Fred Wright installing an older version of a port in the github era -- an answer Fred Wright Command line switch to say yes to dependencies? mf2k at macports.org [macports-ports] 01/01: Merge branch 'seqan_update' mf2k at macports.org Last message date: Sat Dec 31 20:08:23 CET 2016 Archived on: Sat Dec 31 20:08:27 CET 2016 Messages sorted by: [ thread ] [ subject ] [ date ] More info on this list... This archive was generated by Pipermail 0.09 (Mailman edition). | 2026-01-13T09:30:25 |
https://rubygems.org/gems/erubi | erubi | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up erubi 1.13.1 Erubi is a ERB template engine for ruby. It is a simplified fork of Erubis Gemfile: = install: = Versions: 1.13.1 December 19, 2024 (13 KB) 1.13.0 June 13, 2024 (13 KB) 1.12.0 December 22, 2022 (12 KB) 1.11.0 August 02, 2022 (12 KB) 1.10.0 November 13, 2020 (11 KB) Show all versions (18 total) Development Dependencies (2): minitest >= 0 minitest-global_expectations >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans, kuwata-lab.com SHA 256 checksum: = ← Previous version Total downloads 543,428,404 For this version 74,199,438 Version Released: December 19, 2024 5:12pm License: MIT Required Ruby Version: >= 0 Links: Homepage Changelog Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
http://www.rubytapas.com/ | RubyTapas Home About News Subscribe Personal Subscriptions Team Pricing Episodes All Episodes Freebies Guest Episodes Categories APIs and Libraries Applications Design Language Patterns and Anti-Patterns Style Testing Tools Surprise me! Video Downloads Courses Tasting Menus Feasts Help FAQ Contact Nominate a Guest Chef Privacy Log in Twitter Facebook Search for: Search Categories Categories Select Category Announcements APIs and Libraries Applications Behind the Scenes BRUNCH Career Community Design Episodes Premium Episodes Season 1 S1 Premium Season 2 S2 Premium Season 3 S3 Premium Season 4 S4 Premium Season 5 S5 Premium Season 6 S6 Premium Season 7 S7 Premium Season 8 S8 Premium Season 9 S9 Premium Freebies Guest Episodes Kitchen Tour Language News Practices Sideboard Style Testing Tools Uncategorized Tags activerecord asynchrony code smells command line concurrency containers corelib data database debugging devcontainers domain modeling Enumerable & Enumerator failure handling files guest idioms Input - Output iteration linux literals logging metaprogramming oop patterns practices processes (execution) rails refactoring regex rspec RubyGems stdlib strings syntax systems tdd test doubles testing text threads tools unix value objects variables January 2026 M T W T F S S 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 « Sep Archives Archives Select Month September 2021 August 2021 July 2021 June 2021 May 2021 April 2021 March 2021 February 2021 January 2021 December 2020 November 2020 October 2020 September 2020 August 2020 July 2020 June 2020 May 2020 April 2020 March 2020 February 2020 January 2020 December 2019 November 2019 October 2019 September 2019 August 2019 July 2019 June 2019 May 2019 April 2019 March 2019 February 2019 January 2019 December 2018 November 2018 October 2018 September 2018 August 2018 July 2018 June 2018 May 2018 April 2018 March 2018 February 2018 January 2018 December 2017 November 2017 October 2017 September 2017 August 2017 July 2017 June 2017 May 2017 April 2017 March 2017 February 2017 January 2017 December 2016 November 2016 October 2016 September 2016 August 2016 July 2016 June 2016 May 2016 April 2016 March 2016 February 2016 January 2016 December 2015 November 2015 October 2015 September 2015 August 2015 July 2015 June 2015 May 2015 April 2015 March 2015 February 2015 January 2015 December 2014 November 2014 October 2014 September 2014 August 2014 July 2014 June 2014 May 2014 April 2014 March 2014 February 2014 January 2014 December 2013 November 2013 October 2013 September 2013 August 2013 July 2013 June 2013 May 2013 April 2013 March 2013 February 2013 January 2013 December 2012 November 2012 October 2012 September 2012 Meta Log in Entries feed Comments feed WordPress.org Categories All Language Design Style APIs and Libraries Testing Freebies Let's Eat Twitter Facebook Recent Episodes RubyTapas Short Screencasts of Gourmet Ruby, by Avdi Grimm Home About News Subscribe Personal Subscriptions Team Pricing Episodes All Episodes Freebies Guest Episodes Categories APIs and Libraries Applications Design Language Patterns and Anti-Patterns Style Testing Tools Surprise me! Video Downloads Courses Tasting Menus Feasts Help FAQ Contact Nominate a Guest Chef Privacy Log in RubyTapas is getting Graceful Avdi Grimm September 17, 2021 We've had dinner, now it's time for the dancing! Read More Episode #683 Tap Avdi Grimm August 22, 2021 Let's talk about Ruby's `.tap` method. How does it differ from related combinators? When should we use it? And... why is it called "tap", anyway? Read More Episode #682 682 Is it defined? Avdi Grimm August 11, 2021 Constants, globals, locals, instance variables, methods... Ruby has a lot of namespaces. Let's learn about a Ruby power tool for reflecting on these names no matter what space they come … Read More Episode #681 Setter Return Avdi Grimm August 2, 2021 A surprising Rubocop warning inspired this video about an obscure bit of Ruby semantics. Find out why you never need to worry about return values in Ruby setter methods! Read More Episode #680 Hash Splat Merge Avdi Grimm July 24, 2021 In today's video, learn a concise and expressive syntax for merging several Ruby hashes into one! Read More Episode #679 Git Hooks for Evil and Good Avdi Grimm July 11, 2021 Between your beautiful code change and immortality stands a gatekeeper: git commit hooks. These hooks can be helpful... or annoying. Join Jessica Kerr to learn how to make the former, … Read More Episode #678 Module Prepend Avdi Grimm June 28, 2021 Sometimes you need to attach new functionality, such as logging, to other people's code. Learn to leverage Ruby's ancestor chain for (relatively) clean patching, using prepended modules! Read More Episode #677 Direnv and Dotenv Avdi Grimm June 21, 2021 direnv and dotenv: both utilities for managing 12-Factor-style environment-based configuration. Where do they overlap, how do they differ, and, most importantly: how can they complement each other? Find out! Read More Episode #676 Distributed Tracing with Honeycomb Jessica Kerr June 14, 2021 Service-oriented architecture may enable separate teams to work fast independently, but they also push problems into the interstices between systems. Distributed bugs need distributed tracing - learn how, with Jessica … Read More 1 2 3 … 85 → Categories All Language Design Style APIs and Libraries Testing Freebies Home About Subscribe Episodes Courses Help Log in © 2021 ShipRise LLC | 2026-01-13T09:30:25 |
https://rubygems.org/gems/sequel_pg | sequel_pg | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up sequel_pg 1.18.2 sequel_pg overwrites the inner loop of the Sequel postgres adapter row fetching code with a C version. The C version is significantly faster than the pure ruby version that Sequel uses by default. sequel_pg also offers optimized versions of some dataset methods, as well as adds support for using PostgreSQL streaming. Gemfile: = install: = Versions: 1.18.2 December 18, 2025 (27.5 KB) 1.18.1 December 16, 2025 (27.5 KB) 1.18.0 December 01, 2025 (27.5 KB) 1.17.2 March 14, 2025 (26 KB) 1.17.1 January 04, 2023 (26 KB) Show all versions (92 total) Runtime Dependencies (2): pg >= 0.18.0, != 1.2.0 sequel >= 4.38.0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 6,533,035 For this version 10,307 Version Released: December 18, 2025 7:01pm License: MIT Required Ruby Version: >= 1.9.3 Links: Homepage Changelog Source Code Documentation Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/project/local-development/ | Local Development | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Development Local Development 3.0 3.0 2.5 Edit this Page Local Development Project is fully handled using Gradle . That includes from dependency management, to building, testing and releasing. While IDE integration is the most common workflow, all tasks can be run using the gradlew command (i.e., the Gradle Wrapper). We strongly recommend that you use Gradle via the Gradle daemon . Build the artifacts To clone the project, compile the source and build the artifacts (i.e., jars) locally, run: $ git clone https://github.com/asciidoctor/asciidoctorj $ cd asciidoctorj $ ./gradlew assemble Then, you can find the built artifacts in the asciidoctorj-*/build/libs folders. Test To execute tests when running the build, use: $ ./gradlew build To only execute the tests, run: $ ./gradlew check You can also run tests for a single module: $ cd asciidoctorj-core ../gradlew check To run a single test in the asciidoctorj-core subproject, use: $ ../gradlew -Dsingle.test=NameOfTestClass test Create distribution To create the distribution containing all files, run: $ ./gradlew distZip You can find the distribution in the asciidoctorj-distribution/build/distributions folder. Locally install the artifacts If you need to install the artifacts in local Maven repository, for example to be used as dependency for another project. $ ./gradlew publishToMavenLocal Artifacts will be at ~/.m2/repository/org/asciidoctor/asciidoctorj . Project Layout Develop in an IDE Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://stdapi.ai/operations_configuration/ | Configuration - stdapi.ai Skip to content stdapi.ai Configuration Initializing search stdapi-ai/stdapi.ai Home Documentation API Reference stdapi.ai stdapi-ai/stdapi.ai Home Documentation Documentation API API Overview OpenAI Compatible Operations Operations Getting started Configuration Configuration Table of contents Quick Start Minimal Production Setup Production with Authentication Full Production Setup (All Features Enabled) Development Setup Environment Variable Summary Essential (Production) AWS Storage AWS AI Services Bedrock Advanced Authentication OpenAI Compatibility Logging Observability (OpenTelemetry) HTTP/Security Application Behavior API Documentation AWS Services and Regions Storage Configuration AWS_S3_BUCKET AWS_S3_ACCELERATE AWS_S3_TMP_PREFIX AWS_TRANSCRIBE_S3_BUCKET AWS_S3_REGIONAL_BUCKETS S3 Bucket Lifecycle Configuration Bedrock Configuration AWS_BEDROCK_REGIONS AWS_BEDROCK_CROSS_REGION_INFERENCE AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL AWS_BEDROCK_LEGACY AWS_BEDROCK_MARKETPLACE_AUTO_SUBSCRIBE AWS_BEDROCK_ALLOW_CROSS_REGION_INFERENCE_PROFILE_ARN AWS_BEDROCK_ALLOW_APPLICATION_INFERENCE_PROFILE_ARN AWS_BEDROCK_ALLOW_PROMPT_ROUTER_ARN AWS_BEDROCK_MODEL_ARN_MAPPING Other AWS Services AWS_POLLY_REGION AWS_COMPREHEND_REGION AWS_TRANSCRIBE_REGION AWS_TRANSLATE_REGION Compliance and Latency Optimization GDPR and Data Residency Compliance Latency Optimization Hybrid Approach: Compliance with Performance Configuration Order IAM Permissions Bedrock (Required) Bedrock Marketplace Auto-Subscribe (Optional) Bedrock Inference Profiles and Prompt Routers (Optional) Bedrock Guardrails (Optional) S3 File Storage (Optional) Text-to-Speech (Optional) Speech-to-Text (Optional) Language Detection (Optional) Text Translation (Optional) API Key Authentication (Optional) SSM Parameter Store Secrets Manager Complete Policy Examples Permission Notes Feature-Specific Permission Requirements IAM Role vs. IAM User Authentication Method 1: SSM Parameter Store (Recommended) API_KEY_SSM_PARAMETER Method 2: Secrets Manager API_KEY_SECRETSMANAGER_SECRET API_KEY_SECRETSMANAGER_KEY Method 3: Direct API Key API_KEY OpenAI API Compatibility OPENAI_ROUTES_PREFIX CORS Configuration CORS_ALLOW_ORIGINS Trusted Host Configuration TRUSTED_HOSTS Proxy Headers Configuration ENABLE_PROXY_HEADERS GZip Compression ENABLE_GZIP SSRF Protection SSRF_PROTECTION_BLOCK_PRIVATE_NETWORKS Observability (OpenTelemetry) OTEL_ENABLED OTEL_SERVICE_NAME OTEL_EXPORTER_ENDPOINT OTEL_SAMPLE_RATE API Documentation Routes ENABLE_DOCS ENABLE_REDOC ENABLE_OPENAPI_JSON Development Configuration Production Best Practice Validation and Logging Logging Level LOG_LEVEL Client IP Logging LOG_CLIENT_IP Bedrock Guardrails Global Configuration AWS_BEDROCK_GUARDRAIL_IDENTIFIER AWS_BEDROCK_GUARDRAIL_VERSION AWS_BEDROCK_GUARDRAIL_TRACE AWS_BEDROCK_ALLOW_GUARDRAIL_OVERRIDE Per-Request Configuration Request Body Configuration Bedrock Service Tier and Performance Configuration Service Tiers Performance Configuration Per-Request Configuration Audio and Text-to-Speech DEFAULT_TTS_MODEL Token Counting TOKENS_ESTIMATION TOKENS_ESTIMATION_DEFAULT_ENCODING Model Cache MODEL_CACHE_SECONDS Default Model Parameters DEFAULT_MODEL_PARAMS Configuration Examples Parameter Merging Using Inference Profile and Prompt Router ARNs Overview Enabling ARN Support Using ARNs in API Requests Use Case Comparison Best Practices Required IAM Permissions Licensing Logging & Monitoring Use cases Use cases Overview OpenWebUI integration N8N integration IDE integration (Continue.dev & others) LibreChat integration LangChain / LlamaIndex integration Note-taking apps (Obsidian & Notion) Chat bots (Slack, Discord & Teams) Autonomous agents (AutoGPT & more) Roadmap & Changelog API Reference Table of contents Quick Start Minimal Production Setup Production with Authentication Full Production Setup (All Features Enabled) Development Setup Environment Variable Summary Essential (Production) AWS Storage AWS AI Services Bedrock Advanced Authentication OpenAI Compatibility Logging Observability (OpenTelemetry) HTTP/Security Application Behavior API Documentation AWS Services and Regions Storage Configuration AWS_S3_BUCKET AWS_S3_ACCELERATE AWS_S3_TMP_PREFIX AWS_TRANSCRIBE_S3_BUCKET AWS_S3_REGIONAL_BUCKETS S3 Bucket Lifecycle Configuration Bedrock Configuration AWS_BEDROCK_REGIONS AWS_BEDROCK_CROSS_REGION_INFERENCE AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL AWS_BEDROCK_LEGACY AWS_BEDROCK_MARKETPLACE_AUTO_SUBSCRIBE AWS_BEDROCK_ALLOW_CROSS_REGION_INFERENCE_PROFILE_ARN AWS_BEDROCK_ALLOW_APPLICATION_INFERENCE_PROFILE_ARN AWS_BEDROCK_ALLOW_PROMPT_ROUTER_ARN AWS_BEDROCK_MODEL_ARN_MAPPING Other AWS Services AWS_POLLY_REGION AWS_COMPREHEND_REGION AWS_TRANSCRIBE_REGION AWS_TRANSLATE_REGION Compliance and Latency Optimization GDPR and Data Residency Compliance Latency Optimization Hybrid Approach: Compliance with Performance Configuration Order IAM Permissions Bedrock (Required) Bedrock Marketplace Auto-Subscribe (Optional) Bedrock Inference Profiles and Prompt Routers (Optional) Bedrock Guardrails (Optional) S3 File Storage (Optional) Text-to-Speech (Optional) Speech-to-Text (Optional) Language Detection (Optional) Text Translation (Optional) API Key Authentication (Optional) SSM Parameter Store Secrets Manager Complete Policy Examples Permission Notes Feature-Specific Permission Requirements IAM Role vs. IAM User Authentication Method 1: SSM Parameter Store (Recommended) API_KEY_SSM_PARAMETER Method 2: Secrets Manager API_KEY_SECRETSMANAGER_SECRET API_KEY_SECRETSMANAGER_KEY Method 3: Direct API Key API_KEY OpenAI API Compatibility OPENAI_ROUTES_PREFIX CORS Configuration CORS_ALLOW_ORIGINS Trusted Host Configuration TRUSTED_HOSTS Proxy Headers Configuration ENABLE_PROXY_HEADERS GZip Compression ENABLE_GZIP SSRF Protection SSRF_PROTECTION_BLOCK_PRIVATE_NETWORKS Observability (OpenTelemetry) OTEL_ENABLED OTEL_SERVICE_NAME OTEL_EXPORTER_ENDPOINT OTEL_SAMPLE_RATE API Documentation Routes ENABLE_DOCS ENABLE_REDOC ENABLE_OPENAPI_JSON Development Configuration Production Best Practice Validation and Logging Logging Level LOG_LEVEL Client IP Logging LOG_CLIENT_IP Bedrock Guardrails Global Configuration AWS_BEDROCK_GUARDRAIL_IDENTIFIER AWS_BEDROCK_GUARDRAIL_VERSION AWS_BEDROCK_GUARDRAIL_TRACE AWS_BEDROCK_ALLOW_GUARDRAIL_OVERRIDE Per-Request Configuration Request Body Configuration Bedrock Service Tier and Performance Configuration Service Tiers Performance Configuration Per-Request Configuration Audio and Text-to-Speech DEFAULT_TTS_MODEL Token Counting TOKENS_ESTIMATION TOKENS_ESTIMATION_DEFAULT_ENCODING Model Cache MODEL_CACHE_SECONDS Default Model Parameters DEFAULT_MODEL_PARAMS Configuration Examples Parameter Merging Using Inference Profile and Prompt Router ARNs Overview Enabling ARN Support Using ARNs in API Requests Use Case Comparison Best Practices Required IAM Permissions Home Documentation Operations Configuration Guide ¶ stdapi.ai is configured entirely through environment variables, which are read once at startup and cannot be changed without restarting the service. This guide explains each setting category with practical examples to help you configure the service correctly. Zero Configuration Startup stdapi.ai works out of the box with zero configuration. The service automatically detects your current AWS region and discovers available Bedrock models. Prerequisites Before configuring stdapi.ai, ensure you have: AWS Account with access to Amazon Bedrock AWS Credentials configured via environment variables, AWS CLI, or IAM role (for EC2/ECS/Lambda deployments) IAM Permissions to access required AWS services (see IAM Permissions section) S3 Bucket (optional, but recommended for production use with file operations) Container Runtime Both the AWS Marketplace and community Docker images run using Granian , a high-performance Python ASGI server. In addition to the stdapi.ai-specific configuration variables documented below, you can also use Granian environment variables to configure the server runtime (e.g., GRANIAN_PORT , GRANIAN_WORKERS , GRANIAN_THREADS , etc.). Quick Start ¶ For production deployments, configure these essential settings: Minimal Production Setup ¶ Single-region deployment with file storage only. # S3 bucket for file storage (must be in same region as your server) export AWS_S3_BUCKET = my-stdapi-bucket # AWS_BEDROCK_REGIONS is optional - will auto-detect your current AWS region if not specified Production with Authentication ¶ Adds secure API key authentication via AWS Systems Manager. # S3 bucket for file storage (must be in same region as your server) export AWS_S3_BUCKET = my-stdapi-bucket # Secure API authentication (recommended: SSM Parameter Store) export API_KEY_SSM_PARAMETER = /stdapi/prod/api-key # AWS_BEDROCK_REGIONS is optional - will auto-detect your current AWS region if not specified Full Production Setup (All Features Enabled) ¶ Multi-region deployment with all AWS AI services, observability, and security features. # Core AWS configuration - host server in first region export AWS_BEDROCK_REGIONS = us-east-1,us-west-2,eu-west-1 # S3 bucket for file storage (must be in us-east-1, your first/primary region) export AWS_S3_BUCKET = my-stdapi-us-east-1-bucket # Optional: Transcribe S3 bucket (defaults to AWS_S3_BUCKET if not specified) # Only set this if you need a separate bucket or if transcribe is in a different region # export AWS_TRANSCRIBE_S3_BUCKET=my-stdapi-transcribe-us-east-1 # Optional: Regional buckets for async/batch inference in other regions export AWS_S3_REGIONAL_BUCKETS = '{"us-west-2": "my-stdapi-us-west-2-bucket", "eu-west-1": "my-stdapi-eu-west-1-bucket"}' # AWS AI services regions (optional - defaults to first AWS_BEDROCK_REGIONS if not specified) export AWS_POLLY_REGION = us-east-1 # Text-to-speech export AWS_TRANSCRIBE_REGION = us-east-1 # Speech-to-text (audio transcription) export AWS_COMPREHEND_REGION = us-east-1 # Language detection export AWS_TRANSLATE_REGION = us-east-1 # Text translation # Authentication export API_KEY_SSM_PARAMETER = /stdapi/prod/api-key # Logging export LOG_LEVEL = warning export LOG_CLIENT_IP = true # Optional: OpenTelemetry observability (AWS X-Ray integration) # export OTEL_ENABLED=true # export OTEL_SERVICE_NAME=stdapi-production # export OTEL_SAMPLE_RATE=0.1 # Production security settings (when behind AWS ALB/CloudFront) export ENABLE_PROXY_HEADERS = true # Note: TRUSTED_HOSTS not recommended with AWS ALB - use ALB host-based routing instead # Only use TRUSTED_HOSTS if you cannot configure host validation at the load balancer level # Optional: CORS for browser-based web applications # export CORS_ALLOW_ORIGINS='["https://app.example.com"]' Development Setup ¶ Local development configuration with API documentation and debug logging enabled. # Minimal configuration for local development export AWS_S3_BUCKET = my-stdapi-dev-bucket # Enable API documentation export ENABLE_DOCS = true export ENABLE_REDOC = true # Full request/response logging for debugging export LOG_LEVEL = info export LOG_REQUEST_PARAMS = true # AWS_BEDROCK_REGIONS is optional - will auto-detect your current AWS region if not specified S3 Bucket Required for Certain Features Without an S3 bucket configured, some features will be disabled (such as image output as URL, audio transcription). See the relevant API documentation for feature requirements. All Other Settings Are Optional The configurations above are sufficient for most production deployments. All other settings can be configured as needed for your specific use case. Environment Variable Summary ¶ This section provides a quick reference of all available configuration options. Detailed explanations for each variable can be found in the sections below. Essential (Production) ¶ Variable Default Description AWS_S3_BUCKET None Primary S3 bucket for file storage; must be in first region of AWS_BEDROCK_REGIONS AWS_BEDROCK_REGIONS Current region Comma-separated regions for Bedrock; first region is where server should be hosted AWS Storage ¶ Variable Default Description AWS_S3_ACCELERATE false Enable S3 Transfer Acceleration for faster global downloads via CloudFront edge locations AWS_S3_REGIONAL_BUCKETS {} Region-specific S3 buckets for Bedrock async/batch inference operations AWS_S3_TMP_PREFIX tmp/ S3 prefix for temporary files used for jobs; configure lifecycle policies on this prefix AWS_TRANSCRIBE_S3_BUCKET AWS_S3_BUCKET S3 bucket for temporary audio transcription files; must be in same region as AWS_TRANSCRIBE_REGION AWS AI Services ¶ Variable Default Description AWS_POLLY_REGION First AWS_BEDROCK_REGIONS AWS region for Amazon Polly text-to-speech service AWS_COMPREHEND_REGION First AWS_BEDROCK_REGIONS AWS region for Amazon Comprehend language detection service AWS_TRANSCRIBE_REGION First AWS_BEDROCK_REGIONS AWS region for Amazon Transcribe speech-to-text service AWS_TRANSLATE_REGION First AWS_BEDROCK_REGIONS AWS region for Amazon Translate text translation service Bedrock Advanced ¶ Variable Default Description AWS_BEDROCK_CROSS_REGION_INFERENCE true Allow automatic model routing to other configured regions AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL true Allow global cross-region inference routing to any region worldwide (disable for GDPR compliance) AWS_BEDROCK_LEGACY true Allow usage of deprecated/legacy Bedrock models AWS_BEDROCK_MARKETPLACE_AUTO_SUBSCRIBE true Allow automatic subscription to new models in AWS Marketplace AWS_BEDROCK_ALLOW_CROSS_REGION_INFERENCE_PROFILE_ARN false Allow users to pass cross-region inference profile ARNs directly as model IDs AWS_BEDROCK_ALLOW_APPLICATION_INFERENCE_PROFILE_ARN false Allow users to pass application inference profile ARNs directly as model IDs AWS_BEDROCK_ALLOW_PROMPT_ROUTER_ARN false Allow users to pass prompt router ARNs directly as model IDs AWS_BEDROCK_MODEL_ARN_MAPPING {} Map model IDs to custom inference profile or prompt router ARNs (server-controlled routing) AWS_BEDROCK_GUARDRAIL_IDENTIFIER None Bedrock Guardrails ID for content filtering and safety controls AWS_BEDROCK_GUARDRAIL_VERSION None Bedrock Guardrails version number (required with identifier) AWS_BEDROCK_GUARDRAIL_TRACE None Guardrails trace level: disabled , enabled , or enabled_full AWS_BEDROCK_ALLOW_GUARDRAIL_OVERRIDE false Allow users to override global guardrail configuration via request headers (security: default off) Authentication ¶ Choose one method (mutually exclusive): Variable Default Description API_KEY_SSM_PARAMETER None AWS Systems Manager Parameter Store path for API key (recommended) API_KEY_SECRETSMANAGER_SECRET None AWS Secrets Manager secret name containing API key API_KEY_SECRETSMANAGER_KEY api_key JSON key name within Secrets Manager secret API_KEY None Direct API key value (not recommended for production) OpenAI Compatibility ¶ Variable Default Description OPENAI_ROUTES_PREFIX Base path prefix for OpenAI-compatible API routes Logging ¶ Variable Default Description LOG_LEVEL info Minimum log severity: info , warning , error , critical , or disabled LOG_REQUEST_PARAMS false Include request/response parameters in logs (not recommended for production) LOG_CLIENT_IP false Log client IP addresses (requires ENABLE_PROXY_HEADERS for real IPs behind proxies) Observability (OpenTelemetry) ¶ Variable Default Description OTEL_ENABLED false Enable distributed tracing via OpenTelemetry (integrates with AWS X-Ray, Jaeger, etc.) OTEL_SERVICE_NAME stdapi Service name identifier in trace visualizations OTEL_EXPORTER_ENDPOINT http://127.0.0.1:4318/v1/traces OTLP HTTP endpoint URL for trace export OTEL_SAMPLE_RATE 1.0 Trace sampling rate from 0.0 (none) to 1.0 (all requests) HTTP/Security ¶ Variable Default Description CORS_ALLOW_ORIGINS None JSON array of allowed origins for browser cross-origin requests TRUSTED_HOSTS None JSON array of trusted Host header values (prefer ALB host-based routing; see details) ENABLE_PROXY_HEADERS false Trust X-Forwarded-* headers from reverse proxies (only enable behind trusted proxy) ENABLE_GZIP false Enable GZip compression for responses >1KB (prefer AWS ALB/CloudFront compression) SSRF_PROTECTION_BLOCK_PRIVATE_NETWORKS true Block requests to private/local networks for SSRF protection Application Behavior ¶ Variable Default Description TIMEZONE UTC IANA timezone identifier for request timestamps STRICT_INPUT_VALIDATION false Reject API requests with unknown/extra fields DEFAULT_TTS_MODEL amazon.polly-standard Default text-to-speech model: standard , neural , long-form , or generative TOKENS_ESTIMATION false Estimate token counts using tiktoken when model doesn't provide them TOKENS_ESTIMATION_DEFAULT_ENCODING o200k_base Tiktoken encoding algorithm: o200k_base (GPT-4o+), cl100k_base (GPT-4), or p50k_base DEFAULT_MODEL_PARAMS {} JSON object with per-model default inference parameters (temperature, max_tokens, etc.) MODEL_CACHE_SECONDS 900 Model list cache lifetime in seconds before lazy refresh (default: 15 minutes) API Documentation ¶ Variable Default Description ENABLE_DOCS false Enable interactive Swagger UI documentation at /docs ENABLE_REDOC false Enable ReDoc documentation UI at /redoc ENABLE_OPENAPI_JSON false Enable OpenAPI schema endpoint at /openapi.json (auto-enabled with docs/redoc) AWS Services and Regions ¶ Storage Configuration ¶ AWS_S3_BUCKET ¶ Purpose : Primary S3 bucket for storing generated files (images, audio, documents) and temporary data during processing Default : None (must be configured for file operations) Best Practice : The bucket must be in the first region specified in AWS_BEDROCK_REGIONS (your primary region where the server should be hosted) to avoid cross-region data transfer costs and reduce latency export AWS_S3_BUCKET = my-llm-storage-us-east-1 Presigned URLs Files are served via presigned URLs for secure, time-limited access. Presigned URLs expire after 1 hour by default. AWS_S3_ACCELERATE ¶ Purpose : Enable S3 Transfer Acceleration for presigned URLs to improve download performance for large files Type : Boolean Default : false Best Practice : Enable when serving large files (high-resolution images, audio) to geographically distributed users export AWS_S3_ACCELERATE = true What is S3 Transfer Acceleration? S3 Transfer Acceleration uses Amazon CloudFront's globally distributed edge locations to accelerate uploads and downloads to S3 buckets. When enabled, data is routed to the nearest edge location and then transferred to S3 over Amazon's optimized network paths. Performance Benefits: Faster downloads for users far from your bucket's region Global reach via CloudFront edge locations Optimized routing over Amazon's private backbone network Consistent performance regardless of user location Typical speed improvements: 50-500% faster for users located far from the bucket region. Requirements Enable Transfer Acceleration on your S3 bucket before setting this option: aws s3api put-bucket-accelerate-configuration \ --bucket my-stdapi-bucket \ --accelerate-configuration Status = Enabled Additional costs : Transfer Acceleration incurs extra data transfer fees. See AWS S3 Transfer Acceleration pricing When to Enable Consider enabling S3 Transfer Acceleration when: Serving generated images via Images API Users are geographically distributed across multiple continents Generating high-resolution images that are large in file size Download performance is critical to user experience For small images or users close to your bucket region, the performance benefit may not justify the additional cost. Current Usage Presigned URLs with Transfer Acceleration are currently only used for the Images API when returning generated images as URLs. AWS_S3_TMP_PREFIX ¶ Purpose : S3 prefix (folder path) for temporary files used during job processing Default : tmp/ Best Practice : Configure S3 lifecycle policies to automatically delete objects under this prefix after 1 day export AWS_S3_TMP_PREFIX = tmp/ What is an S3 Prefix? An S3 prefix is essentially a folder path within your S3 bucket. When you set AWS_S3_TMP_PREFIX=tmp/ , all temporary files are stored under the tmp/ folder structure in your bucket. Example file paths: With prefix tmp/ : s3://my-bucket/tmp/request-id-123/output.json With prefix temporary/ : s3://my-bucket/temporary/request-id-123/output.json With empty prefix `: s3://my-bucket/request-id-123/output.json` (not recommended) Why Use a Prefix? Using a dedicated prefix for temporary files provides several benefits: Easy Lifecycle Management - Apply S3 lifecycle policies to automatically delete only temporary files Better Organization - Keep temporary files separate from permanent storage Security - Apply different IAM policies or bucket policies to the prefix Cost Control - Easily identify and monitor temporary storage costs Trailing Slash Always include a trailing slash ( / ) in your prefix to create a proper folder structure. Without it, files will be stored with the prefix as part of the filename rather than in a folder. ✅ Correct: tmp/ → Files stored as tmp/file.json ❌ Incorrect: tmp → Files stored as tmpfile.json Custom prefix examples: # Production environment export AWS_S3_TMP_PREFIX = prod/tmp/ # Staging environment export AWS_S3_TMP_PREFIX = staging/tmp/ # Organize by date (requires manual updates) export AWS_S3_TMP_PREFIX = tmp/2025/01/ # No prefix (store at bucket root - not recommended) export AWS_S3_TMP_PREFIX = AWS_TRANSCRIBE_S3_BUCKET ¶ Purpose : Temporary S3 bucket for transcription workflows Default : Falls back to AWS_S3_BUCKET if not specified Requirement : Must be in the same region as AWS_TRANSCRIBE_REGION # If AWS_TRANSCRIBE_REGION is us-east-1 export AWS_TRANSCRIBE_S3_BUCKET = my-transcribe-temp-us-east-1 # If AWS_TRANSCRIBE_REGION is eu-west-1 export AWS_TRANSCRIBE_S3_BUCKET = my-transcribe-temp-eu-west-1 AWS_S3_REGIONAL_BUCKETS ¶ Purpose : Region-specific S3 buckets for Bedrock async and batch inference operations Default : Empty (no regional buckets configured) Format : JSON object with region names as keys and bucket names as values Requirement : Some Bedrock models require S3 buckets in the same region for async and batch inference operations export AWS_S3_REGIONAL_BUCKETS = '{"us-east-1": "my-bedrock-temp-us-east-1", "eu-west-1": "my-bedrock-temp-eu-west-1"}' When to Use Configure this setting when: Using Bedrock async inference API Using Bedrock batch inference API Working with models that require regional S3 storage If not specified for a region where async/batch operations are attempted, those operations may fail. Automatic Fallback For the first region in AWS_BEDROCK_REGIONS (your primary region), if no regional bucket is specified, the service automatically falls back to AWS_S3_BUCKET . You only need to configure regional buckets for additional regions beyond your primary one. Best Practice Apply the same S3 Bucket Lifecycle Configuration to these regional buckets as you would for the primary bucket to automatically clean up temporary files. S3 Bucket Lifecycle Configuration ¶ Purpose : Configure automatic deletion of temporary files to minimize storage costs Recommendation : Configure S3 lifecycle policies to automatically delete objects under the AWS_S3_TMP_PREFIX after 1 day stdapi.ai stores temporary files under the prefix configured by AWS_S3_TMP_PREFIX (default: tmp/ ). These include generated images, audio files, and transcription workflow files. Configure S3 lifecycle policies to automatically delete objects under this prefix after 1 day: Application Cleanup Behavior Short-lived temporary files: The application attempts to clean up short-lived temporary files (such as intermediate transcription files) after processing completes. Results shared with clients: Files shared with clients using presigned URLs (such as generated images and audio) are never cleaned up automatically by the application. These files remain in S3 until removed by lifecycle policies or manual deletion. Why lifecycle policies are essential: Since the application cannot determine when a client has finished using a presigned URL, S3 lifecycle policies are the recommended mechanism to clean up these files and prevent unbounded storage growth. { "Rules" : [ { "Id" : "DeleteTemporaryFiles" , "Status" : "Enabled" , "Filter" : { "Prefix" : "tmp/" }, "Expiration" : { "Days" : 1 }, "AbortIncompleteMultipartUpload" : { "DaysAfterInitiation" : 1 } } ] } Important: Update the Prefix The "Prefix": "tmp/" value in the lifecycle policy must match your AWS_S3_TMP_PREFIX setting. If you use a custom prefix, update the policy accordingly. Examples: If AWS_S3_TMP_PREFIX=temporary/ , use "Prefix": "temporary/" If AWS_S3_TMP_PREFIX=prod/tmp/ , use "Prefix": "prod/tmp/" Apply via AWS CLI: # For primary S3 bucket (AWS_S3_BUCKET) aws s3api put-bucket-lifecycle-configuration \ --bucket my-stdapi-bucket \ --lifecycle-configuration file://lifecycle-policy.json # For transcribe S3 bucket (AWS_TRANSCRIBE_S3_BUCKET, if different from AWS_S3_BUCKET) aws s3api put-bucket-lifecycle-configuration \ --bucket my-transcribe-temp-bucket \ --lifecycle-configuration file://lifecycle-policy.json # For regional buckets (AWS_S3_REGIONAL_BUCKETS) aws s3api put-bucket-lifecycle-configuration \ --bucket my-stdapi-us-west-2-bucket \ --lifecycle-configuration file://lifecycle-policy.json Apply to All S3 Buckets Apply this lifecycle policy to: AWS_S3_BUCKET - Primary bucket for generated files AWS_TRANSCRIBE_S3_BUCKET - Transcription temporary files (if different from AWS_S3_BUCKET) AWS_S3_REGIONAL_BUCKETS - All regional buckets for async/batch operations All these buckets use the same AWS_S3_TMP_PREFIX for temporary file storage. Bedrock Configuration ¶ AWS_BEDROCK_REGIONS ¶ Purpose : List of AWS regions where Bedrock models are available Format : Comma-separated string Default : Current AWS SDK region if not specified Behavior : Models are discovered in the same order as the listed regions. The first region is the primary region where your server should be hosted on AWS for optimal performance. Your S3 bucket ( aws_s3_bucket ) must also be in this region. If a model is unavailable in the primary region, subsequent regions are checked in order export AWS_BEDROCK_REGIONS = us-east-1,us-west-2,eu-west-1 Region Selection Guide Region Description us-east-1 Widest model selection, usually gets latest releases first us-west-2 Good selection, often early access to new models eu-west-1 European compliance, subset of US models available Advanced Configuration See Compliance and Latency Optimization for detailed configuration examples including GDPR compliance, regional optimization strategies, and best practices for multi-region deployments. AWS_BEDROCK_CROSS_REGION_INFERENCE ¶ Purpose : Enable automatic cross-region routing when a model isn't available in the primary region Type : Boolean Default : true export AWS_BEDROCK_CROSS_REGION_INFERENCE = true AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL ¶ Purpose : Allow global cross-region inference routing to any region worldwide Type : Boolean Default : true GDPR Compliance Set to false to comply with data residency regulations (e.g., EU GDPR) by restricting to regional inference only export AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL = false AWS_BEDROCK_LEGACY ¶ Purpose : Allow usage of legacy/deprecated Bedrock models Type : Boolean Default : true export AWS_BEDROCK_LEGACY = true AWS_BEDROCK_MARKETPLACE_AUTO_SUBSCRIBE ¶ Purpose : Control automatic subscription to new models in AWS Marketplace Type : Boolean Default : true Behavior : When true , the server automatically subscribes to new models discovered in the AWS Marketplace, making them immediately available through the API. When false , only models with existing marketplace subscriptions are visible and accessible IAM Permissions Required : aws-marketplace:Subscribe , aws-marketplace:ViewSubscriptions # Allow automatic subscription (default) export AWS_BEDROCK_MARKETPLACE_AUTO_SUBSCRIBE = true # Restrict to pre-subscribed models only export AWS_BEDROCK_MARKETPLACE_AUTO_SUBSCRIBE = false What is Marketplace Auto-Subscribe? AWS Bedrock requires marketplace subscription before certain models can be used. This setting controls whether stdapi.ai automatically handles the subscription process: true (default) : Models are automatically subscribed when discovered, providing seamless access to new models as they become available false : Only models that have already been subscribed through the AWS Marketplace are visible, providing explicit control over model access When to Disable Set to false when: You need explicit control over which models are accessible You want to prevent automatic marketplace subscriptions that may incur costs Your organization requires manual approval for new AI model usage Compliance policies require pre-authorization of AI models IAM Permission Requirements This feature requires the following IAM permissions to automatically subscribe to models: aws-marketplace:Subscribe - Subscribe to marketplace offerings aws-marketplace:ViewSubscriptions - View existing marketplace subscriptions See Bedrock Marketplace Auto-Subscribe section for the complete IAM policy configuration. AWS Documentation For more information about Bedrock model access and marketplace registration, see the AWS Bedrock Model Access documentation . AWS_BEDROCK_ALLOW_CROSS_REGION_INFERENCE_PROFILE_ARN ¶ Purpose : Allow users to pass cross-region inference profile ARNs directly as model IDs in API requests Type : Boolean Default : false Behavior : When enabled, users can use cross-region inference profile ARNs instead of model IDs in the model parameter. Cross-region inference profiles enable routing to multiple regions for better availability IAM Permissions Required : bedrock:GetInferenceProfile (see IAM Permissions ) # Disabled (default) - users can only use standard model IDs # No environment variable needed # Enable cross-region inference profile ARN support export AWS_BEDROCK_ALLOW_CROSS_REGION_INFERENCE_PROFILE_ARN = true Additional IAM Permissions Required Enabling this setting requires adding the bedrock:GetInferenceProfile IAM permission to your role/user. Without this permission, API requests using inference profile ARNs will fail with authorization errors. See the Bedrock Inference Profiles and Prompt Routers IAM section for the complete policy configuration. Example ARN arn:aws:bedrock:us-east-1:123456789012:inference-profile/us.anthropic.claude-3-5-sonnet-20241022-v2:0 What are Cross-Region Inference Profiles? Cross-region inference profiles are AWS-managed routing configurations that automatically distribute requests across multiple AWS regions to improve availability and reduce latency. When a model is unavailable in one region, the request is automatically routed to another region where the model is available. Automatic Cross-Region Routing (Default Behavior) By default, stdapi.ai automatically determines and uses the best cross-region inference profile for each model. You don't need to manually specify cross-region inference profile ARNs in most cases. The automatic behavior is controlled by these settings: AWS_BEDROCK_REGIONS - Defines which regions are available for routing AWS_BEDROCK_CROSS_REGION_INFERENCE (default: true ) - Enables automatic cross-region routing AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL (default: true ) - Allows global routing beyond configured regions When using standard model IDs, the application automatically: Selects the optimal AWS-managed cross-region inference profile for each model Routes requests across your configured regions for best availability Optimizes for latency and regional availability Manually specifying cross-region inference profile ARNs should only be done in rare cases when you need to override the automatic selection for specific requirements. When to Enable Enable this setting only in rare cases when: You need to override automatic cross-region profile selection You have specific cross-region routing requirements that differ from defaults You're testing or comparing different inference profile configurations For most deployments, leave this disabled and let the application handle cross-region routing automatically. AWS_BEDROCK_ALLOW_APPLICATION_INFERENCE_PROFILE_ARN ¶ Purpose : Allow users to pass application inference profile ARNs directly as model IDs in API requests Type : Boolean Default : false Behavior : When enabled, users can use application inference profile ARNs instead of model IDs in the model parameter. Application inference profiles are custom routing configurations for specific use cases IAM Permissions Required : bedrock:GetInferenceProfile (see IAM Permissions ) # Disabled (default) - users can only use standard model IDs # No environment variable needed # Enable application inference profile ARN support export AWS_BEDROCK_ALLOW_APPLICATION_INFERENCE_PROFILE_ARN = true Additional IAM Permissions Required Enabling this setting requires adding the bedrock:GetInferenceProfile IAM permission to your role/user. Without this permission, API requests using application inference profile ARNs will fail with authorization errors. See the Bedrock Inference Profiles and Prompt Routers IAM section for the complete policy configuration. Example ARN arn:aws:bedrock:us-east-1:123456789012:application-inference-profile/abc123xyz What are Application Inference Profiles? Application inference profiles are custom routing configurations that you create in your AWS account. They allow you to define specific routing behavior, region preferences, and failover strategies tailored to your application's needs. When to Enable Enable this setting when: You have custom application inference profiles configured in your AWS account You need application-specific routing configurations You want to give users access to custom profiles you've created AWS_BEDROCK_ALLOW_PROMPT_ROUTER_ARN ¶ Purpose : Allow users to pass prompt router ARNs directly as model IDs in API requests Type : Boolean Default : false Behavior : When enabled, users can use prompt router ARNs instead of model IDs in the model parameter. Prompt routers enable dynamic model selection based on prompt characteristics IAM Permissions Required : bedrock:GetPromptRouter (see IAM Permissions ) # Disabled (default) - users can only use standard model IDs # No environment variable needed # Enable prompt router ARN support export AWS_BEDROCK_ALLOW_PROMPT_ROUTER_ARN = true Additional IAM Permissions Required Enabling this setting requires adding the bedrock:GetPromptRouter IAM permission to your role/user. Without this permission, API requests using prompt router ARNs will fail with authorization errors. See the Bedrock Inference Profiles and Prompt Routers IAM section for the complete policy configuration. Example ARN arn:aws:bedrock:us-east-1:123456789012:default-prompt-router/my-router What are Prompt Routers? Prompt routers are intelligent routing systems that analyze prompt characteristics (length, complexity, language) and dynamically select the most appropriate model. This enables cost optimization and performance tuning based on request patterns. When to Enable Enable this setting when: You have prompt routers configured in your AWS account You want intelligent cost optimization through dynamic model selection You need automatic model selection based on prompt complexity AWS_BEDROCK_MODEL_ARN_MAPPING ¶ Purpose : Map standard model IDs to custom inference profile or prompt router ARNs for server-controlled routing Format : JSON object with model IDs as keys and ARNs as values Default : {} (empty, no mappings) Behavior : When configured, the mapped ARN is used instead of the default cross-region inference profile when clients request the model by its standard ID. This provides centralized control over model routing without requiring client changes export AWS_BEDROCK_MODEL_ARN_MAPPING = '{ "anthropic.claude-3-5-sonnet-20241022-v2:0": "arn:aws:bedrock:us-east-1:123456789012:application-inference-profile/my-custom-profile", "anthropic.claude-3-5-haiku-20241022-v1:0": "arn:aws:bedrock:us-east-1:123456789012:default-prompt-router/my-router" }' What is Model ARN Mapping? Model ARN mapping allows server administrators to override the default routing behavior for specific models. When a client requests a model using its standard ID (e.g., anthropic.claude-3-5-sonnet-20241022-v2:0 ), the server automatically uses the mapped ARN for routing instead. Supported ARN Types: Cross-region inference profiles - AWS-managed multi-region routing Application inference profiles - Custom routing configurations Prompt routers - Intelligent dynamic model selection Key Benefits Centralized Control - Change routing behavior without modifying client code Transparent to Clients - Clients use standard model IDs, server handles routing Easy Migration - Switch between routing strategies by updating server config Environment-Specific - Different mappings for dev/staging/production environments Use Cases Cost Optimization with Prompt Router: export AWS_BEDROCK_MODEL_ARN_MAPPING = '{ "anthropic.claude-3-5-sonnet-20241022-v2:0": "arn:aws:bedrock:us-east-1:123456789012:default-prompt-router/cost-optimizer" }' Automatically route simple prompts to cheaper models, complex prompts to premium models. Custom Application Profile: export AWS_BEDROCK_MODEL_ARN_MAPPING = '{ "anthropic.claude-3-5-sonnet-20241022-v2:0": "arn:aws:bedrock:us-east-1:123456789012:application-inference-profile/production-profile" }' Use your custom inference profile with specific region preferences and failover behavior. Environment-Specific Routing: # Production: Use cost-optimized prompt router export AWS_BEDROCK_MODEL_ARN_MAPPING = '{"anthropic.claude-3-5-sonnet-20241022-v2:0": "arn:aws:bedrock:us-east-1:123456789012:default-prompt-router/prod-router"}' # Development: Use standard cross-region profile export AWS_BEDROCK_MODEL_ARN_MAPPING = '{}' Best Practices Test mappings in development before deploying to production Document your ARN mappings and their purposes Keep ARN mappings in version control alongside other configuration Monitor routing behavior after updating mappings Other AWS Services ¶ Optional Configuration Each service region is optional and defaults to the first region in AWS_BEDROCK_REGIONS if not specified. AWS_POLLY_REGION ¶ Purpose : Region for Amazon Polly text-to-speech service Default : First region in AWS_BEDROCK_REGIONS export AWS_POLLY_REGION = us-east-1 Amazon Polly Engine Availability Not all Polly engines (Standard, Neural, Long-form, Generative) are available in all AWS regions. Verify engine and voice availability in your target region. See Amazon Polly feature and region compatibility for detailed information. AWS_COMPREHEND_REGION ¶ Purpose : Region for Amazon Comprehend language detection service Default : First region in AWS_BEDROCK_REGIONS export AWS_COMPREHEND_REGION = us-east-1 Amazon Comprehend Regional Availability Amazon Comprehend is not available in all AWS regions. stdapi.ai uses the detect_dominant_language feature for language detection. Verify service and feature availability in your target region. See Amazon Comprehend supported regions for regional availability. AWS_TRANSCRIBE_REGION ¶ Purpose : Region for Amazon Transcribe speech-to-text service Default : First region in AWS_BEDROCK_REGIONS export AWS_TRANSCRIBE_REGION = us-east-1 AWS_TRANSLATE_REGION ¶ Purpose : Region for Amazon Translate text translation service Default : First region in AWS_BEDROCK_REGIONS export AWS_TRANSLATE_REGION = us-east-1 Compliance and Latency Optimization ¶ Strategic region configuration is critical for both regulatory compliance and performance optimization. This section provides best practice configurations for common scenarios. AWS AI Services Data Privacy Amazon Bedrock : Does not store or use user prompts and responses, and does not share them with third parties by default. Your content remains private and is not used to train models. Other AI Services : AWS collects telemetry data from other AI services (Polly, Comprehend, Transcribe, Translate) by default. For enhanced data privacy and compliance, you can opt out of AWS using your content to improve AI services. Configure AI services opt-out policies at the AWS Organizations level to prevent your data from being used for service improvement. GDPR and Data Residency Compliance ¶ For applications serving European users, data residency regulations like GDPR may require that data processing occurs within specific geographic boundaries. EU-Only Configuration (Strict GDPR) # Use only European regions export AWS_S3_BUCKET = my-stdapi-eu-bucket export AWS_BEDROCK_REGIONS = eu-west-1,eu-west-3,eu-central-1 # Disable global cross-region inference to prevent data routing outside Europe export AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL = false # Keep cross-region inference enabled for failover within EU regions export AWS_BEDROCK_CROSS_REGION_INFERENCE = true Key Compliance Settings AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL=false : Prevents requests from being routed to regions outside your specified list AWS_BEDROCK_CROSS_REGION_INFERENCE=true : Enables cross-region inference within your specified EU regions All services in EU regions : Ensures all data processing stays within European boundaries Important Considerations Not all Bedrock models are available in all EU regions - verify model availability Some newer models may be available in US regions first; this configuration prioritizes compliance over immediate access to latest models S3 buckets must be created in EU regions and configured appropriately for data residency Latency Optimization ¶ For applications prioritizing low latency and high performance, configure regions closest to your users and application infrastructure. North America: # Primary region for lowest latency, with fallbacks export AWS_S3_BUCKET = my-stdapi-us-east-1-bucket export AWS_BEDROCK_REGIONS = us-east-1,us-west-2,us-east-2 # Enable all cross-region inference for maximum model availability export AWS_BEDROCK_CROSS_REGION_INFERENCE = true export AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL = true Asia-Pacific: # Use Asia-Pacific regions for lowest latency to APAC users export AWS_S3_BUCKET = my-stdapi-ap-southeast-1-bucket export AWS_BEDROCK_REGIONS = ap-southeast-1,ap-northeast-1,us-west-2 # Enable global inference for fallback to US regions if needed export AWS_BEDROCK_CROSS_REGION_INFERENCE = true export AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL = true Global Multi-Region: # Balanced configuration with worldwide coverage export AWS_S3_BUCKET = my-stdapi-us-east-1-bucket export AWS_BEDROCK_REGIONS = us-east-1,eu-west-1,ap-southeast-1,us-west-2 # Enable global inference for best availability export AWS_BEDROCK_CROSS_REGION_INFERENCE = true export AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL = true Latency Optimization Tips Server and S3 co-location : Deploy stdapi.ai and your AWS_S3_BUCKET in the first region specified in AWS_BEDROCK_REGIONS (your primary region) Network proximity : Choose the first region based on low latency to your application servers and end users Data transfer costs : Cross-region data transfer incurs costs; co-locating server and S3 in the same region minimizes these Model availability : While us-east-1 often has the most models, check specific model availability in your target regions Hybrid Approach: Compliance with Performance ¶ Balance compliance requirements with performance needs: EU Primary with US Fallback # EU primary with US fallback (for model availability) export AWS_S3_BUCKET = my-stdapi-eu-bucket export AWS_BEDROCK_REGIONS = eu-west-1,eu-central-1,us-east-1 # Allow cross-region but restrict to specific regions only export AWS_BEDROCK_CROSS_REGION_INFERENCE = true export AWS_BEDROCK_CROSS_REGION_INFERENCE_GLOBAL = false Legal Compliance Notice Including us-east-1 as a fallback region provides access to more models but may not comply with strict data residency requirements. Consult your legal and compliance teams before using this configuration. Configuration Order ¶ When deploying stdapi.ai, configure settings in this recommended order: IAM Permissions - Set up AWS access first AWS Services and Regions - Configure S3 buckets and Bedrock regions Authentication - Secure your API with authentication Optional Features - Add observability, guardrails, and other features as needed IAM Permissions ¶ stdapi.ai requires specific AWS IAM permissions to access Bedrock models and other AWS services. The exact permissions needed depend on which features you enable. Building Your Policy Combine the permission statements below based on the features you need. At minimum, you need the Bedrock permissions. Add statements for S3, TTS, STT, and other features as required by your deployment. Bedrock (Required) ¶ Environment Variables : Always required These permissions are mandatory for stdapi.ai to discover and invoke Bedrock models: Bedrock IAM Policy Statements { "Sid" : "BedrockModelInvoke" , "Effect" : "Allow" , "Action" : [ "bedrock:GetAsyncInvoke" , "bedrock:InvokeModel" , "bedrock:InvokeModelWithResponseStream" , "bedrock:InvokeTool" ], "Resource" : "*" }, { "Sid" : "BedrockModelDiscovery" , "Effect" : "Allow" , "Action" : [ "bedrock:ListFoundationModels" , "bedrock:GetFoundationModelAvailability" , "bedrock:ListProvisionedModelThroughputs" , "bedrock:ListInferenceProfiles" ], "Resource" : "*" } Bedrock Marketplace Auto-Subscribe (Optional) ¶ Environment Variables : AWS_BEDROCK_MARKETPLACE_AUTO_SUBSCRIBE Required only if you want to enable automatic subscription to new models in the AWS Marketplace ( AWS_BEDROCK_MARKETPLACE_AUTO_SUBSCRIBE=true , which is the default). When enabled, the server can automatically subscribe to marketplace offerings for newly discovered models. Bedrock Marketplace Auto-Subscribe IAM Policy Statement { "Sid" : "BedrockMarketplaceAutoSubscribe" , "Effect" : "Allow" , "Action" : [ "aws-marketplace:Subscribe" , "aws-marketplace:ViewSubscriptions" ], "Resource" : "*" } Cost Consideration Automatic marketplace subscriptions may incur costs. Review AWS Marketplace pricing for individual models before enabling this feature, or set AWS_BEDROCK_MARKETPLACE_AUTO_SUBSCRIBE=false to require manual marketplace subscription. Bedrock Inference Profiles and Prompt Routers (Optional) ¶ Environment Variables : AWS_BEDROCK_ALLOW_CROSS_REGION_INFERENCE_PROFILE_ARN , AWS_BEDROCK_ALLOW_APPLICATION_INFERENCE_PROFILE_ARN , AWS_BEDROCK_ALLOW_PROMPT_ROUTER_ARN , AWS_BEDROCK_MODEL_ARN_MAPPING Required only if you enable ARN-based routing features that allow users to pass inference profile or prompt router ARNs directly as model IDs, or if you configure server-side ARN mappings. Bedrock Inference Profiles and Prompt Routers IAM Policy Statement { "Sid" : "BedrockInferenceProfilesAndPromptRouters" , "Effect" : "Allow" , "Action" : [ "bedrock:GetInferenceProfile" , "bedrock:GetPromptRouter" ], "Resource" : "*" } When to Include Add these permissions when: AWS_BEDROCK_ALLOW_CROSS_REGION_INFERENCE_PROFILE_ARN=true AWS_BEDROCK_ALLOW_APPLICATION_INFERENCE_PROFILE_ARN=true AWS_BEDROCK_ALLOW_PROMPT_ROUTER_ARN=true AWS_BEDROCK_MODEL_ARN_MAPPING is configured with any mappings Bedrock Guardrails (Optional) ¶ Environment Variables : AWS_BEDROCK_GUARDRAIL_IDENTIFIER , AWS_BEDROCK_GUARDRAIL_VERSION Required only if you configure Bedrock Guardrails for content filtering. See Bedrock Guardrails configuration section. Bedrock Guardrails IAM Policy Statement { "Sid" : "BedrockGuardrails" , "Effect" : "Allow" , "Action" : [ "bedrock:ApplyGuardrail" ], "Resource" : "arn:aws:bedrock:*:*:guardrail/*" } S3 File Storage (Optional) ¶ Environment Variables : AWS_S3_BUCKET Required for storing generated images, audio files, and documents. See Storage Configuration for bucket setup details. S3 File Storage IAM Policy Statements { "Sid" : "S3FileStorage" , "Effect" : "Allow" , "Action" : [ "s3:PutObject" , "s3:GetObject" , "s3:DeleteObject" ], "Resource" : "arn:aws:s3:::AWS_S3_BUCKET_VALUE/*" } Replace Bucket Name Replace AWS_S3_BUCKET_VALUE with the value of your AWS_S3_BUCKET environment variable. If your S3 bucket uses KMS encryption , also add: { "Sid" : "KMSEncryptedBucket" , "Effect" : "Allow" , "Action" : [ "kms:Decrypt" , "kms:GenerateDataKey" ], "Resource" : "arn:aws:kms:REGION:ACCOUNT_ID:key/YOUR_KMS_KEY_ID" , "Condition" : { "StringEquals" : { "kms:ViaService" : "s3.REGION.amazonaws.com" } } } KMS Security The kms:ViaService condition restricts KMS key usage to S3 service calls only, following AWS security best practices. Text-to-Speech (Optional) ¶ Environment Variables : AWS_POLLY_REGION , DEFAULT_TTS_MODEL Required for generating speech from text using Amazon Polly. See Audio and Text-to-Speech configuration section. Polly Text-to-Speech IAM Policy Statement { "Sid" : "PollyTextToSpeech" , "Effect" : "Allow" , "Action" : [ "polly:SynthesizeSpeech" , "polly:DescribeVoices" ], "Resource" : "*" } Speech-to-Text (Optional) ¶ Environment Variables : AWS_TRANSCRIBE_REGION , AWS_TRANSCRIBE_S3_BUCKET Required for transcribing audio files using Amazon Transcribe. Transcribe Speech-to-Text IAM Policy Statements { "Sid" : "TranscribeSpeechToText" , "Effect" : "Allow" , "Action" : [ "transcribe:StartTranscriptionJob" , "transcribe:GetTranscriptionJob" , "transcribe:DeleteTranscriptionJob" ], "Resource" : "*" }, { "Sid" : "TranscribeS3Storage" , "Effect" : "Allow" , "Action" : [ "s3:PutObject" , "s3:GetObject" , "s3:DeleteObject" ], "Resource" : "arn:aws:s3:::AWS_TRANSCRIBE_S3_BUCKET_VALUE/*" } Replace Bucket Name Replace AWS_TRANSCRIBE_S3_BUCKET_VALUE with the value of your AWS_TRANSCRIBE_S3_BUCKET environment variable (or AWS_S3_BUCKET if using the same bucket). If your transcribe S3 bucket uses KMS encryption , also add the KMS permissions with the appropriate bucket ARN. Language Detection (Optional) ¶ E | 2026-01-13T09:30:25 |
https://lists.debian.org/debconf.html | Debian Mailing Lists -- Index for Debconf mailing lists Skip Quicknav About Debian Getting Debian Support Developers' Corner Mailing Lists / Index for Debconf Debian Mailing Lists Please see the introduction to Debian mailing lists for more information on what they are and how they can be used. Click on a mailing list name to see the information for that list. As a shortcut, years and months on this page designate archives, if any. DebConf lists Lists related to DebConf. Our list server provides mailinglists for DebConf related tasks. debconf-announce : Debconf Announcements 2005 [ Dec ] 2006 [ Jan ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Oct ] [ Nov ] 2007 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Oct ] [ Dec ] 2008 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Dec ] 2009 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] 2010 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Nov ] 2011 [ Apr ] [ May ] [ Jun ] [ Jul ] [ Dec ] 2012 [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] 2013 [ Feb ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Oct ] 2014 [ Feb ] [ Apr ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Nov ] 2015 [ Feb ] [ Mar ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Nov ] 2016 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Sep ] [ Oct ] [ Dec ] 2017 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Nov ] 2018 [ Feb ] [ Mar ] [ Apr ] [ Jun ] [ Jul ] [ Aug ] 2019 [ Mar ] [ Apr ] [ Jun ] [ Jul ] 2020 [ Feb ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Oct ] [ Nov ] [ Dec ] 2021 [ Jan ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] 2022 [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] 2023 [ Apr ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Dec ] 2024 [ Jan ] [ Mar ] [ Apr ] [ May ] [ Jul ] [ Aug ] [ Oct ] [ Nov ] [ Dec ] 2025 [ Mar ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Dec ] debconf-bid-capetown : DebConf bid team for Cape Town 2014 [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2015 [ Jan ] [ Feb ] debconf-bid-paris : DebConf bid team for Paris 2014 [ Sep ] 2015 [ Aug ] 2018 [ Apr ] [ Sep ] debconf-discuss : Discussions about Debconf 2004 [ Jun ] [ Nov ] 2005 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] 2006 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Oct ] [ Nov ] 2007 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Dec ] 2008 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] 2009 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2010 [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Nov ] [ Dec ] 2011 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2012 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2013 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Dec ] 2014 [ Feb ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2015 [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] 2016 [ Jan ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2017 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2018 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] 2019 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Dec ] 2020 [ Jan ] [ Feb ] [ Mar ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2021 [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] 2022 [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2023 [ Mar ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] 2024 [ Jan ] [ Feb ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Dec ] 2025 [ Feb ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Dec ] debconf-infra : DebConf Infrastructure team 2015 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] 2016 [ Jun ] 2017 [ Sep ] [ Nov ] 2018 [ Jun ] 2019 [ Jun ] [ Oct ] 2020 [ Mar ] [ Jun ] [ Nov ] [ Dec ] 2022 [ Jul ] [ Aug ] [ Sep ] 2024 [ Jan ] 2025 [ Jan ] [ Mar ] [ Apr ] [ Jun ] [ Sep ] debconf-kids : Discussion about Kids at DebConf 2014 [ Aug ] 2015 [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Nov ] 2016 [ Feb ] [ Sep ] 2017 [ Mar ] [ Jul ] 2018 [ Jun ] [ Jul ] 2019 [ Jan ] [ Dec ] 2020 [ Jan ] [ Jul ] debconf-mini-berlin : Organization mailing list for the MiniDebConf in Berlin 2023 [ Sep ] debconf-mini-bucharest : Organization mailing list for the MiniDebConf in Bucharest 2015 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Oct ] 2018 [ Mar ] 2019 [ Nov ] debconf-mini-germany : Organization mailing list for MiniDebConfs in Germany debconf-mini-hamburg : Organization mailing list for the MiniDebConf in Hamburg 2017 [ Nov ] 2018 [ Jan ] [ Feb ] [ May ] 2019 [ May ] [ Jul ] 2021 [ Sep ] 2022 [ Mar ] [ Apr ] [ May ] [ Sep ] [ Oct ] 2023 [ Mar ] [ Apr ] [ May ] [ Dec ] 2024 [ Mar ] [ Dec ] 2025 [ Jan ] [ Mar ] [ May ] [ Jul ] [ Aug ] [ Dec ] debconf-sponsors-team : DebConf Sponsors Team List debconf-team : DebConf Organizer Team List 2004 [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2005 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2006 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2007 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2008 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2009 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2010 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2011 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2012 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2013 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2014 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2015 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2016 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2017 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2018 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2019 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2020 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] 2021 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Dec ] 2022 [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Nov ] [ Dec ] 2023 [ Mar ] [ Apr ] [ May ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2024 [ Jan ] [ Feb ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Nov ] [ Dec ] 2025 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2026 [ Jan ] debconf-video : DebConf Video Team List 2005 [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] 2006 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jul ] [ Aug ] [ Oct ] [ Nov ] 2007 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2008 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Nov ] [ Dec ] 2009 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Oct ] [ Dec ] 2010 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Nov ] [ Dec ] 2011 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2012 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Sep ] [ Nov ] [ Dec ] 2013 [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Oct ] 2014 [ Jan ] [ Feb ] [ Apr ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] 2015 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2016 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Nov ] [ Dec ] 2017 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2018 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2019 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2020 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2021 [ Jan ] [ Apr ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] 2022 [ Mar ] [ Apr ] [ May ] [ Jul ] [ Aug ] [ Sep ] [ Nov ] 2023 [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] 2024 [ Jan ] [ Mar ] [ Apr ] [ May ] [ Jul ] [ Aug ] 2025 [ Jan ] [ Mar ] [ Apr ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] debconf14-team : Team Discussion for organizing DebConf14 in Portland 2013 [ May ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2014 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Nov ] 2016 [ Dec ] 2017 [ Feb ] [ Jul ] 2018 [ Jan ] debconf15-team : Team Discussion for organizing DebConf15 in Germany 2014 [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2015 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Nov ] [ Dec ] 2016 [ Jan ] [ Apr ] [ Jun ] [ Jul ] [ Aug ] [ Oct ] 2017 [ Mar ] [ Jul ] 2020 [ Aug ] debconf16-team : Team Discussion for organizing DebConf16 in South Africa 2015 [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] 2016 [ Feb ] [ Mar ] [ Jun ] 2017 [ Jan ] [ Feb ] [ Jul ] 2022 [ Mar ] [ Oct ] If you wish to browse a complete list of mailing lists, see the complete index . Back to: Debian Lists || Debian Project homepage . Home About Social Contract Code of Conduct Free Software Partners Donations Contact Us Getting Debian Network install CD/USB ISO images CD vendors Pre-installed Debian Packages News Project News Events Documentation Release Info Installation manual Debian Books Support Debian International Security Information Bug reports Mailing Lists Mailing List Archives Ports/Architectures Miscellaneous Help Debian Developers' Corner Site map Search You may submit bugs against the list archives using the lists.debian.org pseudo-package or contact the maintainer at listmaster@lists.debian.org . See the Debian contact page for further information on contacting us. Copyright © 2015 SPI and others; See license terms Debian is a registered trademark of Software in the Public Interest, Inc. | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/enum_csv/actions/workflows/ci.yml | CI · Workflow runs · jeremyevans/enum_csv · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / enum_csv Public Notifications You must be signed in to change notification settings Fork 0 Star 9 Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights Actions: jeremyevans/enum_csv Actions --> All workflows Workflows CI CI Show more workflows... Management Caches CI CI Actions Loading... Loading Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> will be ignored since log searching is not yet available Show workflow options Create status badge Create status badge Loading Uh oh! There was an error while loading. Please reload this page . ci.yml --> will be ignored since log searching is not yet available 6 workflow runs 6 workflow runs Event Filter by Event Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching events. Status Filter by Status Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching statuses. Branch Filter by Branch Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching branches. Actor Filter by Actor Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching users. Add Ruby 4.0 to CI CI #16: Commit ddf4922 pushed by jeremyevans 9m 22s master master 9m 22s View workflow file Add JRuby 10.0 to CI CI #15: Commit ec63864 pushed by jeremyevans 4m 52s master master 4m 52s View workflow file Switch rdoc task to normal rake task, avoid rdoc/task require CI #14: Commit cd6b320 pushed by jeremyevans 1m 0s master master 1m 0s View workflow file CI CI #13: by jeremyevans 56s master master 56s View workflow file Add Ruby 3.4 to CI CI #12: Commit 71216de pushed by jeremyevans 54s master master 54s View workflow file Use -W:strict_unused_block when running tests on Ruby 3.4+ CI #11: Commit f5a1cd6 pushed by jeremyevans 56s master master 56s View workflow file You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fcoreboot&trk=organization_guest_nav-header-join | Sign Up | LinkedIn Join LinkedIn now — it’s free! Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password (6+ characters) Show Remember me First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/locating-files/ | Locate Files | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Usage Convert Documents Locate Files 3.0 3.0 2.5 Edit this Page Locate Files AsciidoctorJ offers a collection of utilities called DirectoryWalkers for scenarios where sources may be organized in special ways. Built-in DirectoryWalker implementations Class Type Description AsciiDocDirectoryWalker Concrete class Locates all files of given folder and all its subfolders. Ignores files starting with underscore (_). GlobDirectoryWalker Concrete class Locates all files of given folder following a glob expression. You can also create your own DirectoryWalkers by extending AbstractDirectoryWalker class or DirectoryWalker interface. AsciiDocDirectoryWalker class A utility class AsciiDocDirectoryWalker is available for searching the AsciiDoc files present in a root folder and its subfolders. AsciiDocDirectoryWalker locates all files that end with .adoc , .ad , .asciidoc or .asc . Also it ignores all files starting with underscore ( _ ). Locating AsciiDoc files with AsciiDocDirectoryWalker import java.util.List; import org.asciidoctor.AsciiDocDirectoryWalker; DirectoryWalker directoryWalker = new AsciiDocDirectoryWalker("docs"); (1) List<File> asciidocFiles = directoryWalker.scan(); (2) 1 Defines which parent directory is used for searching. 2 Returns a list of all AsciiDoc files found in root folder and its subfolders. GlobDirectoryWalker class A utility class GlobDirectoryWalker is available for searching the AsciiDoc files present in a root folder and scanning using a Glob expression. GlobDirectoryWalker locates all files that end with .adoc , .ad , .asciidoc or .asc . Locating AsciiDoc files with GlobDirectoryWalker import java.util.List; import org.asciidoctor.GlobDirectoryWalker; DirectoryWalker directoryWalker = new GlobDirectoryWalker("docs", "**/*.adoc"); (1) List<File> asciidocFiles = directoryWalker.scan(); (2) 1 Defines which parent directory is used for searching and the glob expression. 2 Returns a list of all AsciiDoc files matching given glob expression. Conversion Options Safe Modes Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/rack-unreloader/actions/workflows/ci.yml | CI · Workflow runs · jeremyevans/rack-unreloader · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / rack-unreloader Public Notifications You must be signed in to change notification settings Fork 9 Star 108 Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights Actions: jeremyevans/rack-unreloader Actions --> All workflows Workflows CI CI Show more workflows... Management Caches CI CI Actions Loading... Loading Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> will be ignored since log searching is not yet available Show workflow options Create status badge Create status badge Loading Uh oh! There was an error while loading. Please reload this page . ci.yml --> will be ignored since log searching is not yet available 8 workflow runs 8 workflow runs Event Filter by Event Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching events. Status Filter by Status Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching statuses. Branch Filter by Branch Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching branches. Actor Filter by Actor Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching users. Add Ruby 4.0 to CI CI #26: Commit c6e78db pushed by jeremyevans 15m 19s master master 15m 19s View workflow file Use SimpleCov.add_filter block instead of string CI #25: Commit 3fa66bb pushed by jeremyevans 59s master master 59s View workflow file Fix spec guard to handle JRuby 10.0 CI #24: Commit f2f36a7 pushed by jeremyevans 1m 14s master master 1m 14s View workflow file Add JRuby 10.0 to CI CI #23: Commit 4db7151 pushed by jeremyevans 6m 20s master master 6m 20s View workflow file Switch rdoc task to normal rake task, avoid rdoc/task require CI #22: Commit 33a6f63 pushed by jeremyevans 1m 6s master master 1m 6s View workflow file Work with ubuntu-latest using 24.04 by default in CI CI #21: Commit de62600 pushed by jeremyevans 53s master master 53s View workflow file Add Ruby 3.4 to CI CI #20: Commit 2c8362e pushed by jeremyevans 58s master master 58s View workflow file Use -W:strict_unused_block when running tests on Ruby 3.4+ CI #19: Commit 05e6a91 pushed by jeremyevans 1m 1s master master 1m 1s View workflow file You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://lists.macports.org/mailman/listinfo/macports-dev | macports-dev Info Page macports-dev -- MacPorts developer discussion About macports-dev English (USA) Discussion for MacPorts development and Portfile writing. If you wish to post to the mailing list, please subscribe first; we require this to prevent spam. Make sure you subscribe with the same email address from which you want to post. To see the collection of prior postings to the list, visit the macports-dev Archives . Using macports-dev To post a message to all the list members, send email to macports-dev@lists.macports.org . You can subscribe to the list, or change your existing subscription, in the sections below. Subscribing to macports-dev Subscribe to macports-dev by filling out the following form. You will be sent email requesting confirmation, to prevent others from gratuitously subscribing you. This is a hidden list, which means that the list of members is available only to the list administrator. Your email address: Your name (optional): You may enter a privacy password below. This provides only mild security, but should prevent others from messing with your subscription. Do not use a valuable password as it will occasionally be emailed back to you in cleartext. If you choose not to enter a password, one will be automatically generated for you, and it will be sent to you once you've confirmed your subscription. You can always request a mail-back of your password when you edit your personal options. Pick a password: Reenter password to confirm: Which language do you prefer to display your messages? English (USA) Would you like to receive list mail batched in a daily digest? No Yes macports-dev Subscribers ( The subscribers list is only available to the list administrator. ) Enter your admin address and password to visit the subscribers list: Admin address: Password: To unsubscribe from macports-dev, get a password reminder, or change your subscription options enter your subscription email address: If you leave the field blank, you will be prompted for your email address macports-dev list run by macports-dev-owner at lists.macports.org macports-dev administrative interface (requires authorization) Overview of all lists.macports.org mailing lists version 2.1.29 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/guides/access-jruby-instance/ | Accessing the JRuby Instance | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Help & Guides Accessing the JRuby Instance 3.0 3.0 2.5 Edit this Page Accessing the JRuby Instance Sometimes you may need the Ruby runtime used inside AsciidoctorJ. One reason is because you are using JRuby outside AsciidoctorJ and you want to reuse the same instance. Another reason is that you need to instantiate by yourself an Asciidoctor Ruby object. To get this instance you can use org.asciidoctor.jruby.internal.JRubyRuntimeContext.get(Asciidoctor) to get it from a given Asciidoctor instance. Running AsciidoctorJ with Spring Boot Loading Ruby Libraries Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://bundler.io/v4.0/man/bundle-binstubs.1.html | Bundler: bundle binstubs Bundler Docs Team Blog Repository bundle binstubs bundle-binstubs - Install the binstubs of the listed gems bundle binstubs GEM_NAME [--force] [--standalone] [--all-platforms] Description Binstubs are scripts that wrap around executables. Bundler creates a small Ruby file (a binstub) that loads Bundler, runs the command, and puts it into bin/ . Binstubs are a shortcut-or alternative- to always using bundle exec . This gives you a file that can be run directly, and one that will always run the correct gem version used by the application. For example, if you run bundle binstubs rspec-core , Bundler will create the file bin/rspec . That file will contain enough code to load Bundler, tell it to load the bundled gems, and then run rspec. This command generates binstubs for executables in GEM_NAME . Binstubs are put into bin , or the directory specified by bin setting if it has been configured. Calling binstubs with [GEM [GEM]] will create binstubs for all given gems. Options --force Overwrite existing binstubs if they exist. --standalone Makes binstubs that can work without depending on Rubygems or Bundler at runtime. --shebang=SHEBANG Specify a different shebang executable name than the default (default 'ruby') --all Create binstubs for all gems in the bundle. --all-platforms Install binstubs for all platforms. Choose version v4.0 v2.7 v2.6 v2.5 v2.4 v2.3 v2.2 v2.1 v2.0 v1.17 v1.16 v1.15 v1.14 v1.13 General Release notes Primary Commands bundle install bundle update bundle cache bundle exec bundle config bundle help Utilities bundle bundle add bundle binstubs bundle check bundle clean bundle console bundle doctor bundle env bundle fund bundle gem bundle info bundle init bundle issue bundle licenses bundle list bundle lock bundle open bundle outdated bundle platform bundle plugin bundle pristine bundle remove bundle show bundle version gemfile Edit this document on GitHub if you caught an error or noticed something was missing. Docs Team Blog About Repository | 2026-01-13T09:30:25 |
https://rubygems.org/gems/subset_sum | subset_sum | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up subset_sum 1.0.2 Simple Subset Sum Solver with C and Pure Ruby Versions Gemfile: = install: = Versions: 1.0.2 December 05, 2016 (9.5 KB) 1.0.1 November 20, 2010 (8.5 KB) 1.0.0 October 08, 2008 * (8 KB) Owners: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 27,216 For this version 18,044 Version Released: December 5, 2016 5:35pm Licenses: N/A Required Ruby Version: >= 0 Links: Homepage Documentation Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/guides/run-in-osgi/ | Using AsciidoctorJ in an OSGi environment | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Help & Guides Running in Frameworks Using AsciidoctorJ in an OSGi environment 3.0 3.0 2.5 Edit this Page Using AsciidoctorJ in an OSGi environment In a non OSGi context, the following snippet will successfully create an Asciidoctor object: import static org.asciidoctor.Asciidoctor.Factory.create; import org.asciidoctor.Asciidoctor; Asciidoctor asciidoctor = create(); In an OSGi context it will not work because JRuby needs some paths to find the Asciidoctor gems. In order to make it work, you will need to specify the Asciidoctor gems path using the JavaEmbedUtils class. We will update the previous snippet of code to specify this path: import static org.asciidoctor.jruby.AsciidoctorJRuby.Factory.create; import org.asciidoctor.Asciidoctor; Asciidoctor asciidoctor = create(Arrays.asList("uri:classloader:/gems/asciidoctor-2.2.0/lib")); (1) (2) 1 uri:classloader:/gems/asciidoctor-<version>/lib specifies where the gems for Asciidoctor are located. Actually this path is located inside the asciidoctorj-<version>.jar file 2 The version here differs from the AsciidoctorJ version as it corresponds to the version of Asciidoctor, not the AsciidoctorJ one. We consider this code to be placed inside an OSGi bundle This solution has pros and cons: Pros: you don’t need to extract the gems located in the asciidoctorj binary ; Cons: the version of asciidoctor is hard coded ; Extension Migration: 1.5.x to 1.6.x Running AsciidoctorJ on WildFly Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
http://heisenbug.blogspot.com/search?updated-max=2010-11-27T16:27:00-08:00#main | don't count on finding me skip to main | skip to sidebar don't count on finding me Saturday, November 27, 2010 Applicative Structures and Thrists I've been toying with the idea of furnishing the the applicative framework into thrist-like clothing , with early attempts here . Last night I might have gotten it, finally... Here is the idea. Since function application is left-associative, but thrists are right associative, I'll reverse the application's direction to right-to-left, i.e. f a b c will become c b a f . This uglyness is another reason to finally whip up a RevThrist , which would be SNOC-like and left-associative. We need following ingredients: Fun - functions perform the reduction to a new object, Arg - arguments successively saturate the applicable structure to the right, Par - partial application (or parent) initiates the reduction. I'll explain these elements next, but first rewrite the above expression a bit to get a parentesized form (c(b(a f))) , and now with roles marked up in thrist syntax: Cons (Arg c) $ Cons (Arg b) $ Cons (Arg a) $ Cons (Fun f) Nil Looks almost reasonable. Time to define the ingredients mentioned above. Remember, that it must be a two-parameter data type and that the types must match up between Arg c and Arg b , etc., and finally between Arg a and Fun f . This is a pretty hefty requirement! We can attempt passing the effective application type between the ingredients, defining the data structure as data Appli :: * → * → * where Fun :: (a → b) → Appli (a → b) c Arg :: a → Appli b (a → b) This means functions pass their own type to the left (and ignoring what comes from the right), while arguments expect a saturable effective type from the right, store an appropriate value and propagate the remaining type to the left. This should work now: Cons (Arg 'a') $ Cons (Fun ord) Nil , with the type being Thrist Appli Int c . As you can see, no function type gets passed to the left, so you cannot prepend any more arguments. But this all appears useless since we cannot nest things. The Par ingredient will take care of this: Par :: Thrist Appli a c → Appli b (a → b) Par has a double role, it acts just like an argument, but holding a thrist inside, and thus groups a sub-application. The c type variable occurring in Par and Fun troubled me a lot, because it allows building up illegal thrists. Consider Cons (Fun f) $ Cons (Fun f) Nil . This gibberish cannot be assigned any reasonable semantics! Finally it occurred to me to use a phantom type for filling in this breach: data Peg Since Peg is uninhabited, no function signature can include it (unless it is a divergent one). It also ensures that the leftmost ingredient in a thrist is a function, how practial for Par ! Anyway, our Appli is done now: data Appli :: * → * → * where Fun :: (a → b) → Appli (a → b) Peg Arg :: a → Appli b (a → b) Par :: Thrist Appli a Peg → Appli b (a → b) So what brave soul will try this out? Because I must confess, up to this point I've been too lazy to fire up GHC! You might be inclined to say, why this whole circus? An awkward notation for something as simple as function application? Any Haskell implementation can do this with a beautiful syntax! Yes, we can build up applications but can't even compute them. This is a toy at the moment. But try to pull apart an application in Haskell! You can't! Here you can add an evaluator ( foldlThrist ?) and also instrument, trace, debug your evaluation process. Also, there is a reason I say 'Applicative Structures' in the title. Here is a generalization of Appli that is parametrized: data Appli :: ( * → * → * ) → * → * → * where Fun :: (a ~> b) → Appli ( ~> ) (a ~> b) Peg Arg :: a → Appli ( ~> ) b (a ~> b) Par :: Thrist (Appli ( ~> )) a Peg → Appli ( ~> ) b (a ~> b) You are free now to create your own function and value space with attached typing rules and still be able to use Thrist (Appli MySpace) ... The possibilities are endless, e.g. encrypted execution on remote hosts or abstract interpretation, you say it. Have Fun ! Posted by heisenbug at 6:37 AM No comments: Labels: applicative , haskell , thrist Thursday, November 25, 2010 Type Synonyms Generalized Type functions are the new trend. Ωmega has them with the following syntax: tfun :: Nat ~> Nat {tfun Z} = S Z Haskell (that is GHC) has them in the flavor of type families. It has just occurred to me that they can be considered as a syntactic relaxation of type synonyms! Look: tfun :: Nat ~> Nat type tfun Z = S Z type tfun (S n) = Z When conventional type synonyms are used they must be fully applied. This should be the case here too. I am not sure whether type families or Ωmega-style type functions can be partially applied, though. Anyway, a bit more to write at the definition site but less curlies to type at the call site; it may well be worth it. Posted by heisenbug at 3:06 PM No comments: Labels: crazy , haskell , omega Patterns and Existentials I am reading papers again and this always activates my creative fantasy. I want to explain a small revelation I had just now. Patterns are the same thing as declaring existential values corresponding to all pattern variables according to their respective types as stated in their respective constructors and asserting that the pattern interpreted as a value is the same as the scrutinee. The body behind the pattern in turn is similarly evaluated with the existential variables in scope. Of course the existential values are filled in by some oracle which is uninteresting from the typing perspective. A strong corollary of the asserted value identity is that we can also assert that the type of the scrutinee unifies with the type of the pattern-value (in the scope of the existentials, but not outside of it)! Just as universally quantified values are typed by dependent products (∏-stuff) the existentially quantified values are typed by dependent sums (∑-stuff). Note that the stuff is at stratum 1, e.g. types. This is in contrast to the Haskell data declaration data Foo = forall a . Foo a where a is at stratum 1, being an existential type . Hmm, when thinking this to the end we may either end up at the conventional non-inference for GADTs or something like the generalized existentials as proposed in Chuan-kai Lin's thesis. I conjecture also that this is the same thing as the post-facto type inference I suggested here . Now all remains to is to reinterpret function calls as a data type being a tuple with existential values and to apply the above trick. Posted by heisenbug at 2:21 PM No comments: Labels: crazy , GADT , haskell Tuesday, November 23, 2010 Hats off The types subreddit references Chuan-kai Lin's PhD thesis about GADT type inference. I already have read the pointwise paper , but this is of course a revelation. He actually did implement an algorithm that inferred types for 25 (out of 30) little benchmark programs with GADTs. Previous attempts accomplished at most one! But the thing that impressed me the most wasn't the technical side of his story but the beautifully crafted slides of his PhD defense talk. I am baffled... Congratulations Chuan-kai! Posted by heisenbug at 6:09 PM No comments: Labels: GADT , types Friday, November 12, 2010 Cooperation I have just uploaded the thrist-0.2 package to hackage. All credit goes to Brandon Simmons , who has added significant functionality and now provides some functions for thrists that are more in line with the prelude. Brandon has accepted to be a co-author to the library and I am very happy about it. Welcome, Brandon! For the users of the package this is good news, as I am a little dim spot on the outer sectors of the haskell radar, while Brandon is a savvy and ambitioned person, and to continue with my previous metaphor, a bright green dot on the screen, swiftly moving towards the center :-) This post is a kind of mini release note for the release. Being an experimental package we do not intend to guarantee API stability, so we took the freedom to rename routines to make naming more consistent with the prelude. foldThrist is now foldrThrist and it got a bunch of new cousins too. Notably the types are much wider now, which allows for some more magic to happen. Finally, the haddock comments have been enhanced and as-of-present actually tell something. Please ignore the sub-modules for now, they are unfinished, and much more experimental than the rest (I have not got around researching a compelling solution yet). A RevThrist (or similar) GADT did not make it into the release, I hope I can cram it in sometime later. Anyway, enjoy the lib! Posted by heisenbug at 5:55 PM No comments: Labels: hackage , haskell , thrist Monday, October 18, 2010 Lion's Share I am sick. Five days already, and counting. My brain feels like Sauerkraut and thinking is hard. But my dysregulated sleep cycle lets me ponder all kinds of idle things. One of them is the upcoming "Back to Mac" announcements on Wednesday 11/9. It seems pretty sure that Mac OS X 10.7 (or 11.0 possibly) will be introduced under the 'Lion' code name. This is pretty exciting as nothing really revolutionary happened in the Mac world since 'Leopard'. Many people are speculating what the foundations will be. My bet is a fully-LLVM compiled system: good-bye GCC, we had a nice time together. The majority of the LLVM team is virtually absent from the IRC channel and the mailing lists, they must be working on something big... That is, ironing out the latest bugs so that nothing embarrassing can happen while Steve is on stage. But clang v2.8 already compiles e.g. the FreeBSD kernel and userland with pretty good quality, so this cannot be the entire reason. The (already filled-in) job posting for a "revolutionary new feature in the very foundations of Mac OS X" is probably LLVM-related. Modern GPUs have hundreds of very potent processors that excel at floating-point computations. To use them effectively one needs a flexible compiler that can specialize snippets of code to run on each with optimal throughput. OpenCL attempts this but mostly in the graphical domain, and it sources from a C-like language. What we have in this case, however, is not about graphics... I am going on a limb here and suggest that the new feature is about ... conscience! Yeah, a primitive (compared to humans) but effective way of reflection, that is, understanding of its own existence and goals. Also the goals of the user! This will pave the way to new forms of assistance the OS can provide for us to get our jobs done. It has been tried many times, but to cite the job description, "Something that has never been done before and will truly amaze everyone". My neuronal storm has ceased, I feel limp and tired. Time for another nap. Bye. Posted by heisenbug at 1:56 PM No comments: Labels: llvm , mac , speculation Friday, August 27, 2010 Link as link can Today I made my first significant contribution to clang , by fixing PR8007 , which was a showstopper for building the codebase that I develop at my workplace. I added a testcase that validates the fix, too. In a nutshell, everything compiled well, but failed to link because of a non-instantiated type-dependent friend function. Admittedly, I am a green-horned newbie when it comes to clang, but even so I succeeded debugging the problem with some hints from Doug Gregor (on IRC ) in two hours. The fix arrived on short order after the conception of the solution idea. That I could get this working in a few hours is an astonishing feat (that I am pretty proud of) and a tell-tale aspect of clang's awesome design. Naturally, I still have to survive post-commit review, especially w.r.t. performance regressions; OTOH I am rather confident that I got the semantics right. Some loose ends in testing remain, which I hope to wrap up this weekend, so that I can see my application linking with clang (LLVM) on monday. That will burst up the doors towards static analysis ... Go CLANG! PS: Hopefully I won't need months to make this working ;-) Posted by heisenbug at 8:29 PM No comments: Labels: clang , llvm Wednesday, July 21, 2010 64-bit Waymarking Finally I came around working on the 64bit variant of my (array) waymarking algorithm, the result of which can be observer here (starting at line 77). But I'd like to provide some background first. Back when I implemented the original waymarking algorithm with a 2-bit alphabet used as the marks, I hoped that extending the alphabet to have 3 bits could be a major win. 64-bit pointers are by ABI rules aligned on an eight byte boundary, so pointers to these have their 3 lowest bits cleared, and I can use this space for jotting down the marks. With eight letters I can fully encode four digits and the two stops. This almost halves the number of accesses. The big question is how to assign a lucrative rôle to the remaining two characters! After some thinking I settled with the idea to make them valued stops. Clearly, increasing the frequency of stops reduces the chance of long linear searches. In the current incarnation 'x' carries a value of (binary) 01 at the start and at the end of a digit sequence, while 'y' carries 02 in the start rôle only. 's' is not carrying any value and is used when neither of the others fit. Since "s0" is a silly fragment to create, so I assign a special meaning of "s10" to it. I designed the decoder (d3code) first. It is essential that it obtains the correct length for the string tail wherever it starts out. And it should minimize the number of accesses to characters in the string. The decoding rules are taylored to only need maximally 4 accesses to compute the correct length for the last 12 characters. Actually the last couple of marks were a result of a co-evolution with the decoder's rules. In the front of this part the digit sequences become longer and there is less wiggle room, this part can be automatically generated. The code as it is now needs some serious cleanup, but it does QuickCheck and I am pretty confident that it is correct for all lengths. Of course you are encouraged to find a better scheme, but so far I am happy with it. PS: As I wrote this I discovered that I can eliminate another 2 characters of my hand-written seed string. PPS: I do not employ the 'x' terminates with a value rule in the generator yet, only in the hand-written seed. But it should be easy enough to change every "3sx" to "x" in the generator. Posted by heisenbug at 3:00 PM No comments: Labels: haskell , llvm , waymarking Wednesday, July 14, 2010 The Proof is in the Pudding Looks like I've finally done it! r108240 stuck and no broken external projects have been reported. I've prepared some little statistic and quietly celebrating the 1%+ speed gain of LLVM in the last week. Now on, plucking some more low-hanging fruit before adventuring into some more hard-core changes! Update: The ClangBSD project will surely put it through some serious regression testing... Posted by heisenbug at 4:12 PM No comments: Labels: bsd , llvm Thursday, June 24, 2010 Emacs the Lifesaver I was not thrilled of the task in front of me. Refreshing an old mega-patch, revise virtually every hunk to use a different interface, and committing it piecemeal to the repository again. Sounds like a long error prone job of suffering. Fortunately here is where the power tools come in. I re-merged the backed out revision, postponing conflicts; saved the diff away and reverted the repository; wrote a small awk script to massage the hunks in the diff to get a new patch; fired up emacs with the patch and applied each hunk after thorough review (and seldom with minor changes); some hunks are not ready to go in yet as they do not qualify as refactoring, these are kept for later; commit almost every file as a separate revision. I spend the most time in Emacs (the Mac OS X incarnation, Aquamacs is fantastic). It provides me all the comfort and productivity I need: it provides all necessary hunk operations such as apply, reverse, go to original, drop etc. I can transparently work from a remote machine via ssh, including editing, version control and the above diff operations peace of mind, by being rock solid and autosaving stuff. The only inconvenience is the sheer amount of keyboard equivalents, but I am getting used to them too. Thanks Emacs, without you I would probably drop! Posted by heisenbug at 7:55 AM No comments: Labels: emacs , llvm Tuesday, June 22, 2010 Burning ISO CDs I wasted some hours with trying to burn ISO CDs on the mac. I tried various methods like converting .dmg to .cdr (CD Master) in Disk Utility, but the resulting CD always mounted as HFS+. Finally I googled a nice method: hdiutil makehybrid -iso -o MyImage.iso /Volumes/SomeFolder/ will create an ISO filesystem, which can be burnt with Disk Utility and shows up like that in the Finder. That is - well, I am pretty sure - readable on PCs. Alternatively I may use hdiutil burn MyImage.iso I believe... In retrospect, some of my burn products may have ended up as PC-readable too, since hybrid filesystems may have been created. I'll test them on a PC tomorrow for sure. Posted by heisenbug at 5:24 PM No comments: Labels: filesystem , iso Friday, June 18, 2010 Sized types I have always liked the idea of assigning some notion of size to (tree-like) values, and track its changes along pattern matching and construction to be able to reason about termination-unaffecting recursive calls. Many years ago, when reading the Hughes-Pareto-Sabry paper I did not see the point yet why termination is fundamental in various aspects. Only when sitting on the park bench on the isle of Margitsziget (Budapest) and discussing with Tim about sound logic in Ωmega, it dawned to me how termination checking with sized types can be exploited. I developed the intuition of the tree-like data floating heads down in the water and we are reasoning about criteria that it can still float without touching the ground at depth n . Still, this metaphor was rather hazy. In the meantime I have tried to digest the relevant papers from Barthe and Abel, brainstormed somewhat here and let my brain background. Yesterday, I found (on reddit) a link to Abel's new MiniAgda implementation and its description. It made clear to me that my early intuition was not bad at all, the water depth is the upper limit of the size, and recursion is to reduce this to obtain a well-founded induction. Now it is time to rethink my ideas about infinite function types and how they can be reconciled with sized types. But it looks like Abel has done the hard work and his Haskell implementation of MiniAgda could be married with Ωmega in the following way: Derive a sized variant of every (suitable) Ωmega datatype and try to check which functions on them terminate. These can be used as theorems in Ωmega. Hopefully Tim is paying attention to this when implementing Trellys... Posted by heisenbug at 12:01 PM No comments: Labels: omega , termination , types Tuesday, June 8, 2010 My grief with out-of-tree code This post is a long-standing todo item in my brain, but this checkin actually prompted me to do it. A little bit of history first. As a software developer currently mostly active in the embedded space, I like solutions which allow me to save some CPU cycles or bytes of RAM here and there as long as they still allow me to use the same interfaces. Exploiting the characteristics of the underlying hardware and algorithms is often low-hanging fruit when it comes to optimizations. So I have this little agenda of about 10 items I wish to implement in the future to make the LLVM framework a little more efficient. One of these was to reorder the operands inside of the call instruction, to obtain faster access to the callee but mainly to allow fast visitation of all instructions that have a certain callee. I explained all my motives in a separate mail , so I want to save you from the gory details here. To make a long story short, it took me several iterations to catch all places in the optimizers where the operand order was assumed to be in the (callee, arg1, arg2, ...) fashion, instead of the new (arg1, arg2, ..., callee) one, and some miscompilations were only revealed by running the nightly tests. It was a work of blood and sweat because there are many intrinsics and transformations on them and they are often manipulating via the low-level interface getOperand(n) . Actually there is a nice helper interface, called CallSite , which makes it easy to access the call instruction's arguments in a high-level fashion and this interface probably the best for LLVM clients, since its also handles the invoke instructions. However, I regard it ok to use the low-level interface in the LLVM tree directly, since it is possible to consistently change things in one atomic commit. Finally, the day where all regression and nightly tests succeeded, has dawned. My patch seemingly stuck, with all buildbots green. I left for downtown and returned late at night. Just to discover that all has been backed out, because my change broke havoc in an Apple project that obviously used the low-level interface. This was especially frustrating, since I cannot even submit a correcting patch against that project. I did receive very little encouraging support, not even moral one. Some comments were even pretty dismissive, like this patch has already caused many problems, it is not worth it for such a marginal gain . I have no problem with the comment itself, since I would utter such words in comparable situations too, but this time it was my investment that was at stake. I was pretty determined to keep fighting. I wondered whether new measurements with higher arity calls would find a significant speedup with my patch applied. So I did some benchmarking for cases where the change is expected to make a difference, and actually found (roughly) a 3% speedup. Clearly this number is only achieved in specific situations, so the generic case would be well below that, but still it could compensate for many little time eaters that are necessary for an advanced optimization pass or analysis. In my conversation with the involved engineer I enumerated following reasons why resorting to low-level interface in out-of-tree projects is a bad idea: they are not conveying the intent they are depending on implementation details by reaching over abstraction barriers they are an impediment to change (these are mostly the same reasons which you can find in the above commit message too). He did agree to all this and promised to nudge the OpenGL implementors. I also received a request to submit a patch that guarantees that no silent breakage can happen. Well, I acknowledged that this is a valid concern, so I did some brainstorming. I succeeded to put together a small patch that detected all instances of get/setOperand(0) , the major potential cause of breakage in external projects. Compiling with this patch would pinpoint all places where getCalledValue() should be used. But I cannot promise more than that! Why it is impossible to guarantee that with my proposed change either everything keeps working or there is a compilation error with a clear fixing indication? Because the User baseclass does provide the low-level getOperand interface too and I cannot disallow that. C++ only lets me protect parts of the CallInst class... Would a patch to make getOperand private in CallInst be accepted? Probably not now, but read on. What aggravates the problem with private trees is file ownership. The engineer who detects the breakage is not entitled to fix simple cases, but needs to lobby the project/file owner first. This results in additional inertia. (Disclaimer: I am not sure whether Apple does have a file-ownership model internally.) Surprisingly the same thing that happened to me theoretically could happen to any Apple engineer too. Imagine some checkin to LLVM broke the dragonegg GCC plugin which is effectively licensed as GPLv3, so no Apple engineer is allowed to inspect its sources. What would happen if the dragonegg maintainer backed out the change on grounds of "broke an important external project"? What to do next? Now, whining is not one of the things I like to do, so let's advance in some way. Bill's patch I mentioned in the beginning is a possible first step, as I could rework a large portion of my patch in terms of getArgOperand(n-1) instead of getOperand(n-1) , without actually changing the operand order for now. These kinds of incremental refactorings that do not change functionality are mostly welcome in the LLVM world. Then I am dependent on the goodwill of some Apple engineer to make a similar change in that internal project too. Finally the switch (i.e. the operand order) could be flipped. Why I am reluctant to begin? Because it is lots of work, many new intrinsics have been introduced, I definitely will get a bunch of merge conflicts, and finally, who knows, there might be another internal project that chokes and the whole misery enters a new iteration. Why do I feel that the change is urgent? Because LLVM is getting popular with an extraordinal speed. As more and more external projects use LLVM as a foundation, more and more code will exhibit bad habits of using low-level interfaces. The few post-v2.7 months are probably the last chance to make the switch in argument order, before things become de-facto cemented. Maybe it is too late already. That would be a pity, though, LLVM as a compilation infrastructure should be as fast and nimble as possible. Every one of its clients would profit. So, dear external tree developers, I hope you get rid of the low-level calls and use the high-level ones instead. It should not cost you more than touching a couple of lines and retesting. I would be happy to assist you. Regarding development policy, I would welcome a clear statement about what amount of testing in the LLVM ecosystem is "sufficient" and excludes the risk of a patch being backed out. Bottom line, I'd love to get this patch wrapped up, but I am dependent on the support of external tree owners. Are you willing to help me? Posted by heisenbug at 3:23 AM No comments: Labels: llvm Wednesday, November 25, 2009 Patrícia's New Hobby The artistic blood of my lovely wife is flowing again :-) Her newest hobby is orchestrating photo-shootings. Predominantly of pregnant friends and everybody who simply wants to feel marvelous... Like Lelêca! Posted by heisenbug at 2:45 PM No comments: Labels: family Monday, November 2, 2009 Freude, die man sieht Dieses Photo zeigt Lelêca (alias MausiMausi, alias SchlausiMausi) in mit einem Kopfschmuck, der eigentlich zur pernambucanischen Tracht gehört. Ein Geschenk von Tio Davis – Danke! Lelê freut sich inzwischen auf den morgentlichen Gang in den Kindergarten (natürlich mit Papa!) und scheut sich auch nicht vor kleineren Wortgefechten ("vai comer não!"). Aber was richtig gut ist heißt dann "muito ótimo" und Akzeptanz wird mit einem klaren "tá certo!" signalisiert. Und wie man sieht, geht es den Jungs auch ganz passabel... Posted by heisenbug at 3:47 PM No comments: Labels: family Thursday, October 1, 2009 New Thrist Cabbage Yeah, it took more than a year (and dcoutts help on IRC), but finally I've gathered all my hackage-foo to submit a new thrist package (v1.1.1). Its main purpose is to require base v4.0 or higher. As an added bonus (Thrist p) now provides a Category instance. I have also added an Arrow (Thrist (->)) instance, but its first method is bogus as of now. I plan to correct this with v1.1.2. My plans for 0.2 are: adaptors Data.Thrist.Monad , Data.Thrist.List (aka. R*), Data.Thrist.Arrow , all with their respective sensible class instances, tests. Then sometime I can start setting up some cool stuff to demonstrate hoare-triples in thrist setting. We'll see. Posted by heisenbug at 2:37 PM No comments: Labels: thrist Tuesday, August 4, 2009 Static Constraints In the last months Tim has been adding a new function sameLabel to Ωmega and this finally allowed me to encode the concept of free variables. In just a couple of days I managed to implement environment construction with statically checked proof that no identifier is shadowed. Here is a little example. Building on this advance I fulfilled a long lasting desire and managed to prototype LLVM basic blocks in Ωmega with thrists. The approach is implemented in 2 steps: build up a labelled sequence of preinstructions, and then construct sufficient evidence about well-formedness, that the strict type constraints in the thrist can be proven. Curiously, the defs propagate to the right and the uses to the right in this thrist. The good thing is, that after all this struggle I am pretty confident that many more properties and constraints can be encoded, such as the LLVM type system (on defs, uses and constants), that Phi nodes must not go into entry blocks, that Phi nodes must preceed other instructions in the basic block, every use must happen in the scope of a corresponding def, etc. The next days will surely see more progress, I have crawled out of the swamp and have firm ground under my feet... Posted by heisenbug at 3:52 PM No comments: Labels: llvm , omega , thrist Sunday, June 14, 2009 Daddy's Girl Das Bild zeigt die Ruhe vor dem Sturm. Wenige Minuten später ist Leleka in ihren Festanzug geschlüpft und die Party ging los, mit Geschenken und viel Leckerem. Spruch der letzten Woche: "Aniversário de Lelêca no domingo!" Posted by heisenbug at 2:56 PM No comments: Labels: family Wednesday, May 27, 2009 Ketchup Problem In Chapter 6 (page 16) Jeremy Gibbons describes a datatype that models all secure operations that can be applied to a (partially filled) ketchup bottle . I believe that this is the example that Jeremy has shown me at ICFP'07 in Freiburg (when I have introduced him to my thrist concept), and I have been unable to find it ever since. Now, I guess I can add it to the bibliography section of my paper. That is, if I ever get around updating the draft again... PS: a bibtex-able conference paper is here . Posted by heisenbug at 6:43 AM No comments: Labels: thrist Tuesday, March 31, 2009 Sieben Tage Regen, Sieben Tage Schnee … … und es tut nicht mehr weh! Dieser Winter war der schmerzhafteste den ich bisher in Deutschland erlebt habe. Lang und kalt. Die Natur ist acht Wochen (oder mehr?) hinterher, unser Hunger nach Sonne unvorstellbar. Wie gut, daß mein Wetter-Widget jetzt sieben Tage Sonne und angenehme Temperaturen verspricht! Das Haus ist nunmehr tiptop eingerichtet, die Gartensaison kann kommen. Auf wiedersehen, Winter, willkommen Frühling! Posted by heisenbug at 10:15 PM No comments: Labels: family , garden , weather Newer Posts Older Posts Home Subscribe to: Comments (Atom) Blog Archive ▼  2022 (1) ▼  February (1) Pattern musings ►  2014 (5) ►  November (1) ►  October (1) ►  August (1) ►  July (1) ►  January (1) ►  2013 (5) ►  September (1) ►  August (3) ►  February (1) ►  2012 (2) ►  December (1) ►  September (1) ►  2011 (7) ►  December (1) ►  November (1) ►  October (1) ►  September (1) ►  August (1) ►  February (1) ►  January (1) ►  2010 (19) ►  December (5) ►  November (6) ►  October (1) ►  August (1) ►  July (2) ►  June (4) ►  2009 (12) ►  November (2) ►  October (1) ►  August (1) ►  June (1) ►  May (1) ►  March (4) ►  January (2) ►  2008 (22) ►  October (1) ►  September (3) ►  August (6) ►  July (3) ►  June (2) ►  May (1) ►  April (3) ►  March (1) ►  February (1) ►  January (1) ►  2007 (20) ►  December (2) ►  November (1) ►  October (1) ►  September (1) ►  August (1) ►  July (14) About Me heisenbug I am here and there. You may encounter me if you try, but no guarantees. Just a hint: I am mostly with my family. View my complete profile   | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/preprocessor/ | Preprocessor | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Write an Extension Preprocessor 3.0 3.0 2.5 Edit this Page Preprocessor Preprocessors allow to process the raw asciidoctor sources before Asciidoctor parses and converts them. A preprocessor could for example make comments visible that should be rendered in drafts. Our example preprocessor does exactly that and will render the comment in the following document as a note. comment.adoc Normal content. //// RP: This is a comment and should only appear in draft documents //// The preprocessor will render the document as if it looked like this: comment-with-note.adoc Normal content. [NOTE] -- RP: This is a comment and should only appear in draft documents -- The implementation of the preprocessor simply gets the AST node for the document to be created as well as a PreprocessorReader . A PreprocessorReader gives access to the raw input, on a per-line basis, allowing to fetch and manipulate content. And this is exactly what our Preprocessor does: it fetches the raw content, modifies it and stores it back so that Asciidoctor will only see our modified content. A Preprocessor that renders comments as notes import org.asciidoctor.ast.Document; import org.asciidoctor.extension.Preprocessor; import org.asciidoctor.extension.PreprocessorReader; import org.asciidoctor.extension.Reader; import java.util.ArrayList; import java.util.List; public class CommentPreprocessor extends Preprocessor { (1) @Override public Reader process(Document document, PreprocessorReader reader) { List<String> lines = reader.readLines(); (2) List<String> newLines = new ArrayList<String>(); boolean inComment = false; for (String line: lines) { (3) if (line.trim().equals("////")) { if (!inComment) { newLines.add("[NOTE]"); } newLines.add("--"); inComment = !inComment; } else { newLines.add(line); } } return newReader(newLines); (4) } } 1 All Preprocessors must extend the class org.asciidoctor.extension.Preprocessor and implement the method process() . 2 The implementation gets the whole Asciidoctor source as an array of Strings where each entry corresponds to one line. 3 Every odd occurrence of a comment start is replaced by opening an admonition block, every even occurrence is closing it. The new content is collected in a new list. 4 A new Reader containing the processed content is returned so that it replaces the content that was already consumed at the beginning of the method. There may be multiple Preprocessors registered and every Preprocessor will be called. The order in which the Preprocessors are called is undefined so that all Preprocessors should be independent of each other. Include Processor Postprocessor Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
http://heisenbug.blogspot.com/search?updated-max=2010-07-14T16:12:00-07:00#main | don't count on finding me skip to main | skip to sidebar don't count on finding me Thursday, June 24, 2010 Emacs the Lifesaver I was not thrilled of the task in front of me. Refreshing an old mega-patch, revise virtually every hunk to use a different interface, and committing it piecemeal to the repository again. Sounds like a long error prone job of suffering. Fortunately here is where the power tools come in. I re-merged the backed out revision, postponing conflicts; saved the diff away and reverted the repository; wrote a small awk script to massage the hunks in the diff to get a new patch; fired up emacs with the patch and applied each hunk after thorough review (and seldom with minor changes); some hunks are not ready to go in yet as they do not qualify as refactoring, these are kept for later; commit almost every file as a separate revision. I spend the most time in Emacs (the Mac OS X incarnation, Aquamacs is fantastic). It provides me all the comfort and productivity I need: it provides all necessary hunk operations such as apply, reverse, go to original, drop etc. I can transparently work from a remote machine via ssh, including editing, version control and the above diff operations peace of mind, by being rock solid and autosaving stuff. The only inconvenience is the sheer amount of keyboard equivalents, but I am getting used to them too. Thanks Emacs, without you I would probably drop! Posted by heisenbug at 7:55 AM No comments: Labels: emacs , llvm Tuesday, June 22, 2010 Burning ISO CDs I wasted some hours with trying to burn ISO CDs on the mac. I tried various methods like converting .dmg to .cdr (CD Master) in Disk Utility, but the resulting CD always mounted as HFS+. Finally I googled a nice method: hdiutil makehybrid -iso -o MyImage.iso /Volumes/SomeFolder/ will create an ISO filesystem, which can be burnt with Disk Utility and shows up like that in the Finder. That is - well, I am pretty sure - readable on PCs. Alternatively I may use hdiutil burn MyImage.iso I believe... In retrospect, some of my burn products may have ended up as PC-readable too, since hybrid filesystems may have been created. I'll test them on a PC tomorrow for sure. Posted by heisenbug at 5:24 PM No comments: Labels: filesystem , iso Friday, June 18, 2010 Sized types I have always liked the idea of assigning some notion of size to (tree-like) values, and track its changes along pattern matching and construction to be able to reason about termination-unaffecting recursive calls. Many years ago, when reading the Hughes-Pareto-Sabry paper I did not see the point yet why termination is fundamental in various aspects. Only when sitting on the park bench on the isle of Margitsziget (Budapest) and discussing with Tim about sound logic in Ωmega, it dawned to me how termination checking with sized types can be exploited. I developed the intuition of the tree-like data floating heads down in the water and we are reasoning about criteria that it can still float without touching the ground at depth n . Still, this metaphor was rather hazy. In the meantime I have tried to digest the relevant papers from Barthe and Abel, brainstormed somewhat here and let my brain background. Yesterday, I found (on reddit) a link to Abel's new MiniAgda implementation and its description. It made clear to me that my early intuition was not bad at all, the water depth is the upper limit of the size, and recursion is to reduce this to obtain a well-founded induction. Now it is time to rethink my ideas about infinite function types and how they can be reconciled with sized types. But it looks like Abel has done the hard work and his Haskell implementation of MiniAgda could be married with Ωmega in the following way: Derive a sized variant of every (suitable) Ωmega datatype and try to check which functions on them terminate. These can be used as theorems in Ωmega. Hopefully Tim is paying attention to this when implementing Trellys... Posted by heisenbug at 12:01 PM No comments: Labels: omega , termination , types Tuesday, June 8, 2010 My grief with out-of-tree code This post is a long-standing todo item in my brain, but this checkin actually prompted me to do it. A little bit of history first. As a software developer currently mostly active in the embedded space, I like solutions which allow me to save some CPU cycles or bytes of RAM here and there as long as they still allow me to use the same interfaces. Exploiting the characteristics of the underlying hardware and algorithms is often low-hanging fruit when it comes to optimizations. So I have this little agenda of about 10 items I wish to implement in the future to make the LLVM framework a little more efficient. One of these was to reorder the operands inside of the call instruction, to obtain faster access to the callee but mainly to allow fast visitation of all instructions that have a certain callee. I explained all my motives in a separate mail , so I want to save you from the gory details here. To make a long story short, it took me several iterations to catch all places in the optimizers where the operand order was assumed to be in the (callee, arg1, arg2, ...) fashion, instead of the new (arg1, arg2, ..., callee) one, and some miscompilations were only revealed by running the nightly tests. It was a work of blood and sweat because there are many intrinsics and transformations on them and they are often manipulating via the low-level interface getOperand(n) . Actually there is a nice helper interface, called CallSite , which makes it easy to access the call instruction's arguments in a high-level fashion and this interface probably the best for LLVM clients, since its also handles the invoke instructions. However, I regard it ok to use the low-level interface in the LLVM tree directly, since it is possible to consistently change things in one atomic commit. Finally, the day where all regression and nightly tests succeeded, has dawned. My patch seemingly stuck, with all buildbots green. I left for downtown and returned late at night. Just to discover that all has been backed out, because my change broke havoc in an Apple project that obviously used the low-level interface. This was especially frustrating, since I cannot even submit a correcting patch against that project. I did receive very little encouraging support, not even moral one. Some comments were even pretty dismissive, like this patch has already caused many problems, it is not worth it for such a marginal gain . I have no problem with the comment itself, since I would utter such words in comparable situations too, but this time it was my investment that was at stake. I was pretty determined to keep fighting. I wondered whether new measurements with higher arity calls would find a significant speedup with my patch applied. So I did some benchmarking for cases where the change is expected to make a difference, and actually found (roughly) a 3% speedup. Clearly this number is only achieved in specific situations, so the generic case would be well below that, but still it could compensate for many little time eaters that are necessary for an advanced optimization pass or analysis. In my conversation with the involved engineer I enumerated following reasons why resorting to low-level interface in out-of-tree projects is a bad idea: they are not conveying the intent they are depending on implementation details by reaching over abstraction barriers they are an impediment to change (these are mostly the same reasons which you can find in the above commit message too). He did agree to all this and promised to nudge the OpenGL implementors. I also received a request to submit a patch that guarantees that no silent breakage can happen. Well, I acknowledged that this is a valid concern, so I did some brainstorming. I succeeded to put together a small patch that detected all instances of get/setOperand(0) , the major potential cause of breakage in external projects. Compiling with this patch would pinpoint all places where getCalledValue() should be used. But I cannot promise more than that! Why it is impossible to guarantee that with my proposed change either everything keeps working or there is a compilation error with a clear fixing indication? Because the User baseclass does provide the low-level getOperand interface too and I cannot disallow that. C++ only lets me protect parts of the CallInst class... Would a patch to make getOperand private in CallInst be accepted? Probably not now, but read on. What aggravates the problem with private trees is file ownership. The engineer who detects the breakage is not entitled to fix simple cases, but needs to lobby the project/file owner first. This results in additional inertia. (Disclaimer: I am not sure whether Apple does have a file-ownership model internally.) Surprisingly the same thing that happened to me theoretically could happen to any Apple engineer too. Imagine some checkin to LLVM broke the dragonegg GCC plugin which is effectively licensed as GPLv3, so no Apple engineer is allowed to inspect its sources. What would happen if the dragonegg maintainer backed out the change on grounds of "broke an important external project"? What to do next? Now, whining is not one of the things I like to do, so let's advance in some way. Bill's patch I mentioned in the beginning is a possible first step, as I could rework a large portion of my patch in terms of getArgOperand(n-1) instead of getOperand(n-1) , without actually changing the operand order for now. These kinds of incremental refactorings that do not change functionality are mostly welcome in the LLVM world. Then I am dependent on the goodwill of some Apple engineer to make a similar change in that internal project too. Finally the switch (i.e. the operand order) could be flipped. Why I am reluctant to begin? Because it is lots of work, many new intrinsics have been introduced, I definitely will get a bunch of merge conflicts, and finally, who knows, there might be another internal project that chokes and the whole misery enters a new iteration. Why do I feel that the change is urgent? Because LLVM is getting popular with an extraordinal speed. As more and more external projects use LLVM as a foundation, more and more code will exhibit bad habits of using low-level interfaces. The few post-v2.7 months are probably the last chance to make the switch in argument order, before things become de-facto cemented. Maybe it is too late already. That would be a pity, though, LLVM as a compilation infrastructure should be as fast and nimble as possible. Every one of its clients would profit. So, dear external tree developers, I hope you get rid of the low-level calls and use the high-level ones instead. It should not cost you more than touching a couple of lines and retesting. I would be happy to assist you. Regarding development policy, I would welcome a clear statement about what amount of testing in the LLVM ecosystem is "sufficient" and excludes the risk of a patch being backed out. Bottom line, I'd love to get this patch wrapped up, but I am dependent on the support of external tree owners. Are you willing to help me? Posted by heisenbug at 3:23 AM No comments: Labels: llvm Wednesday, November 25, 2009 Patrícia's New Hobby The artistic blood of my lovely wife is flowing again :-) Her newest hobby is orchestrating photo-shootings. Predominantly of pregnant friends and everybody who simply wants to feel marvelous... Like Lelêca! Posted by heisenbug at 2:45 PM No comments: Labels: family Monday, November 2, 2009 Freude, die man sieht Dieses Photo zeigt Lelêca (alias MausiMausi, alias SchlausiMausi) in mit einem Kopfschmuck, der eigentlich zur pernambucanischen Tracht gehört. Ein Geschenk von Tio Davis – Danke! Lelê freut sich inzwischen auf den morgentlichen Gang in den Kindergarten (natürlich mit Papa!) und scheut sich auch nicht vor kleineren Wortgefechten ("vai comer não!"). Aber was richtig gut ist heißt dann "muito ótimo" und Akzeptanz wird mit einem klaren "tá certo!" signalisiert. Und wie man sieht, geht es den Jungs auch ganz passabel... Posted by heisenbug at 3:47 PM No comments: Labels: family Thursday, October 1, 2009 New Thrist Cabbage Yeah, it took more than a year (and dcoutts help on IRC), but finally I've gathered all my hackage-foo to submit a new thrist package (v1.1.1). Its main purpose is to require base v4.0 or higher. As an added bonus (Thrist p) now provides a Category instance. I have also added an Arrow (Thrist (->)) instance, but its first method is bogus as of now. I plan to correct this with v1.1.2. My plans for 0.2 are: adaptors Data.Thrist.Monad , Data.Thrist.List (aka. R*), Data.Thrist.Arrow , all with their respective sensible class instances, tests. Then sometime I can start setting up some cool stuff to demonstrate hoare-triples in thrist setting. We'll see. Posted by heisenbug at 2:37 PM No comments: Labels: thrist Tuesday, August 4, 2009 Static Constraints In the last months Tim has been adding a new function sameLabel to Ωmega and this finally allowed me to encode the concept of free variables. In just a couple of days I managed to implement environment construction with statically checked proof that no identifier is shadowed. Here is a little example. Building on this advance I fulfilled a long lasting desire and managed to prototype LLVM basic blocks in Ωmega with thrists. The approach is implemented in 2 steps: build up a labelled sequence of preinstructions, and then construct sufficient evidence about well-formedness, that the strict type constraints in the thrist can be proven. Curiously, the defs propagate to the right and the uses to the right in this thrist. The good thing is, that after all this struggle I am pretty confident that many more properties and constraints can be encoded, such as the LLVM type system (on defs, uses and constants), that Phi nodes must not go into entry blocks, that Phi nodes must preceed other instructions in the basic block, every use must happen in the scope of a corresponding def, etc. The next days will surely see more progress, I have crawled out of the swamp and have firm ground under my feet... Posted by heisenbug at 3:52 PM No comments: Labels: llvm , omega , thrist Sunday, June 14, 2009 Daddy's Girl Das Bild zeigt die Ruhe vor dem Sturm. Wenige Minuten später ist Leleka in ihren Festanzug geschlüpft und die Party ging los, mit Geschenken und viel Leckerem. Spruch der letzten Woche: "Aniversário de Lelêca no domingo!" Posted by heisenbug at 2:56 PM No comments: Labels: family Wednesday, May 27, 2009 Ketchup Problem In Chapter 6 (page 16) Jeremy Gibbons describes a datatype that models all secure operations that can be applied to a (partially filled) ketchup bottle . I believe that this is the example that Jeremy has shown me at ICFP'07 in Freiburg (when I have introduced him to my thrist concept), and I have been unable to find it ever since. Now, I guess I can add it to the bibliography section of my paper. That is, if I ever get around updating the draft again... PS: a bibtex-able conference paper is here . Posted by heisenbug at 6:43 AM No comments: Labels: thrist Tuesday, March 31, 2009 Sieben Tage Regen, Sieben Tage Schnee … … und es tut nicht mehr weh! Dieser Winter war der schmerzhafteste den ich bisher in Deutschland erlebt habe. Lang und kalt. Die Natur ist acht Wochen (oder mehr?) hinterher, unser Hunger nach Sonne unvorstellbar. Wie gut, daß mein Wetter-Widget jetzt sieben Tage Sonne und angenehme Temperaturen verspricht! Das Haus ist nunmehr tiptop eingerichtet, die Gartensaison kann kommen. Auf wiedersehen, Winter, willkommen Frühling! Posted by heisenbug at 10:15 PM No comments: Labels: family , garden , weather Saturday, March 21, 2009 Lack of Total Order My new project is starting to bind my mental resources at work. So some of the fringe projects which I casually do for fun will surely suffer. LLVM: Two of my recent patches had to be backed out of the tree, because they caused trouble with bootstrapping llvm-gcc. I am pretty sure these are not caused by bugs on my side (geee!), but frustrating nevertheless. The situation is also aggravated by the fact that I am unable to build a stock llvm-gcc on my Tiger machines I have access to, so I have lost my ability to debug these beasts. A third patch is in-progress (CallInst operand reorg - function to the back) but it is dependent on one of the backed-out ones. It is also pretty stubborn, since there are many hidden assumptions in the codebase which expect the callee in front position. I am slowly weeding out the problems. Omega: Little progress on this front. Tim also seems to have reduced his workload on here - probably caused by the "Cyber Milennium" course - so I do not feel a lot of motivation. Which is sad, because there are some nice papers on GADT decidable type inference appearing. Omega could benefit from those. Clang: Doug has been working on the template instantiation machinery lately, and I took over a mini-project: instantiation of "?:" expressions. It mostly works, but there is still review feedback to satisfy and the missing middle-expression problem needs a solution. These must be unit-tested as well. Back to my regular work. The job is demanding, I co-develop the implementation, test framework and test-suite simultaneously. Of course I could accept some help, but it is also important that the basics get in right and unwatered. I have a nice plan for stub-libraries that can invoke TCL commands to fill in out parameters and result values. Fun. Regarding the headline, it was inspired by thinking about a purely-functional (i.e. immutable) lattice library for use by Clang's (partial) template specialization feature. Yes, and lattices arise as containers of partially-ordered data. Posted by heisenbug at 3:04 PM No comments: Labels: clang , haskell , llvm , work Wednesday, March 11, 2009 RWH I am happy because my copy of Real World Haskell arrived today. I ordered it through my employer, and while waiting for it more than two months, it finally got delivered. Anyway, I plan to put QuickCheck to good use by generating testcases automatically. Let's see how far this can carry us. Posted by heisenbug at 5:05 AM No comments: Labels: haskell , work Tuesday, March 3, 2009 3^2 Day Today is 3^2 day, because 3 squared is 9 and today's date is 03.03.09. Number jokes aside, it was a good day, I am finally beginning the implementation part of my new project at work and the ideas keep sprouting. Good. PS.: Also I found a nice article about decidable type inference for GADTs. Final version hopefully for ICFP09! Posted by heisenbug at 2:55 PM No comments: Labels: GADT , good Friday, January 30, 2009 Verhörhämmer Um ein Paar dieser "rohen Diamanten" zu downloaden, habe ich dieses kleine tcsh script geschrieben: foreach j ( 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 ) foreach i ( `curl "http://blog.br-online.de/fruehaufdreher/index.php?/categories/2-Verhoerhammer/P"$j".html" | grep .mp3 | grep value= | grep song_title= | awk -F= '{print $4}' | awk -F"&" '{print $1}' | awk -F/ '{print $6}' ` ) echo $j : $i curl http://blog.br-online.de/fruehaufdreher/uploads/$i > $i end end Macht Spaß... Danke BR! :-) Posted by heisenbug at 4:27 PM No comments: Wednesday, January 28, 2009 Dan's Birthday Yesterday was Daniel's birthday. We made a surprise visit and he loved it! I came a bit late (work, work, new project, yadda), which was no problem because people had lots of fun. They fired up the karaoke machine, and after some beers even I took the mike. But Helena on stage was the cutest thing ever! She grabbed the microphone as if she was a seasoned singer. However she did not sing a single tune, just posed :-) Posted by heisenbug at 3:27 PM No comments: Labels: family Thursday, October 9, 2008 Hauskauf Heute war doch ein recht spezieller Tag. Notartermin zwecks Vertragsunterzeichnung. Ich kann nur sagen daß mein Herz doch ziemlich in die Hose geruscht ist... ...noch nie habe ich so eine Menge Geld auf eine Karte gesetzt. Als nächstes nun wird bezahlt und dann beginnt der lange, schweißtreibende Weg zur Tilgung. Darüber später mehr. Posted by heisenbug at 9:30 AM No comments: Labels: family , house Wednesday, September 10, 2008 Hoare Triples and Thrists While mousing through the L4.verified presentation that took place at Galois , I could not help but build an association bridge between Hoare triples and thrists. Especially when you go to p. 52 and thereabout. Here is my take on the connection: We have some command s that belong to a data type C , and C has two type parameters: data C :: * -> * -> * where C1 :: ... -> C a b The first type parameter can be interpreted as the precondition of the command while the second as its postcondition ({P} and {Q} in Hoare's notation). This convention employs the types-as-properties interpretation. If commands are sequenced, the postconditions of the former commands must imply the preconditions of the latter. This is referred to as the composition rule and corresponds to appending two thrists. Now, in Ωmega the situation is even prettier, because C need not be a two-type-parameter entity, but can be parameterized over arbitrary kind s. The built-in evaluation mechanism (type functions) allow the most powerful constructs. (Haskell will get something similar at the type level, called type families , with GHC v6.10.) Posted by heisenbug at 12:54 PM No comments: Labels: haskell , hoare-triple , omega , thrist Wednesday, September 3, 2008 Saudades É muito bom ficar sozinho alguns dias, pensando e trabalhando em paz. Mas quando as semanas passam a distância parece que aumenta e a ausência começa de doer. Meus amores sinto muito falta de voces, quero que voltam logo. Posted by heisenbug at 12:22 PM No comments: Labels: family Monday, September 1, 2008 Meme evolution While I am missing family induced distraction, I use the opportunity of reading old papers that I always wanted to revisit. Yesterday, while reading "A History of Haskell" I was amused by the sentence: "Wadler misunderstood what Fasel had in mind, and type classes were born!" This is a concrete case of "meme evolution" (in Dawkins ' sense): a mutation of a meme (by transcription error) finds a new habitat where it thrives and blossoms. Some preconditions are needed for this to happen: communication loosening of amorphous ideas an open mind, not shying away from listening to the unknown Many great ideas come to me while reading conference papers of others and where I have no idea what they are talking about :-) While trying to make vague sense of what I have in front of me a fireworks of ideas commence, all building in some way on foundations of things (pet projects) I have done in the past. Now, how can I ensure that I periodically can enjoy the state of minimal disturbances? Posted by heisenbug at 9:38 AM No comments: Labels: evolution , haskell , philosophy Newer Posts Older Posts Home Subscribe to: Comments (Atom) Blog Archive ▼  2022 (1) ▼  February (1) Pattern musings ►  2014 (5) ►  November (1) ►  October (1) ►  August (1) ►  July (1) ►  January (1) ►  2013 (5) ►  September (1) ►  August (3) ►  February (1) ►  2012 (2) ►  December (1) ►  September (1) ►  2011 (7) ►  December (1) ►  November (1) ►  October (1) ►  September (1) ►  August (1) ►  February (1) ►  January (1) ►  2010 (19) ►  December (5) ►  November (6) ►  October (1) ►  August (1) ►  July (2) ►  June (4) ►  2009 (12) ►  November (2) ►  October (1) ►  August (1) ►  June (1) ►  May (1) ►  March (4) ►  January (2) ►  2008 (22) ►  October (1) ►  September (3) ►  August (6) ►  July (3) ►  June (2) ►  May (1) ►  April (3) ►  March (1) ►  February (1) ►  January (1) ►  2007 (20) ►  December (2) ►  November (1) ►  October (1) ►  September (1) ►  August (1) ►  July (14) About Me heisenbug I am here and there. You may encounter me if you try, but no guarantees. Just a hint: I am mostly with my family. View my complete profile   | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/ruby-extensions/ | Register a Ruby Extension | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Usage Register a Ruby Extension 3.0 3.0 2.5 Edit this Page Register a Ruby Extension You can even register extensions written in Ruby using AsciidoctorJ. To register a Ruby extension you must get a RubyExtensionRegistry class instead of JavaExtensionRegistry . Register a Ruby extension in Java RubyExtensionRegistry rubyExtensionRegistry = this.asciidoctor.rubyExtensionRegistry(); (1) rubyExtensionRegistry.loadClass(Class.class.getResourceAsStream("/YellRubyBlock.rb")).block("rubyyell", "YellRubyBlock"); (2) String content = asciidoctor.convertFile(new File( "target/test-classes/sample-with-ruby-yell-block.ad"), Opions.builder().toFile(false).build()); 1 rubyExtensionRegistry method is called to get a RubyExtensionRegistry instance. 2 Ruby file containing a class implementing a Block extension is loaded inside the Ruby runtime. Then the block is registered with a name (rubyyell), and we pass the name of the class to be instantiated. YellBlock.rb require 'asciidoctor' require 'asciidoctor/extensions' class YellRubyBlock < Asciidoctor::Extensions::BlockProcessor option :contexts, [:paragraph] option :content_model, :simple def process parent, reader, attributes lines = reader.lines.map {|line| line.upcase.gsub(/\.( |$)/, '!\\1') } Asciidoctor::Block.new parent, :paragraph, :source => lines, :attributes => attributes end end Ruby Runtime Logs Handling API Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/erubi/actions/workflows/ci.yml | CI · Workflow runs · jeremyevans/erubi · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / erubi Public Notifications You must be signed in to change notification settings Fork 22 Star 380 Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights Actions: jeremyevans/erubi Actions --> All workflows Workflows CI CI Show more workflows... Management Caches CI CI Actions Loading... Loading Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> will be ignored since log searching is not yet available Show workflow options Create status badge Create status badge Loading Uh oh! There was an error while loading. Please reload this page . ci.yml --> will be ignored since log searching is not yet available 8 workflow runs 8 workflow runs Event Filter by Event Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching events. Status Filter by Status Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching statuses. Branch Filter by Branch Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching branches. Actor Filter by Actor Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching users. Add Ruby 4.0 to CI CI #49: Commit 1ff124e pushed by jeremyevans 12m 33s master master 12m 33s View workflow file Use SimpleCov.add_filter block instead of string CI #48: Commit f3c93cc pushed by jeremyevans 52s master master 52s View workflow file Add JRuby 10.0 to CI CI #47: Commit 62e85a8 pushed by jeremyevans 5m 40s master master 5m 40s View workflow file Switch rdoc task to normal rake task, avoid rdoc/task require CI #46: Commit 33a677c pushed by jeremyevans 1m 1s master master 1m 1s View workflow file CI CI #45: by jeremyevans 58s master master 58s View workflow file Add Ruby 3.4 to CI CI #44: Commit 8cefe2a pushed by jeremyevans 1m 15s master master 1m 15s View workflow file Bump version to 1.13.1 CI #43: Commit f1a0fb5 pushed by jeremyevans 57s master master 57s View workflow file Use -W:strict_unused_block when running tests on Ruby 3.4+ CI #42: Commit aeae5e7 pushed by jeremyevans 48s master master 48s View workflow file You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/block-processor/ | Block Processor | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Write an Extension Block Processor 3.0 3.0 2.5 Edit this Page Block Processor A block processor is very similar to a block macro processor. But in contrast to a block macro a block processor is called for a block having a certain name instead of a macro invocation. Therefore block processors rather transform blocks instead of creating them as block macro processors do. The following example shows a block processor that converts the whole text of a block to upper case if it has the name yell . That means that our block processor will convert blocks like this: yell-block.adoc [yell] I really mean it After the processing this block will look like this I REALLY MEAN IT The BlockProcessor looks like this: A BlockProcessor that transforms the content of a block to upper case @Name("yell") (1) @Contexts({Contexts.PARAGRAPH}) (2) @ContentModel(ContentModel.SIMPLE) (3) public class YellBlockProcessor extends BlockProcessor { (4) @Override public Object process( (5) StructuralNode parent, Reader reader, Map<String, Object> attributes) { String content = reader.read(); String yellContent = content.toUpperCase(); return createBlock(parent, "paragraph", yellContent, attributes); } } 1 The annotation @Name defines the block name that this block processor handles. 2 The annotation @Contexts defines the block types that this block processor handles like paragraphs, listing blocks, or open blocks. Constants for all contexts are also defined in this annotation. Note that this annotation takes a list of block types, so that a block processor can process paragraph blocks as well as example blocks with the same block name. 3 The annotation @ContentModel defines what this processor produces. Constants for all contexts are also defined for the annotation class. In this case the block processor creates a simple paragraph, therefore the content model ContentModel.SIMPLE is defined. 4 All block processors must extend org.asciidoctor.extension.BlockProcessor . 5 A block processor must implement the method process() . Here the implementation gets the raw block content from the reader, transforms it and creates and returns a new block that contains the transformed content. Attributes Block Processors receive attributes in their process() method. These attributes contain the additional key value pairs that were applied to the block. You can read more about element attributes in general in the AsciiDoc documentation . If we convert the following document: yell-block-attributes.adoc [yell,loudness=3] I really mean it Then a Block Processor can access the attribute loudness like this: YellBlockProcessorWithAttributes.java @Name("yell") @Contexts({Contexts.PARAGRAPH}) @ContentModel(ContentModel.SIMPLE) public class YellBlockProcessorWithAttributes extends BlockProcessor { @Override public Object process( StructuralNode parent, Reader reader, Map<String, Object> attributes) { String content = reader.read(); String yellContent = content.toUpperCase(); String loudness = (String) attributes.get("loudness"); (1) if (loudness != null) { yellContent += IntStream.range(0, Integer.parseInt(loudness)) .mapToObj(i -> "!") .collect(joining()); } return createBlock(parent, "paragraph", yellContent, attributes); } } 1 Attribute values from the source document are usually Strings. Positional attributes Besides defining attributes as key value pairs like in [yell,loudness=3] AsciiDoc also supports positional attributes. For positional attributes the meaning is implicitly derived from the position in the attribute list. In our example the attribute loudness might be defined as the first positional attribute after the block style: yell-block-positional.adoc [yell,5] I really mean it Then a Block Processor can access the attribute loudness like this: YellBlockProcessorWithPositionalAttributes.java @Name("yell") @PositionalAttributes({"loudness"}) (1) @Contexts({Contexts.PARAGRAPH}) @ContentModel(ContentModel.SIMPLE) public class YellBlockProcessorWithPositionalAttributes extends BlockProcessor { @Override public Object process( StructuralNode parent, Reader reader, Map<String, Object> attributes) { String content = reader.read(); String yellContent = content.toUpperCase(); String loudness = (String) attributes.get("loudness"); (2) if (loudness != null) { yellContent += IntStream.range(0, Integer.parseInt(loudness)) .mapToObj(i -> "!") .collect(joining()); } return createBlock(parent, "paragraph", yellContent, attributes); } } 1 The attribute names defined in the annotation reflect the attribute positions, i.e., loudness is the first positional attribute. A second attribute exclamationmark would be defined as @PositionalAttributes({"loudness", "exclamationmark"}) so that the Block Processor can access the attributes of the block defined with [yell,3,"¡"] . 2 For the code itself there is no difference between a positional and a named attribute. Inline Macro Processor Include Processor Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://nuclearsquid.com/category/postgresql/ | PostgreSQL Hi, I'm Markus. I'm a freelance programmer who likes performance, PostgreSQL , cooking, and getting Email . All posts in PostgreSQL n Things You Probably Didn't Know About PostgreSQL Archives Feed cypher nuclearsquid cypher@hachyderm.io © 2008–2023 Markus Wein Imprint | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctor/latest/get-started/ | Convert Your First AsciiDoc File | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets Asciidoctor Features What’s New in 2.0 Install and Update Supported Platforms Install Using Ruby Packaging Install Using Linux Packaging Install on macOS Install on Windows Convert Your First File Converters Available Converters Custom Converter Converter Templates Convertible Contexts Generate HTML Stylesheets Default Stylesheet Stylesheet Modes Apply a Custom Stylesheet Embed a CodeRay or Pygments Stylesheet Manage Images Use Local Font Awesome Add a Favicon Verbatim Block Line Wrapping Skip Front Matter Generate DocBook Generate Manual Pages Process AsciiDoc Using the CLI asciidoctor(1) Specify an Output File Process Multiple Source Files Pipe Content Through the CLI Set Safe Mode CLI Options Process AsciiDoc Using the API Load and Convert Files Load and Convert Strings Generate an HTML TOC Set Safe Mode Enable the Sourcemap Catalog Assets Find Blocks API Options Safe Modes Safe Mode Specific Content AsciiDoc Tooling Syntax Highlighting Highlight.js Rouge CodeRay Pygments Custom Adapter STEM Processing MathJax and HTML Asciidoctor Mathematical STEM Support in the DocBook Toolchain AsciiMath Gem Extensions Register Extensions Log from an Extension Preprocessor Tree Processor Postprocessor Docinfo Processor Block Processor Compound Block Processor Block Macro Processor Inline Macro Processor Include Processor Localization Support Errors and Warnings Migration Guides Upgrade from Asciidoctor 1.5.x to 2.0 Migrate from AsciiDoc.py Migrate from DocBook XML Migrate from Markdown Migrate from Confluence XHTML Migrate from MS Word Asciidoctor 2.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community Asciidoctor Convert Your First File Edit this Page Convert Your First AsciiDoc File Assumptions: You’ve installed Asciidoctor. You’ve confirmed that the Asciidoctor command line interface (CLI) is available on your PATH. On this page, you’ll learn how to run Asciidoctor on an AsciiDoc document and convert it to HTML. Generate HTML using the default converter Let’s generate HTML 5 using Asciidoctor’s default converter and stylesheet from an AsciiDoc document. To follow along with the steps below, copy the contents of Example 1 into a new plain text file or use your own AsciiDoc document. Example 1. my-document.adoc = The Dangers of Wolpertingers :url-wolpertinger: https://en.wikipedia.org/wiki/Wolpertinger Don't worry about gumberoos or splintercats. Something far more fearsome plagues the days, nights, and inbetweens. Wolpertingers. == Origins Wolpertingers are {url-wolpertinger}[ravenous beasts]. Make sure to save the file with the .adoc file extension. Open a terminal and switch ( cd ) into the directory where your AsciiDoc document is saved. $ cd directory-name Call Asciidoctor with the asciidoctor command, followed by file name of the AsciiDoc document. Since HTML 5 is Asciidoctor’s default output, we don’t need to specify a converter. $ asciidoctor my-document.adoc As long as the document didn’t contain any syntax errors, you won’t see any messages printed to your terminal. Type ls to list the files in the directory. $ ls my-document.adoc my-document.html You should see a new file named my-document.html . Asciidoctor derives the name of the output file from the name of the input document. Open my-document.html in your web browser. The converted document should look like the example below. The document’s text, titles, and link is styled by the default Asciidoctor stylesheet, which is embedded in the HTML output. As a result, you could save my-document.html to any computer and it will look the same. Most of the examples in the general documentation use the CLI, but there are usually corresponding API examples under Process AsciiDoc Using the API . Install on Windows Converters Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/browser-extension/ | Asciidoctor Browser Extension Documentation | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets Browser Extension Install Quickstart Features Extension Options Custom attributes string Diagrams extension Theme/Stylesheet JavaScript Load the JavaScript Diagrams Extension Quickstart Use Cases Known issues Browser Extension AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community Browser Extension Introduction Edit this Page Asciidoctor Browser Extension Documentation An AsciiDoc File Viewer, the Asciidoctor Browser Extension uses Asciidoctor.js to view AsciiDoc files (.ad, .adoc, .asc, .asciidoc, and optionally .txt) as HTML inside Chrome, Brave, Firefox, Opera, Microsoft Edge and other Chromium-based browsers. The Asciidoctor Browser Extension brings all the features of simple AsciiDoc markup directly to the browser such as: attributes (akin to variables), include files, conditional statements, admonitions, icons, stylesheets, automatic numbering of sections and lists, and more. With the Asciidoctor Browser Extension and simple AsciiDoc markup you can save time and effort in creating beautiful output from simple text. The Asciidoctor Browser Extension is a both a viewer and previewer, depending upon your contexts (plural) of using it: from using the Asciidoctor Browser Extension as the only way to render and view collections of AsciiDoc files, to more complex environments. You can learn more about AsciiDoc and use an interactive editor at asciidoc.org . Install Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://www.gentoo.org | Welcome – Gentoo Linux Get Gentoo! gentoo.org sites gentoo.org Wiki Bugs Packages Forums Planet Archives Devmanual Gitweb Infra status Toggle navigation Home Get started Downloads Inside Gentoo Support Get involved Donate Welcome to Gentoo, a highly flexible, source-based Linux distribution. Learn more Get started now 2025 in retrospect & happy new year 2026! (Jan 5, 2026) Happy New Year 2026! Once again, a lot has happened in Gentoo over the past months. New developers, more binary packages, GnuPG alternatives support, Gentoo for WSL, improved Rust bootstrap, better NGINX packaging, … As always here we’re going to revisit all the exciting news from our favourite Linux distribution. FOSDEM 2026 (Dec 26, 2025) Once again it’s FOSDEM time! Join us at Université Libre de Bruxelles , Campus du Solbosch, in Brussels, Belgium. The upcoming FOSDEM 2026 will be held on January 31st and February 1st 2026. If you visit FOSDEM, make sure to come by at our Gentoo stand (exact location still to be announced), for the newest Gentoo news and Gentoo swag. Also, this year there will be a talk about the official Gentoo binary packages in the Distributions devroom . Visit our Gentoo wiki page on FOSDEM 2026 to see who’s coming and for more practical information. All news items Developer blogs live from Planet Gentoo GentooNews 2025 in retrospect & happy new year 2026! GentooNews FOSDEM 2026 mgorny One jobserver to rule them all mgorny How we incidentally uncovered a 7-year old bug in gentoo-ci mgorny EPYTEST_PLUGINS and other goodies now in Gentoo Security advisories from our Security database GLSA 202512-01 GnuPG: Arbitrary Code Execution high GLSA 202511-07 librnp: Weak random number generation high GLSA 202511-06 libpng: Multiple vulnerabilities high GLSA 202511-05 redict, redis: Multiple Vulnerabilities high GLSA 202511-04 Chromium, Google Chrome, Microsoft Edge. Opera: Multiple Vulnerabilities high New packages at the Gentoo packages database app-editors/cursor Cursor App - AI-first coding environment dev-haskell/tasty-inspection-testing Inspection testing support for tasty dev-haskell/inspection-testing GHC plugin to do inspection testing dev-haskell/vector-stream Efficient Streams sys-fs/bcachefs-kmod Linux bcachefs kernel module for sys-fs/bcachefs-tools Fresh documentation on the Gentoo wiki NILFS started by Csfore Bcc started by Csfore Swww started by Flexibeast Mangowc started by DeiveDS Kmscon started by Afstelnoj Questions or comments? Please feel free to contact us . Home News Get Started About Gentoo Philosophy Screenshots FAQ Downloads Mirrors Signatures Inside Gentoo Developers Projects GLEPs Artwork Gentoo Foundation Sponsors Stores Contact Support Consulting Documentation Package database Repository news items Security USE flags rsync mirrors Get Involved IRC channels Forums Mailing lists Contribute Become a developer Get the code m Privacy Policy © 2001-2026 Gentoo Authors Gentoo is a trademark of the Gentoo Foundation, Inc. and of Förderverein Gentoo e.V. The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-4.0 license. The Gentoo Name and Logo Usage Guidelines apply. Version 3b02cac Generated Generated: 2026-01-13T08:30:19Z | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/sequel | GitHub - jeremyevans/sequel: Sequel: The Database Toolkit for Ruby Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / sequel Public Notifications You must be signed in to change notification settings Fork 1.1k Star 5.1k Sequel: The Database Toolkit for Ruby sequel.jeremyevans.net 5.1k stars 1.1k forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights jeremyevans/sequel master Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 8,591 Commits .github .github bin bin doc doc lib lib spec spec www www .ci.gemfile .ci.gemfile .gitignore .gitignore CHANGELOG CHANGELOG CONTRIBUTING CONTRIBUTING MIT-LICENSE MIT-LICENSE README.rdoc README.rdoc Rakefile Rakefile sequel.gemspec sequel.gemspec View all files Repository files navigation README Contributing License Sequel: The Database Toolkit for Ruby Sequel is a simple, flexible, and powerful SQL database access toolkit for Ruby. Sequel provides thread safety, connection pooling and a concise DSL for constructing SQL queries and table schemas. Sequel includes a comprehensive ORM layer for mapping records to Ruby objects and handling associated records. Sequel supports advanced database features such as prepared statements, bound variables, savepoints, two-phase commit, transaction isolation, primary/replica configurations, and database sharding. Sequel currently has adapters for ADO, Amalgalite, IBM_DB, JDBC, MySQL, Mysql2, ODBC, Oracle, PostgreSQL, SQLAnywhere, SQLite3, TinyTDS, and Trilogy. Resources Website sequel.jeremyevans.net RDoc Documentation sequel.jeremyevans.net/rdoc Source Code github.com/jeremyevans/sequel Bug tracking (GitHub Issues) github.com/jeremyevans/sequel/issues Discussion Forum (GitHub Discussions) github.com/jeremyevans/sequel/discussions Archived Discussion Forum (sequel-talk Google Group) www.mail-archive.com/sequel-talk@googlegroups.com / If you have questions about how to use Sequel, please ask on GitHub Discussions. Only use the the bug tracker to report bugs in Sequel, not to ask for help on using Sequel. To check out the source code: git clone git://github.com/jeremyevans/sequel.git Contact If you have any comments or suggestions please post to the Google group. Installation gem install sequel A Short Example require 'sequel' DB = Sequel . sqlite # memory database, requires sqlite3 DB . create_table :items do primary_key :id String :name Float :price end items = DB [ :items ] # Create a dataset # Populate the table items . insert ( name: 'abc' , price: rand * 100 ) items . insert ( name: 'def' , price: rand * 100 ) items . insert ( name: 'ghi' , price: rand * 100 ) # Print out the number of records puts "Item count: #{items.count}" # Print out the average price puts "The average price is: #{items.avg(:price)}" The Sequel Console Sequel includes an IRB console for quick access to databases (usually referred to as bin/sequel ). You can use it like this: sequel sqlite://test.db # test.db in current directory You get an IRB session with the Sequel::Database object stored in DB. In addition to providing an IRB shell (the default behavior), bin/sequel also has support for migrating databases, dumping schema migrations, and copying databases. See the bin/sequel guide for more details. An Introduction Sequel is designed to take the hassle away from connecting to databases and manipulating them. Sequel deals with all the boring stuff like maintaining connections, formatting SQL correctly and fetching records so you can concentrate on your application. Sequel uses the concept of datasets to retrieve data. A Dataset object encapsulates an SQL query and supports chainability, letting you fetch data using a convenient Ruby DSL that is both concise and flexible. For example, the following one-liner returns the average GDP for countries in the middle east region: DB [ :countries ]. where ( region: 'Middle East' ). avg ( :GDP ) Which is equivalent to: SELECT avg(GDP) FROM countries WHERE region = 'Middle East' Since datasets retrieve records only when needed, they can be stored and later reused. Records are fetched as hashes, and are accessed using an Enumerable interface: middle_east = DB [ :countries ]. where ( region: 'Middle East' ) middle_east . order ( :name ). each { | r | puts r [ :name ]} Sequel also offers convenience methods for extracting data from Datasets, such as an extended map method: middle_east . map ( :name ) # => ['Egypt', 'Turkey', 'Israel', ...] middle_east . map ([ :id , :name ]) # => [[1, 'Egypt'], [3, 'Turkey'], [2, 'Israel'], ...] Or getting results as a hash via as_hash , with one column as key and another as value: middle_east . as_hash ( :name , :area ) # => {'Israel' => 20000, 'Turkey' => 120000, ...} Getting Started Connecting to a database To connect to a database you simply provide Sequel.connect with a URL: require 'sequel' DB = Sequel . connect ( 'sqlite://blog.db' ) # requires sqlite3 The connection URL can also include such stuff as the user name, password, and port: DB = Sequel . connect ( 'postgres://user:password@host:port/database_name' ) # requires pg You can also specify optional parameters, such as the connection pool size, or loggers for logging SQL queries: DB = Sequel . connect ( "postgres://user:password@host:port/database_name" , max_connections: 10 , logger: Logger . new ( 'log/db.log' )) It is also possible to use a hash instead of a connection URL, but make sure to include the :adapter option in this case: DB = Sequel . connect ( adapter: :postgres , user: 'user' , password: 'password' , host: 'host' , port: port , database: 'database_name' , max_connections: 10 , logger: Logger . new ( 'log/db.log' )) You can specify a block to connect, which will disconnect from the database after it completes: Sequel . connect ( 'postgres://user:password@host:port/database_name' ){ | db | db [ :posts ]. delete } The DB convention Throughout Sequel’s documentation, you will see the DB constant used to refer to the Sequel::Database instance you create. This reflects the recommendation that for an app with a single Sequel::Database instance, the Sequel convention is to store the instance in the DB constant. This is just a convention, it’s not required, but it is recommended. Note that some frameworks that use Sequel may create the Sequel::Database instance for you, and you might not know how to access it. In most cases, you can access the Sequel::Database instance through Sequel::Model.db . Arbitrary SQL queries You can execute arbitrary SQL code using Database#run : DB . run ( "create table t (a text, b text)" ) DB . run ( "insert into t values ('a', 'b')" ) You can also create datasets based on raw SQL: dataset = DB [ 'select id from items' ] dataset . count # will return the number of records in the result set dataset . map ( :id ) # will return an array containing all values of the id column in the result set You can also fetch records with raw SQL through the dataset: DB [ 'select * from items' ]. each do | row | p row end You can use placeholders in your SQL string as well: name = 'Jim' DB [ 'select * from items where name = ?' , name ]. each do | row | p row end Getting Dataset Instances Datasets are the primary way records are retrieved and manipulated. They are generally created via the Database#from or Database#[] methods: posts = DB . from ( :posts ) posts = DB [ :posts ] # same Datasets will only fetch records when you tell them to. They can be manipulated to filter records, change ordering, join tables, etc. Datasets are always frozen, and they are safe to use by multiple threads concurrently. Retrieving Records You can retrieve all records by using the all method: posts . all # SELECT * FROM posts The all method returns an array of hashes, where each hash corresponds to a record. You can also iterate through records one at a time using each : posts . each { | row | p row } Or perform more advanced stuff: names_and_dates = posts . map ([ :name , :date ]) old_posts , recent_posts = posts . partition { | r | r [ :date ] < Date . today - 7 } You can also retrieve the first record in a dataset: posts . order ( :id ). first # SELECT * FROM posts ORDER BY id LIMIT 1 Note that you can get the first record in a dataset even if it isn’t ordered: posts . first # SELECT * FROM posts LIMIT 1 If the dataset is ordered, you can also ask for the last record: posts . order ( :stamp ). last # SELECT * FROM posts ORDER BY stamp DESC LIMIT 1 You can also provide a filter when asking for a single record: posts . first ( id: 1 ) # SELECT * FROM posts WHERE id = 1 LIMIT 1 Or retrieve a single value for a specific record: posts . where ( id: 1 ). get ( :name ) # SELECT name FROM posts WHERE id = 1 LIMIT 1 Filtering Records The most common way to filter records is to provide a hash of values to match to where : my_posts = posts . where ( category: 'ruby' , author: 'david' ) # WHERE ((category = 'ruby') AND (author = 'david')) You can also specify ranges: my_posts = posts . where ( stamp: ( Date . today - 14 ) .. ( Date . today - 7 )) # WHERE ((stamp >= '2010-06-30') AND (stamp <= '2010-07-07')) Or arrays or sets of values: my_posts = posts . where ( category: [ 'ruby' , 'postgres' , 'linux' ]) # WHERE (category IN ('ruby', 'postgres', 'linux')) my_posts = posts . where ( category: Set [ 'ruby' , 'postgres' , 'linux' ]) # WHERE (category IN ('ruby', 'postgres', 'linux')) By passing a block to where, you can use expressions (this is fairly “magical”): my_posts = posts . where { stamp > Date . today << 1 } # WHERE (stamp > '2010-06-14') my_posts = posts . where { stamp =~ Date . today } # WHERE (stamp = '2010-07-14') If you want to wrap the objects yourself, you can use expressions without the “magic”: my_posts = posts . where ( Sequel [ :stamp ] > Date . today << 1 ) # WHERE (stamp > '2010-06-14') my_posts = posts . where ( Sequel [ :stamp ] =~ Date . today ) # WHERE (stamp = '2010-07-14') Some databases such as PostgreSQL and MySQL also support filtering via Regexps: my_posts = posts . where ( category: /ruby/i ) # WHERE (category ~* 'ruby') You can also use an inverse filter via exclude : my_posts = posts . exclude ( category: [ 'ruby' , 'postgres' , 'linux' ]) # WHERE (category NOT IN ('ruby', 'postgres', 'linux')) But note that this does a full inversion of the filter: my_posts = posts . exclude ( category: [ 'ruby' , 'postgres' , 'linux' ], id: 1 ) # WHERE ((category NOT IN ('ruby', 'postgres', 'linux')) OR (id != 1)) If at any point you want to use a custom SQL fragment for part of a query, you can do so via Sequel.lit : posts . where ( Sequel . lit ( 'stamp IS NOT NULL' )) # WHERE (stamp IS NOT NULL) You can safely interpolate parameters into the custom SQL fragment by providing them as additional arguments: author_name = 'JKR' posts . where ( Sequel . lit ( '(stamp < ?) AND (author != ?)' , Date . today - 3 , author_name )) # WHERE ((stamp < '2010-07-11') AND (author != 'JKR')) Datasets can also be used as subqueries: DB [ :items ]. where ( Sequel [ :price ] > DB [ :items ]. select { avg ( price ) + 100 }) # WHERE (price > (SELECT avg(price) + 100 FROM items)) After filtering, you can retrieve the matching records by using any of the retrieval methods: my_posts . each { | row | p row } See the Dataset Filtering file for more details. Security Designing apps with security in mind is a best practice. Please read the Security Guide for details on security issues that you should be aware of when using Sequel. Summarizing Records Counting records is easy using count : posts . where ( Sequel . like ( :category , '%ruby%' )). count # SELECT COUNT(*) FROM posts WHERE (category LIKE '%ruby%' ESCAPE '\') And you can also query maximum/minimum values via max and min : max = DB [ :history ]. max ( :value ) # SELECT max(value) FROM history min = DB [ :history ]. min ( :value ) # SELECT min(value) FROM history Or calculate a sum or average via sum and avg : sum = DB [ :items ]. sum ( :price ) # SELECT sum(price) FROM items avg = DB [ :items ]. avg ( :price ) # SELECT avg(price) FROM items Ordering Records Ordering datasets is simple using order : posts . order ( :stamp ) # ORDER BY stamp posts . order ( :stamp , :name ) # ORDER BY stamp, name order always overrides the existing order: posts . order ( :stamp ). order ( :name ) # ORDER BY name If you would like to add to the existing order, use order_append or order_prepend : posts . order ( :stamp ). order_append ( :name ) # ORDER BY stamp, name posts . order ( :stamp ). order_prepend ( :name ) # ORDER BY name, stamp You can also specify descending order: posts . reverse_order ( :stamp ) # ORDER BY stamp DESC posts . order ( Sequel . desc ( :stamp )) # ORDER BY stamp DESC Core Extensions Note the use of Sequel.desc(:stamp) in the above example. Much of Sequel’s DSL uses this style, calling methods on the Sequel module that return SQL expression objects. Sequel also ships with a core_extensions extension that integrates Sequel’s DSL better into the Ruby language, allowing you to write: :stamp . desc instead of: Sequel . desc ( :stamp ) Selecting Columns Selecting specific columns to be returned is also simple using select : posts . select ( :stamp ) # SELECT stamp FROM posts posts . select ( :stamp , :name ) # SELECT stamp, name FROM posts Like order , select overrides an existing selection: posts . select ( :stamp ). select ( :name ) # SELECT name FROM posts As you might expect, there are order_append and order_prepend equivalents for select called select_append and select_prepend : posts . select ( :stamp ). select_append ( :name ) # SELECT stamp, name FROM posts posts . select ( :stamp ). select_prepend ( :name ) # SELECT name, stamp FROM posts Deleting Records Deleting records from the table is done with delete : posts . where ( Sequel [ :stamp ] < Date . today - 3 ). delete # DELETE FROM posts WHERE (stamp < '2010-07-11') Be very careful when deleting, as delete affects all rows in the dataset. Call where first and delete second: # DO THIS: posts . where ( Sequel [ :stamp ] < Date . today - 7 ). delete # NOT THIS: posts . delete . where ( Sequel [ :stamp ] < Date . today - 7 ) Inserting Records Inserting records into the table is done with insert : posts . insert ( category: 'ruby' , author: 'david' ) # INSERT INTO posts (category, author) VALUES ('ruby', 'david') Updating Records Updating records in the table is done with update : posts . where ( Sequel [ :stamp ] < Date . today - 7 ). update ( state: 'archived' ) # UPDATE posts SET state = 'archived' WHERE (stamp < '2010-07-07') You can provide arbitrary expressions when choosing what values to set: posts . where ( Sequel [ :stamp ] < Date . today - 7 ). update ( backup_number: Sequel [ :backup_number ] + 1 ) # UPDATE posts SET backup_number = (backup_number + 1) WHERE (stamp < '2010-07-07')))) As with delete , update affects all rows in the dataset, so where first, update second: # DO THIS: posts . where ( Sequel [ :stamp ] < Date . today - 7 ). update ( state: 'archived' ) # NOT THIS: posts . update ( state: 'archived' ). where ( Sequel [ :stamp ] < Date . today - 7 ) Merging records Merging records using the SQL MERGE statement is done using merge* methods. You use merge_using to specify the merge source and join conditions. You can use merge_insert , merge_delete , and/or merge_update to set the INSERT, DELETE, and UPDATE clauses for the merge. merge_insert takes the same arguments as insert , and merge_update takes the same arguments as update . merge_insert , merge_delete , and merge_update can all be called with blocks, to set the conditions for the related INSERT, DELETE, or UPDATE. Finally, after calling all of the other merge_* methods, you call merge to run the MERGE statement on the database. ds = DB [ :m1 ] merge_using ( :m2 , i1: :i2 ). merge_insert ( i1: :i2 , a: Sequel [ :b ] +11 ). merge_delete { a > 30 }. merge_update ( i1: Sequel [ :i1 ] + :i2 +10 , a: Sequel [ :a ] + :b +20 ) ds . merge # MERGE INTO m1 USING m2 ON (i1 = i2) # WHEN NOT MATCHED THEN INSERT (i1, a) VALUES (i2, (b + 11)) # WHEN MATCHED AND (a > 30) THEN DELETE # WHEN MATCHED THEN UPDATE SET i1 = (i1 + i2 + 10), a = (a + b + 20) Transactions You can wrap a block of code in a database transaction using the Database#transaction method: DB . transaction do # BEGIN posts . insert ( category: 'ruby' , author: 'david' ) # INSERT posts . where ( Sequel [ :stamp ] < Date . today - 7 ). update ( state: 'archived' ) # UPDATE end # COMMIT If the block does not raise an exception, the transaction will be committed. If the block does raise an exception, the transaction will be rolled back, and the exception will be reraised. If you want to rollback the transaction and not raise an exception outside the block, you can raise the Sequel::Rollback exception inside the block: DB . transaction do # BEGIN posts . insert ( category: 'ruby' , author: 'david' ) # INSERT if posts . where ( 'stamp < ?' , Date . today - 7 ). update ( state: 'archived' ) == 0 # UPDATE raise Sequel :: Rollback end end # ROLLBACK Joining Tables Sequel makes it easy to join tables: order_items = DB [ :items ]. join ( :order_items , item_id: :id ). where ( order_id: 1234 ) # SELECT * FROM items # INNER JOIN order_items ON (order_items.item_id = items.id) # WHERE (order_id = 1234) The important thing to note here is that item_id is automatically qualified with the table being joined, and id is automatically qualified with the last table joined. You can then do anything you like with the dataset: order_total = order_items . sum ( :price ) # SELECT sum(price) FROM items # INNER JOIN order_items ON (order_items.item_id = items.id) # WHERE (order_id = 1234) Note that the default selection in Sequel is * , which includes all columns in all joined tables. Because Sequel returns results as a hash keyed by column name symbols, if any tables have columns with the same name, this will clobber the columns in the returned hash. So when joining you are usually going to want to change the selection using select , select_all , and/or select_append . Column references in Sequel Sequel expects column names to be specified using symbols. In addition, returned hashes always use symbols as their keys. This allows you to freely mix literal values and column references in many cases. For example, the two following lines produce equivalent SQL: items . where ( x: 1 ) # SELECT * FROM items WHERE (x = 1) items . where ( 1 => :x ) # SELECT * FROM items WHERE (1 = x)" Ruby strings are generally treated as SQL strings: items . where ( x: 'x' ) # SELECT * FROM items WHERE (x = 'x') Qualifying identifiers (column/table names) An identifier in SQL is a name that represents a column, table, or schema. The recommended way to qualify columns is to use Sequel[][] or Sequel.qualify Sequel [ :table ][ :column ] Sequel . qualify ( :table , :column ) # table.column You can also qualify tables with schemas: Sequel [ :schema ][ :table ] # schema.table or use multi-level qualification: Sequel [ :schema ][ :table ][ :column ] # schema.table.column Expression aliases You can alias identifiers using Sequel[].as or Sequel.as : Sequel [ :column ]. as ( :alias ) Sequel . as ( :column , :alias ) # column AS alias You can use the Sequel.as method to alias arbitrary expressions, not just identifiers: Sequel . as ( DB [ :posts ]. select { max ( id )}, :p ) # (SELECT max(id) FROM posts) AS p And most Sequel expression objects support an as method for aliasing: ( Sequel [ :column ] + 2 ). as ( :c_plus_2 ) # (column + 2) AS c_plus_2 Sequel Models A model class wraps a dataset, and an instance of that class wraps a single record in the dataset. Model classes are defined as regular Ruby classes inheriting from Sequel::Model : DB = Sequel . connect ( 'sqlite://blog.db' ) class Post < Sequel :: Model end When a model class is created, it parses the schema in the table from the database, and automatically sets up accessor methods for all of the columns in the table (Sequel::Model implements the active record pattern). Sequel model classes assume that the table name is an underscored plural of the class name: Post . table_name # => :posts You can explicitly set the table name or even the dataset used: class Post < Sequel :: Model ( :my_posts ); end # or: class Post < Sequel :: Model ( DB [ :my_posts ]); end If you pass a symbol to the Sequel::Model method, it assumes you are referring to the table with the same name. You can also call it with a dataset, which will set the defaults for all retrievals for that model: class Post < Sequel :: Model ( DB [ :my_posts ]. where ( category: 'ruby' )); end class Post < Sequel :: Model ( DB [ :my_posts ]. select ( :id , :name ). order ( :date )); end Model instances Model instances are identified by a primary key. Sequel queries the database to determine the primary key for each model. The Model.[] method can be used to fetch records by their primary key: post = Post [ 123 ] The pk method is used to retrieve the record’s primary key value: post . pk # => 123 If you want to override which column(s) to use as the primary key, you can use set_primary_key : class Post < Sequel :: Model set_primary_key [ :category , :title ] end post = Post [ 'ruby' , 'hello world' ] post . pk # => ['ruby', 'hello world'] You can also define a model class that does not have a primary key via no_primary_key , but then you lose the ability to easily update and delete records: Post . no_primary_key A single model instance can also be fetched by specifying a condition: post = Post . first ( title: 'hello world' ) post = Post . first { num_comments < 10 } The dataset for a model class returns rows of model instances instead of plain hashes: DB [ :posts ]. first . class # => Hash Post . first . class # => Post Acts like a dataset A model class forwards many methods to the underlying dataset. This means that you can use most of the Dataset API to create customized queries that return model instances, e.g.: Post . where ( category: 'ruby' ). each { | post | p post } You can also manipulate the records in the dataset: Post . where { num_comments < 7 }. delete Post . where ( Sequel . like ( :title , /ruby/ )). update ( category: 'ruby' ) Accessing record values A model instance stores its values as a hash with column symbol keys, which you can access directly via the values method: post . values # => {:id => 123, :category => 'ruby', :title => 'hello world'} You can read the record values as object attributes, assuming the attribute names are valid columns in the model’s dataset: post . id # => 123 post . title # => 'hello world' If the record’s attributes names are not valid columns in the model’s dataset (maybe because you used select_append to add a computed value column), you can use Model#[] to access the values: post [ :id ] # => 123 post [ :title ] # => 'hello world' You can also modify record values using attribute setters or the []= method. post . title = 'hey there' post [ :title ] = 'hey there' That will just change the value for the object, it will not update the row in the database. To update the database row, call the save method: post . save Mass assignment You can also set the values for multiple columns in a single method call, using one of the mass-assignment methods. See the mass assignment guide for details. For example set updates the model’s column values without saving: post . set ( title: 'hey there' , updated_by: 'foo' ) and update updates the model’s column values and then saves the changes to the database: post . update ( title: 'hey there' , updated_by: 'foo' ) Creating new records New model instances can be created by calling Model.new , which returns a new model instance without updating the database: post = Post . new ( title: 'hello world' ) You can save the record to the database later by calling save on the model instance: post . save If you want to create a new record and save it to the database at the same time, you can use Model.create : post = Post . create ( title: 'hello world' ) You can also supply a block to Model.new and Model.create : post = Post . new do | p | p . title = 'hello world' end post = Post . create { | p | p . title = 'hello world' } Hooks You can execute custom code when creating, updating, or deleting records by defining hook methods. The before_create and after_create hook methods wrap record creation. The before_update and after_update hook methods wrap record updating. The before_save and after_save hook methods wrap record creation and updating. The before_destroy and after_destroy hook methods wrap destruction. The before_validation and after_validation hook methods wrap validation. Example: class Post < Sequel :: Model def after_create super author . increase_post_count end def after_destroy super author . decrease_post_count end end Note the use of super if you define your own hook methods. Almost all Sequel::Model class and instance methods (not just hook methods) can be overridden safely, but you have to make sure to call super when doing so, otherwise you risk breaking things. For the example above, you should probably use a database trigger if you can. Hooks can be used for data integrity, but they will only enforce that integrity when you are modifying the database through model instances, and even then they are often subject to race conditions. It’s best to use database triggers and database constraints to enforce data integrity. Deleting records You can delete individual records by calling delete or destroy . The only difference between the two methods is that destroy invokes before_destroy and after_destroy hook methods, while delete does not: post . delete # => bypasses hooks post . destroy # => runs hooks Records can also be deleted en-masse by calling delete and destroy on the model’s dataset. As stated above, you can specify filters for the deleted records: Post . where ( category: 32 ). delete # => bypasses hooks Post . where ( category: 32 ). destroy # => runs hooks Please note that if destroy is called, each record is deleted separately, but delete deletes all matching records with a single SQL query. Associations Associations are used in order to specify relationships between model classes that reflect relationships between tables in the database, which are usually specified using foreign keys. You specify model associations via class methods: class Post < Sequel :: Model many_to_one :author one_to_many :comments one_to_one :first_comment , class: :Comment , order: :id many_to_many :tags one_through_one :first_tag , class: :Tag , order: :name , right_key: :tag_id end many_to_one and one_to_one create a getter and setter for each model object: post = Post . create ( name: 'hi!' ) post . author = Author . first ( name: 'Sharon' ) post . author one_to_many and many_to_many create a getter method, a method for adding an object to the association, a method for removing an object from the association, and a method for removing all associated objects from the association: post = Post . create ( name: 'hi!' ) post . comments comment = Comment . create ( text: 'hi' ) post . add_comment ( comment ) post . remove_comment ( comment ) post . remove_all_comments tag = Tag . create ( tag: 'interesting' ) post . add_tag ( tag ) post . remove_tag ( tag ) post . remove_all_tags Note that the remove_* and remove_all_* methods do not delete the object from the database, they merely disassociate the associated object from the receiver. All associations add a dataset method that can be used to further filter or reorder the returned objects, or modify all of them: # Delete all of this post's comments from the database post . comments_dataset . destroy # Return all tags related to this post with no subscribers, ordered by the tag's name post . tags_dataset . where ( subscribers: 0 ). order ( :name ). all Eager Loading Associations can be eagerly loaded via eager and the :eager association option. Eager loading is used when loading a group of objects. It loads all associated objects for all of the current objects in one query, instead of using a separate query to get the associated objects for each current object. Eager loading requires that you retrieve all model objects at once via all (instead of individually by each ). Eager loading can be cascaded, loading association’s associated objects. class Person < Sequel :: Model one_to_many :posts , eager: [ :tags ] end class Post < Sequel :: Model many_to_one :person one_to_many :replies many_to_many :tags end class Tag < Sequel :: Model many_to_many :posts many_to_many :replies end class Reply < Sequel :: Model many_to_one :person many_to_one :post many_to_many :tags end # Eager loading via .eager Post . eager ( :person ). all # eager is a dataset method, so it works with filters/orders/limits/etc. Post . where { topic > 'M' }. order ( :date ). limit ( 5 ). eager ( :person ). all person = Person . first # Eager loading via :eager (will eagerly load the tags for this person's posts) person . posts # These are equivalent Post . eager ( :person , :tags ). all Post . eager ( :person ). eager ( :tags ). all # Cascading via .eager Tag . eager ( posts: :replies ). all # Will also grab all associated posts' tags (because of :eager) Reply . eager ( person: :posts ). all # No depth limit (other than memory/stack), and will also grab posts' tags # Loads all people, their posts, their posts' tags, replies to those posts, # the person for each reply, the tag for each reply, and all posts and # replies that have that tag. Uses a total of 8 queries. Person . eager ( posts: { replies: [ :person , { tags: [ :posts , :replies ]}]}). all In addition to using eager , you can also use eager_graph , which will use a single query to get the object and all associated objects. This may be necessary if you want to filter or order the result set based on columns in associated tables. It works with cascading as well, the API is similar. Note that using eager_graph to eagerly load multiple *_to_many associations will cause the result set to be a cartesian product, so you should be very careful with your filters when using it in that case. You can dynamically customize the eagerly loaded dataset by using a proc. This proc is passed the dataset used for eager loading, and should return a modified copy of that dataset: # Eagerly load only replies containing 'foo' Post . eager ( replies: proc { | ds | ds . where ( Sequel . like ( text , '%foo%' ))}). all This also works when using eager_graph , in which case the proc is called with dataset to graph into the current dataset: Post . eager_graph ( replies: proc { | ds | ds . where ( Sequel . like ( text , '%foo%' ))}). all You can dynamically customize eager loads for both eager and eager_graph while also cascading, by making the value a single entry hash with the proc as a key, and the cascaded associations as the value: # Eagerly load only replies containing 'foo', and the person and tags for those replies Post . eager ( replies: { proc { | ds | ds . where ( Sequel . like ( text , '%foo%' ))} => [ :person , :tags ]}). all Joining with Associations You can use the association_join method to add a join to the model’s dataset based on the association: Post . association_join ( :author ) # SELECT * FROM posts # INNER JOIN authors AS author ON (author.id = posts.author_id) This comes with variants for different join types: Post . association_left_join ( :replies ) # SELECT * FROM posts # LEFT JOIN replies ON (replies.post_id = posts.id) Similar to the eager loading methods, you can use multiple associations and nested associations: Post . association_join ( :author , replies: :person ). all # SELECT * FROM posts # INNER JOIN authors AS author ON (author.id = posts.author_id) # INNER JOIN replies ON (replies.post_id = posts.id) # INNER JOIN people AS person ON (person.id = replies.person_id) Extending the underlying dataset The recommended way to implement table-wide logic by defining methods on the dataset using dataset_module : class Post < Sequel :: Model dataset_module do def with_few_comments where { num_comments < 30 } end def clean_boring with_few_comments . delete end end end This allows you to have access to your model API from filtered datasets as well: Post . where ( category: 'ruby' ). clean_boring # DELETE FROM posts WHERE ((category = 'ruby') AND (num_comments < 30)) Inside dataset_module blocks, there are numerous methods that support easy creation of dataset methods. Most of these methods are named after the dataset methods themselves, such as select , order , and group : class Post < Sequel :: Model dataset_module do where ( :with_few_comments , Sequel [ :num_comments ] < 30 ) select :with_title_and_date , :id , :title , :post_date order :by_post_date , :post_date limit :top10 , 10 end end Post . with_few_comments . with_title_and_date . by_post_date . top10 # SELECT id, title, post_date # FROM posts # ORDER BY post_date # LIMIT 10 One advantage of using these methods inside dataset_module blocks, instead of defining methods manually, is that the created methods will generally cache the resulting values and result in better performance. Model Validations You can define a validate method for your model, which save will check before attempting to save the model in the database. If an attribute of the model isn’t valid, you should add an error message for that attribute to the model object’s errors . If an object has any errors added by the validate method, save will raise an error by default: class Post < Sequel :: Model def validate super errors . add ( :name , "can't be empty" ) if name . empty? errors . add ( :written_on , "should be in the past" ) if written_on >= Time . now end end Testing Sequel Please see the testing guide for recommendations on testing applications that use Sequel, as well as the how to run the tests for Sequel itself. Sequel Release Policy New major versions of Sequel do not have a defined release policy, but historically have occurred once every few years. New minor versions of Sequel are released around once a month near the start of the month. New tiny versions of Sequel are only released to address security issues or regressions in the most current release. Ruby Support Policy Sequel fully supports the currently supported versions of Ruby (MRI) and JRuby. It may support unsupported versions of Ruby or JRuby, but such support may be dropped in any minor version if keeping it becomes a support issue. The minimum Ruby version required to run the current version of Sequel is 1.9.2, and the minimum JRuby version is 9.2.0.0 (due to the bigdecimal dependency). Maintainer Jeremy Evans <code@jeremyevans.net> About Sequel: The Database Toolkit for Ruby sequel.jeremyevans.net Resources Readme Contributing Contributing Uh oh! There was an error while loading. Please reload this page . Activity Stars 5.1k stars Watchers 108 watching Forks 1.1k forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 338 Uh oh! There was an error while loading. Please reload this page . + 324 contributors Languages Ruby 98.5% HTML 1.4% CSS 0.1% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/guides/optimization/ | Optimization | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Help & Guides Optimization 3.0 3.0 2.5 Edit this Page Optimization JRuby may start slower than expected versus the C-based Ruby implementation (MRI). Fortunately, JRuby offers flags that can improve the start time and tune applications. Several Java flags can also be used in conjunction with or apart from the JRuby flags in order to improve the start time even more. For small tasks such as converting an AsciiDoc document, two JRuby flags can drastically improve the start time: JRuby flags Name Value jruby.compat.version RUBY1_9 jruby.compile.mode OFF When using AsciidoctorJ via the API these flags have to be set as system properties when creating the org.asciidoctor.Asciidoctor instance: System.setProperty("jruby.compat.version", "RUBY1_9"); System.setProperty("jruby.compile.mode", "OFF"); Asciidoctor asciidoctor = Asciidoctor.Factory.create(); When starting AsciidoctorJ via the CLI these options can be defined in the files .jrubyrc that are loaded from the current working directory and the home directory of the user. $ cat ./.jrubyrc compat.version=RUBY1_9 compile.mode=OFF $ ./asciidoctorj -V AsciidoctorJ 1.5.2 [https://asciidoctor.org] Runtime Environment: jruby 1.7.20 (1.9.3) The properties in these .jrubyrc files do not contain the prefix jruby. . The property values also must not have trailing blanks! Alternatively you can also set any system properties using the environment variable ASCIIDOCTORJ_OPTS : $ export ASCIIDOCTORJ_OPTS=-Djruby.compat.version=RUBY1_9 $ asciidoctorj -V AsciidoctorJ 1.5.2 [https://asciidoctor.org] Runtime Environment: jruby 1.7.20 (1.9.3) The Java flags available for improving start time depend on whether your working on a 32- or 64-bit processor and your JDK version. Let’s see a summary of these flags and in which environments they can be used. Java flags Name JDK -client 32 bit Java -Xverify:none 32/64 bit Java -XX:+TieredCompilation 32/64 bit Java SE 7 -XX:TieredStopAtLevel=1 32/64 bit Java SE 7 Setting flags for Java SE 6 export JAVA_OPTS="-Xverify:none -client" Loading External Gems with GEM_PATH Using a pre-release version Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/conversion-examples/ | Examples | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Usage Convert Documents Examples 3.0 3.0 2.5 Edit this Page Examples Here you will find simple but complete examples of how to convert documents using the different configuration options available. The examples cover the main scenarios, but you can mix and match usage of instances, builders and maps freely to suite your needs. Setting attributes and options as instances This is the supported method for its ease of use and type validation. Other way found below have been deprecated since v2.4.4 and may not be available in future releases. Asciidoctor asciidoctor = Asciidoctor.Factory.create(); (1) Attributes attributes = Attributes.builder() .backend("docbook") .icons("font") .build(); (2) Options options = Options.builder() .inPlace(true) .attributes(attributes) .build(); (3) String outfile = asciidoctor.convertFile(new File("sample.adoc"), options); (4) 1 Create Asciidoctor instance. 2 Defines the attributes as an Attributes class. 3 Defines the options as an Options class. 4 Converts the document passing previously created Options instance. The icons attribute requires a String to set the value used to "draw" icons. At this time, you can use two constants org.asciidoctor.Attributes.IMAGE_ICONS for using the same approach as AsciiDoc, that is using img tags, or org.asciidoctor.Attributes.FONT_ICONS for using icons from Font Awesome . Setting attributes and options as Map collections Asciidoctor asciidoctor = Asciidoctor.Factory.create(); (1) Map<String, Object> attributes = Attributes.builder() .backend("docbook") .icons("font") .asMap(); (2) Map<String, Object> options = Options.builder() .inPlace(true) .attributes(attributes) (3) .asMap(); (4) String outfile = asciidoctor.convertFile(new File("sample.adoc"), options); (5) 1 Create Asciidoctor instance. 2 Defines attributes using builder fluent API and retrieves them as Map . 3 Registers the attributes map as attributes . 4 Converts options to java.util.Map instance. Setting attributes and options as builders Asciidoctor asciidoctor = Asciidoctor.Factory.create(); (1) AttributesBuilder attributes = Attributes.builder() .backend("docbook") .icons("font"); (2) OptionsBuilder options = Options.builder() .inPlace(true) .attributes(attributes); (3) String outfile = asciidoctor.convertFile(new File("sample.adoc"), options); (4) 1 Create Asciidoctor instance. 2 Defines the attributes as an AttributesBuilder by not using build() , get() or `asMap(). 3 Defines the options as an OptionsBuilder by not using build() , get() or `asMap(). 4 Converts the document passing OptionsBuilder instance. Safe Modes Converting to EPUB3 Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://rubygems.org/gems/apetag | apetag | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up apetag 1.1.5 APEv2 Tag Reader/Writer Gemfile: = install: = Versions: 1.1.5 February 27, 2013 (16 KB) 1.1.4 January 21, 2011 (14 KB) 1.1.3 January 16, 2011 (14 KB) 1.1.2 November 07, 2007 * (13.5 KB) 1.1.1 August 20, 2007 * (13.5 KB) Show all versions (8 total) Runtime Dependencies (1): cicphash >= 1.0.0 Show all transitive dependencies Owners: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 180,341 For this version 139,252 Version Released: February 27, 2013 9:44pm Licenses: N/A Required Ruby Version: None Links: Homepage Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/reveal.js-converter/latest/setup/ruby-setup/ | Ruby Setup | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets Asciidoctor reveal.js What’s New Setup Ruby Node / JavaScript Standalone Executable Minimum Requirements Compatibility Matrix Write Your Presentation Title Slide Layout Background Slide Transitions Slide State Auto Animate Steps Admonitions Syntax Highlighting Videos Roles Data Attributes Footnotes Custom Styles Docinfo Configure reveal.js Config Options Plugins PDF Export Showcase Presentations Project Hacking Copyright and Licensing Asciidoctor reveal.js 5.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community Asciidoctor reveal.js Setup Ruby 5.0 5.0 4.1 Edit this Page Ruby Setup To ensure repeatability, we recommend that you manage your presentation projects using Bundler . Prerequisites If you manage Ruby using RVM (as recommended), make sure you switch to the default Ruby version and gemset: $ rvm use default If you’ve installed Ruby using RVM, you should already have Bundler installed. You can verify this using the following command: $ bundle -v If Bundler is not installed, you can install it using the following command: $ gem install bundler You’re now ready to install Asciidoctor reveal.js. Install These instructions should be repeated for every presentation project. Create a project directory $ mkdir my-awesome-presentation $ cd my-awesome-presentation In that directory, create a file named Gemfile with the following contents: source 'https://rubygems.org' gem 'asciidoctor-revealjs' (1) 1 Installs the latest released version of the asciidoctor-revealjs gem Install the gems into the project using Bundler $ bundle config --local path .bundle/gems $ bundle (Optional) Copy or clone reveal.js presentation framework $ git clone -b 4.5.0 --depth 1 https://github.com/hakimel/reveal.js.git This step allows you to modify themes or view slides offline. Rendering the AsciiDoc into slides Create content in a file (*.adoc, *.ad, etc.). See examples on the Features page to get started. Generate HTML presentation from the AsciiDoc source $ bundle exec asciidoctor-revealjs \ -a revealjsdir=https://cdn.jsdelivr.net/npm/reveal.js@4.5.0 \ presentation.adoc If you did the optional step of having a local clone of reveal.js, you can convert the AsciiDoc source using: $ bundle exec asciidoctor-revealjs presentation.adoc If you’re using GitHub Pages , plan ahead by keeping your source files on the default branch and all output files on the gh-pages branch. Features unique to the Ruby CLI Starting with 4.0.0 you can specify a set of custom templates to use instead of the ones provided by this project. This can help you achieve even more concise AsciiDoc syntax and integration with reveal.js at the cost of more maintenance. To use it, add the following dependencies to your Gemfile : gem 'tilt', '~>2.0' gem 'slim', '~>4.0' Then install the dependencies with: $ bundle install The feature is activated with the --template-dir or -T option: $ bundle exec asciidoctor-revealjs -T templates presentation.adoc Any individual template file not provided in the directory specified on the command-line will fall back to the template provided by your version of Asciidoctor reveal.js. Refer to our templates for inspiration. This feature hasn’t been ported to the JavaScript CLI (and API) or the standalone executables. Asciidoctor reveal.js Node / JavaScript Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/postprocessor/ | Postprocessor | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Write an Extension Postprocessor 3.0 3.0 2.5 Edit this Page Postprocessor Postprocessors are called when Asciidoctor has converted the document to its target format and have the chance to modify the result. A Postprocessor could for example insert a custom copyright notice into the footer element of the resulting HTML document. Postprocessors in AsciidoctorJ currently only supports String based target formats. That means it is not possible at the moment to write Postprocessors for binary formats like PDF or EPUB. As example, a Postprocessor that adds a copyright notice would look like this: A Postprocessor that inserts a copyright notice in the footer element import org.asciidoctor.ast.Document; import org.asciidoctor.extension.Postprocessor; import org.jsoup.Jsoup; import org.jsoup.nodes.Element; public class CopyrightFooterPostprocessor extends Postprocessor { (1) static final String COPYRIGHT_NOTICE = "Copyright Acme, Inc."; @Override public String process(Document document, String output) { org.jsoup.nodes.Document doc = Jsoup.parse(output, "UTF-8"); (2) Element contentElement = doc.getElementById("footer-text"); (3) if (contentElement != null) { contentElement.text(contentElement.ownText() + " | " + COPYRIGHT_NOTICE); } output = doc.html(); (4) return output; } } 1 All Postprocessors must extend the class org.asciidoctor.extension.Postprocessor and implement the method process() . 2 The processor parses the resulting HTML text using the Jsoup library. This returns the document as a data structure. 3 Find the element with the ID footer-text . This element contains the footer text, which usually contains the document generation timestamp. If this element is available its text is modified by appending the copyright notice. 4 Finally, convert the modified document back to the HTML string and let the processor return it. Make sure header_footer option is not set to false , otherwise these will not be added to the document. Preprocessor Treeprocessor Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/safe-mode-and-filesystem-access/ | Safe Modes | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Usage Convert Documents Safe Modes 3.0 3.0 2.5 Edit this Page Safe Modes Asciidoctor provides security levels that control the read and write access of attributes, the include directive, macros, and scripts while a document is processing. Each level includes the restrictions enabled in the prior security level. The safe modes in order from most insecure to most secure are: UNSAFE A safe mode level that disables any security features enforced by Asciidoctor. This is the default safe mode for the CLI. SAFE This safe mode level prevents access to files which reside outside of the parent directory of the source file. It disables all macros, except the include directive. The paths to include files must be within the parent directory. It allows assets to be embedded in the document. SERVER A safe mode level that disallows the document from setting attributes that would affect the rendering of the document. This level trims the attribute docfile to its relative path and prevents the document from: setting source-highlighter, doctype, docinfo and backend seeing docdir It allows icons and linkcss. SECURE A safe mode level that disallows the document from attempting to read files from the file system and including their contents into the document. Additionally, it: disables icons disables the include directive data can not be retrieved from URIs prevents access to stylesheets and JavaScript files sets the backend to html5 disables docinfo files disables data-uri disables docdir and docfile disables source highlighting Asciidoctor extensions may still embed content into the document depending on whether they honor the safe mode setting. This is the default safe mode for the API. When Asciidoctor (and AsciidoctorJ) is used as API , it uses SECURE safe mode by default. This mode is the most restrictive one and in summary it disallows the document from attempting to read files from the file system and including their contents into the document. We recommend you to set SAFE safe mode when converting AsciiDoc documents using AsciidoctorJ to have almost all Asciidoctor features such as icons , include directive or retrieving content from URIs enabled. Safe mode is set as option when a document is converted. For example: Options options = Options.builder() .safe(SafeMode.SAFE) .build(); String outfile = asciidoctor.convertFile(new File("sample.adoc"), options); We are going to explain in more detail options in Conversion Options section. You can read more about safe modes in asciidoctor.org/docs/user-manual/#running-asciidoctor-securely Locate Files Examples Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://wiki.freenode.net/ | freenode wiki Main Page From freenode wiki Jump to: navigation , search Contents 1 ¸¸♬·¯·♪·¯·♫¸¸ Welcome To freenode ¸¸♫·¯·♪¸♩·¯·♬¸¸ 2 Getting Started 2.1 clients 3 Resources and Tools 3.1 Guides 3.2 Network News 4 Help and Support 4.1 FAQ 5 Community Corner 5.1 freenode User Corner 5.2 Community Spotlight 6 Gaming Corner 7 Finding staff 8 Contact Information ¸¸♬·¯·♪·¯·♫¸¸ Welcome To freenode ¸¸♫·¯·♪¸♩·¯·♬¸¸ Maintainers: f Welcome to the freenode Wiki! This collaborative platform is dedicated to providing a wealth of information on various topics related to freenode, an IRC (Internet Relay Chat) network supporting discussions on open source and free software projects. Here, users like you can find valuable resources, guides, and documentation to enhance your experience on freenode. Thank you for visiting, and we hope you find the information here useful! Getting Started Freenode is an IRC (Internet Relay Chat) network that serves as a hub for open source and free software communities. To get started on Freenode, you'll need an IRC client, such as HexChat, mIRC, or IRCCloud. Once you have your client set up, connect to the Freenode network and choose a nickname (usually with the command /nick yournickname). Join channels related to your interests or projects by using the command /join #channelname. Remember to follow the network's guidelines and etiquette to have a positive experience interacting with others. clients Webchat Hexchat mIRC weechat konversation AdIRC Resources and Tools Guides Cloaks Nick Registration Channel Registration Channel Takeover Policy Network News Freenode has launched an exciting new feature: Freenode Radio! Tune in to #freenode-radio to enjoy a variety of music and shows while chatting with the Freenode community. Whether you're looking for background music while you work or want to discover new tunes, Freenode Radio has something for everyone. Join the channel and start listening today! Help and Support This is the section you will find the FAQs or troubleshooting guides or any helpful information. FAQ 1. What is Freenode? Freenode is an IRC (Internet Relay Chat) network used for discussing peer-directed projects and collaboration between individuals and communities interested in free and open-source software (FOSS) and related topics. 2. How do I connect to Freenode? You can connect to Freenode using an IRC client. Set your client to connect to chat.freenode.net on port 6667 (or port 6697 for SSL/TLS connections). You can also use Freenode's webchat service available at https://webchat.freenode.net/ . 3. Do I need to register my nickname on Freenode? While registration is not mandatory, it is recommended. Registering your nickname helps protect it from being used by others and allows you to access additional services such as joining channels that require registered nicknames. 4. How do I register my nickname on Freenode? To register your nickname, use the command /msg NickServ REGISTER password email, replacing password with your desired password and email with your email address. Follow the instructions sent to your email to complete the registration. 5. What are channels on Freenode? Channels on Freenode are chat rooms dedicated to specific topics or communities. Users can join channels to participate in discussions and interact with others who share similar interests. 6. How do I join a channel on Freenode? To join a channel, use the command /join #channel-name, replacing #channel-name with the name of the channel you want to join. For example, /join #freenode. 7. Are there any guidelines or rules for using Freenode? Yes, Freenode has a set of guidelines called the Freenode Charter, which outlines the expectations for behavior and interactions on the network. It is important to familiarize yourself with these guidelines to ensure a positive experience for yourself and others. 8. How can I get help or support on Freenode? If you need help or have questions about using Freenode, you can join the #freenode channel and ask for assistance. There are also several other channels dedicated to providing support for specific topics or services on Freenode. Community Corner The FreeNode Community Guidelines are designed to ensure a respectful and welcoming environment for all users. freenode User Corner Freenode channels Community Spotlight This section will be dedicated to a community that is active on freenode. Could be changed weekly or monthly. Gaming Corner Gaming Corner on Freenode is a vibrant community hub where gamers gather to explore new and exciting games. Our corner features a modern take on classics like Duckhunt , offering an enhanced and immersive experience that keeps players engaged and entertained. Additionally, we host exciting trivia games that test your knowledge and offer a fun way to compete with fellow gamers. If you have a game channel that you'd like to see featured on our corner, please reach out to either F or End3r to get your channel added to our wiki. Join us at Gaming Corner on Freenode and dive into a world of endless gaming possibilities! Finding staff Staff Contact Information - Name: Foxy - Email: foxy@freenode.net Notice: We reserve the right to deny access to the network at any time and for any reason. Whenever possible, a reason will be provided to you, however, we are under no obligation to do so. Retrieved from ‘ https://wiki.freenode.net/index.php?title=Main_Page&oldid=406 ’ Navigation menu Personal tools Log in Namespaces Main page Discussion Variants Views Read View source View history More Search Navigation Main page Network Info Network Information Community Guidelines Staff IRCd Info (inspircd) Channel Modes Basic User Commands Basic User Modes Services Anope MemoServ BotServ HostServ ChanServ NickServ HostServ Guides Cloaks Nick Registration Channel Registration Help about MediaWiki Tools What links here Related changes Special pages Printable version Permanent link Page information This page was last modified on 19 March 2025, at 16:23. Privacy policy About freenode wiki Disclaimers | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/converting-documents/ | Convert Documents | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Usage Convert Documents 3.0 3.0 2.5 Edit this Page Convert Documents This section shows you how you can use AsciidoctorJ to render AsciiDoc documents to HTML from within your own code. An introductory Getting started example shows the first steps necessary to convert your documents. Getting started The very first step to integrate AsciidoctorJ is to add the required dependencies to your project. Depending on your build system you have to add a dependency on the artifact asciidoctorj with the group id org.asciidoctor to your build file. The following snippets show what you have to add in case you use Maven, Gradle, Ivy or SBT. Declaring the dependency in a Maven build file (i.e., pom.xml) <dependencies> <dependency> <groupId>org.asciidoctor</groupId> <artifactId>asciidoctorj</artifactId> <version>3.0.0</version> (1) </dependency> </dependencies> Declaring the dependency in a Gradle build file (e.g., build.gradle) dependencies { compile 'org.asciidoctor:asciidoctorj:3.0.0' (1) } Declaring the dependency in an Ivy dependency descriptor (e.g., ivy.xml) <dependency org="org.asciidoctor" name="asciidoctorj" rev="3.0.0" /> (1) Declaring the dependency in an SBT build file (e.g., build.sbt) libraryDependencies += "org.asciidoctor" % "asciidoctorj" % "3.0.0" (1) 1 Specifying the version of AsciidoctorJ implicitly selects the version of Asciidoctor The dependency on AsciidoctorJ will transitively add a dependency on the module jruby-complete with the group id org.jruby . The following Java program shows how to convert an arbitrary AsciiDoc file to an HTML file. AsciidoctorJ will already fully embedded in your Java program and it looks like any other Java library, so there is no need to fear Ruby. If you execute the following Java program and have an AsciiDoc file document.adoc in your current working directory you should see the rendered result document.html afterwards next to your original document. Converting an AsciiDoc file to an HTML file package org.asciidoctor.integrationguide; import org.asciidoctor.Asciidoctor; import org.asciidoctor.Options; import org.asciidoctor.SafeMode; import java.io.File; public class SimpleAsciidoctorRendering { public static void main(String[] args) { Asciidoctor asciidoctor = Asciidoctor.Factory.create(); (1) asciidoctor.convertFile( (2) new File(args[0]), Options.builder() (3) .toFile(true) .safe(SafeMode.UNSAFE) .build()); } } 1 The static method Asciidoctor.Factory.create() creates a new Asciidoctor instance. This is the door to all interactions with Asciidoctor. 2 The method convertFile takes a File and conversion options. Depending on the options it will create a new file or return the rendered content. In this case a new file is created and the method returns null . 3 The conversion options define via toFile(true) that the result should be written to a new file. The option safe imposes security constraints on the rendering process. safe(SafeMode.UNSAFE) defines the least restricting constraints and allows for example inserting the beautiful asciidoctor.css stylesheet into the resulting document. Command Line Interface The Asciidoctor Interface Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/ruby-vorbis_comment | GitHub - jeremyevans/ruby-vorbis_comment: Ruby library for reading/writing vorbis comments Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / ruby-vorbis_comment Public Notifications You must be signed in to change notification settings Fork 1 Star 3 Ruby library for reading/writing vorbis comments ruby-vorbiscomment.jeremyevans.net License View license 3 stars 1 fork Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights jeremyevans/ruby-vorbis_comment master Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 44 Commits .github/ workflows .github/ workflows test test .ci.gemfile .ci.gemfile .gitignore .gitignore LICENSE LICENSE README.rdoc README.rdoc Rakefile Rakefile extconf.rb extconf.rb vcedit.c vcedit.c vcedit.h vcedit.h vorbis_comment.gemspec vorbis_comment.gemspec vorbis_comment.rb vorbis_comment.rb vorbis_comment_ext.c vorbis_comment_ext.c View all files Repository files navigation README License ruby-vorbis_comment ruby-vorbis_comment is a Ruby library for manipulating Vorbis comments. It wraps libvorbis and libogg, so it should be completely standards compatible. Vorbis comment is the standard tagging format for Ogg Vorbis, FLAC, and Speex files. This library tries to be API compatible with ruby-apetag, a library for reading and writing APE tags, the standard tagging format for Musepack and Monkey’s Audio, which can also be used with MP3s as an alternative to ID3v2. Usage require 'vorbis_comment' vc = VorbisComment . new ( 'file.ogg' ) # Whether file already has an vorbis comment vc . exists? # A CICPHash of fields, keys are strings, values are lists of strings vc . fields # String suitable for pretty printing vc . pretty_print # Update the tag with the added/changed/deleted fields vc . update { | fields | fields [ 'Artist' ]= 'Test Artist' ; fields . delete ( 'Year' )} # Clear the list of vorbis comments from the file vc . remove! Building To build the library, run rake build . To run the tests for the library after building, run rake . Support If you find any bugs, would like additional documentation, or want to submit a patch, please use GitHub ( github.com/jeremyevans/ruby-vorbis_comment/issues ). One known bug is that it doesn’t like files less than 8K in size. The RDoc for the project is available on ruby-vorbiscomment.jeremyevans.net The most current source code can be accessed via github ( github.com/jeremyevans/ruby-vorbis_comment /). Note that the library isn’t modified on a regular basis, so it is unlikely to be different from the latest release. If called from the command line, ‘vorbis_comment.rb` prints out the contents of the Vorbis comments for the given filename arguments. About Ruby library for reading/writing vorbis comments ruby-vorbiscomment.jeremyevans.net Resources Readme License View license Uh oh! There was an error while loading. Please reload this page . Activity Stars 3 stars Watchers 1 watching Forks 1 fork Report repository Releases 3 tags Packages 0 No packages published Uh oh! There was an error while loading. Please reload this page . Languages C 61.0% Ruby 39.0% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://www.unicode.org/reports/tr6/ | Stabilized Technical Report Technical Reports Home | Site Map | Search Related Links Unicode Technical Committee About Technical Reports Unicode Technical Notes Stabilized Technical Report UTS #6, "A Standard Compression Scheme for Unicode" has been stabilized: There are no plans to ever publish another update for it. The last version can be found at https://www.unicode.org/reports/tr6/tr6-4.html . SCSU defines a compact encoding, which is sometimes useful. However, Unicode text is much more commonly stored and transmitted in UTF-8 which is less compact (except for ASCII), much simpler, and does not present any security issues. For longer texts, general-purpose compression is effective and common. Therefore, there is no need to develop this report any further. | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/logging/ | Logging | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Logging 3.0 3.0 2.5 Edit this Page Logging Extensions are also able to log messages that are handled in the same way as messages logged by Asciidoctor itself as explained in Logs Handling API . Logging messages via this API allows build tools like the Asciidoctor Maven plugin to capture them and for example fail the build in case an error or warning is logged. Therefore it might be preferable to use this instead of directly logging messages via slf4j or other APIs. Every extension inherits the method Processor.log() that allows it to log messages. The following example shows a Block Macro Processor that logs a message containing the target of the macro: @Name("log") public class LoggingBlockMacroProcessor extends BlockMacroProcessor { @Override public StructuralNode process( StructuralNode parent, String target, Map<String, Object> attributes) { String message = target; log(new org.asciidoctor.log.LogRecord( (1) org.asciidoctor.log.Severity.INFO, parent.getSourceLocation(), (2) message)); return createBlock(parent, "paragraph", "Hello from the logging macro"); } } 1 The method log(LogRecord) is inherited from the Processor class hierarchy. 2 You can access the source location of the parent node to put the message in relation to the source document. Note that the source location will be null unless you enable the sourcemap option Automatically Loading Extensions Syntax Highlighter API Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/diagram-extension/latest/blocks/ | Diagram Blocks | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets Asciidoctor Diagram Overview Diagram Blocks Installation Rendering Diagrams Output Directories Diagram Types ASCIIToSVG ActDiag Barcode BlockDiag BPMN Bytefield-SVG D2 DBML Diagrams Ditaa ERD Gnuplot GoAT Graphviz LilyPond Meme Mermaid MscGen Nomnoml NwDiag / RackDiag / PacketDiag Oxdraw Penrose Pikchr Pintora PlantUML SeqDiag Shaape State Machine Cat Structurizr SvgBob Symbolator Syntrax / JSyntrax TikZ UMLet Vega / Vega-Lite WaveDrom Advanced Topics Enabling Extensions Asciidoctor Diagram 3.0.1 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community Asciidoctor Diagram Diagram Blocks Edit this Page Diagram Blocks Embedded diagrams are written using diagram blocks. Diagram blocks are delimited using either the literal or listing delimiter. Diagram Block Structure All diagram block types share a similar structure. Anatomy of a diagram [diagram-type, target=output-file-name, format=output-format] (1) (2) (3) .... (4) Diagram code (5) .... 1 The first value in the attribute list specifies the diagram syntax that is being used. 2 The target attribute specifies the basename of the image file that will be generated. If this attribute is omitted an auto-generated name will be used instead. 3 The format attribute determines the output image format to use. If a format is not specified, the default output format for the chosen diagram type will be used. 4 The asciidoc block type can be literal ( …​. ), listing ( ---- ) or open -- . 5 The block content is written in syntax of the chosen diagramming tool. Diagram Macros The diagram extensions can also be used in inline, or block macro form. Anatomy of a diagram block macro diagram-type::source-file-name[format=output-format] (1) (2) (3) 1 The macro name specifies the diagram syntax that is being used. 2 The source file name specifies the external file that contains the diagram source code. 3 The format attribute determines the output image format to use. If a format is not specified, the default output format for the chosen diagram type will be used. When the source file name is a relative path it is resolved with respect to the location of the document being processed. Diagram Attributes Some diagram types allow image generation to be customized using attributes. Attributes can be assigned to individual diagram blocks by adding them to the attribute list of the block. If the same attribute value should be applied to all blocks of a given diagram type, the attribute can also be assigned indirectly by defining an attribute at the document level. The attribute name at the document level should be prefixed with the diagram type name and a dash. This is illustrated for the blockdiag fontpath attribute in the example below. Diagram attributes per block and global = Asciidoctor Diagram :blockdiag-fontpath: /path/to/font.ttf (1) [blockdiag] (2) .... .... [blockdiag, fontpath="/path/to/otherfont.ttf"] (3) .... .... 1 Attributes can be specified for all diagram of a certain type at the document level by prefixing them with <blocktype>- . In this example, the fontpath attribute is specified for all diagrams of type blockdiag . 2 The first diagram does not specify an explicit value for fontpath so the global blockdiag-fontpath value will be used 3 The second diagram does specify a fontpath value. This overrides the global blockdiag-fontpath value. Common Attributes A number of attributes are common to all diagram types. These can be specified per block using their name, for each block of a diagram type using the diagram type as prefix, or globally for all diagram blocks using the diagram- prefix. Name Default value Description nocache unset When set, disables caching of images files and metadata . cachedir .asciidoctor/diagram The directory in which to write diagram cache entries (and optionally images) cache-images unset When set, generated images are written to the cachedir directory before being written to their final target location. svg-type unspecified When the output format is SVG, this attribute determines the SVG interactivity level. Example The example below illustrates the structure of a basic ditaa block written directly in an AsciiDoc document. Basic ditaa block [ditaa] .... +-------------+ | Asciidoctor |-------+ | diagram | | +-------------+ | PNG out ^ | | ditaa in | | v +--------+ +--------+----+ /---------------\ | | --+ Asciidoctor +--> | | | Text | +-------------+ | Beautiful | |Document| | !magic! | | Output | | {d}| | | | | +---+----+ +-------------+ \---------------/ : ^ | Lots of work | +-----------------------------------+ .... The ditaa block above results in the following diagram. Figure 1. Rendered ditaa diagram The rendered ditaa diagram above gets the file name 58372f7d2ceffae9e91fd0a7cbb080b6.png . That long number is the checksum of the source code calculated by asciidoctor-diagram. If you want to give your image files a more meaningful name, fill in the target attribute. This can be done by either specifying it as the second positional attribute or as a named attribute. Both examples below would result in a file called ditaa-diagram.png . [ditaa, target="ditaa-diagram"] ---- <snip> ---- [ditaa, "ditaa-diagram"] ---- <snip> ---- Overview Installation Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/guides/load-ruby-library/ | Loading Ruby Libraries | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Help & Guides Loading Ruby Libraries 3.0 3.0 2.5 Edit this Page Loading Ruby Libraries Most extensions can be fully implemented in Java, but some complex ones may require mixing Ruby and Java code. This means that you may need to execute a Ruby file or a RubyGem (i.e., gem) inside your extension. To load a Ruby file inside the Ruby runtime, you can use org.asciidoctor.jruby.internal.RubyUtils.loadRubyClass(Ruby, InputStream) . You can also load a gem using an API that wraps Ruby’s require command. The gem must be available inside the classpath. Next run org.asciidoctor.jruby.internal.RubyUtils.requireLibrary(Ruby, String) , passing the name of the gem as the second argument. Accessing the JRuby Instance Loading External Gems with GEM_PATH Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://lists.debian.org/debian-devel-announce/2015/02/msg00013.html | --> [CTTE #762194] Transition plan to systemd by default [ Date Prev ][Date Next] [ Thread Prev ][Thread Next] [ Date Index ] [ Thread Index ] [CTTE #762194] Transition plan to systemd by default To : debian-devel-announce@lists.debian.org Subject : [CTTE #762194] Transition plan to systemd by default From : Don Armstrong < don@debian.org > Date : Sun, 22 Feb 2015 11:15:32 -0800 Message-id : < [🔎] 20150222191532.GM6383@teltox.donarmstrong.com > Mail-followup-to : debian-ctte@lists.debian.org In #762194, the Technical Committee was asked to consider the transition plan of the init package maintainers to have both new installs and upgrades use systemd by default. 1. The CTTE determined in #727708 that systemd should be the default init system in Debian. 2. In https://lists.debian.org/87mwc9gfsw.fsf@xoog.err.no , the maintainers of the init package announced their transition plan for migrating to systemd as the default init system on both installs and new upgrades. 3. The init package (and other related packages) currently in jessie implement this transition. ==== RESOLUTION ==== Using its power under §6.1.5 to make statements: 3. The CTTE affirms the decision of the init system package maintainers to transition to systemd by default on upgrades and to install systemd by default on new installs. 4. The CTTE appreciates the effort of Debian contributors to mitigate any issues with the transition by: a) Providing a fallback boot entry for sysvinit when systemd is the default init in grub (#757298) b) Developing a mechanism to warn on inittab configurations which are unsupported in systemd. (#761063) c) Providing documentation on how to remain with sysvinit on upgrades and switch to sysvinit upon installation. d) Numerous bug reports and fixes by contributors who have tested the systemd migration in their configurations. 5. The CTTE advises (without overriding any Debian contributor, maintainer, or team) that any such mitigations should be included in jessie, to ensure a smooth transition for Debian users. ==== END OF RESOLUTION ==== The committe would like to thank everyone who participated in the discussion of #762194. Please see http://bugs.debian.org/762194 for discussion of this bug. Attachment: signature.asc Description: Digital signature Reply to: debian-devel-announce@lists.debian.org Don Armstrong (on-list) Don Armstrong (off-list) Prev by Date: Hosting offers for Debian development Previous by thread: Hosting offers for Debian development Index(es): Date Thread | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/asciidoctor-api-options/ | Conversion Options | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Usage Convert Documents Conversion Options 3.0 3.0 2.5 Edit this Page Conversion Options Asciidoctor provides many options that can be passed when converting content. This section explains the most important and commonly used options when converting Asciidoctor content. The options for conversion of a document are held in an instance of the class org.asciidoctor.Options . The builder OptionsBuilder (obtained via Options.builder() ) allows for simple configuration of that instance that can be passed to the respective methods of the Asciidoctor interface. The following example shows how to set the options so that the resulting HTML document is rendered for embedding it into another document. That means that the result only contains the content of a HTML body element: Example for converting to an embeddable document String result = asciidoctor.convert( "Hello World", Options.builder() (1) .standalone(false) (2) .build()); (3) assertThat(result, startsWith("<div ")); 1 Create a new OptionsBuilder that is used to prepare the options with a fluent API. 2 Set the option header_footer to false , meaning that an embeddable document will be rendered, 3 Get the built Options instance and pass it to the conversion method. The convert method is overloaded so org.asciidoctor.Options , org.asciidoctor.OptionsBuild or java.util.Map can be used. attributes This option allows to define document attributes externally. There are several ways to accomplish that. Use Attributes.builder() to obtain a fluent API builder. This is the supported method for its ease of use and type validation. Other way found below have been deprecated since v2.4.4 and may not be available in future releases. Attributes builder initialization Attributes attributes = Attributes.builder() .icons("font") .experimental(true) .attribute("my-attribute", "my-value") .build(); The builder also allows passing a chain of values in a String or Array . Attributes builder initialization as String Attributes attributes = Attributes.builder().arguments("toc numbered").build(); Attributes builder initialization as String array String[] attributesArray = new String[]{"toc", "source-highlighter=coderay"}; Attributes attributes = Attributes.builder().arguments(attributesArray).build(); Create an instance of Attributes and set them as a normal POJO. Attributes instance initialization as POJO Attributes attributes = new Attributes(); attributes.setBackend("pdf"); attributes.setExperimental(true) attributes.setAttribute("my-attribute", "my-value"); It is also possible to use a String of attributes similar to the CLI. Attributes instance initialization as String attributes.setAttributes("toc numbered icons=font"); Directly pass a collection of key-values using Map<String,Object>. Attributes instance initialization as Map Map<String, Object> attributesMap = new HashMap<>(); attributesMap.put("icons", "font"); attributesMap.put("experimental", Boolean.TRUE); attributesMap.put("my-attribute", "my-value"); Attributes attributes = new Attributes(attributesMap); Attributes builder initialization as Map Map<String, Object> attributesMap = new HashMap<>(); attributesMap.put("icons", "font"); attributesMap.put("experimental", Boolean.TRUE); attributesMap.put("my-attribute", "my-value"); Attributes.builder() .attributes(attributesMap); backend Defines the target format for which the document should be converted. Among the possible values are html5 , pdf or docbook . Converting a document to PDF File targetFile = // ... asciidoctor.convert( "Hello World", Options.builder() .backend("pdf") .toFile(targetFile) .safe(SafeMode.UNSAFE) .build()); assertThat(targetFile.length(), greaterThan(0L)); inPlace Tells the converter to store the output to a file adjacent to the input file. This is true by default. Setting inPlace option OptionsBuilder optionsBuilder = Options.builder().inPlace(true); safe Asciidoctor provides security levels that control the read and write access of attributes, the include directive, macros, and scripts while a document is processing. Each level includes the restrictions enabled in the prior security level. All safe modes are defined by the enum org.asciidoctor.SafeMode . The safe modes in order from most insecure to most secure are: UNSAFE A safe mode level that disables any security features enforced by Asciidoctor. This is the default safe mode for the CLI. SAFE This safe mode level prevents access to files which reside outside of the parent directory of the source file. It disables all macros, except the include directive. The paths to include files must be within the parent directory. It allows assets to be embedded in the document. SERVER A safe mode level that disallows the document from setting attributes that would affect the rendering of the document. This level trims the attribute docfile to its relative path and prevents the document from: setting source-highlighter, doctype, docinfo and backend seeing docdir It allows icons and linkcss. SECURE A safe mode level that disallows the document from attempting to read files from the file system and including their contents into the document. Additionally, it: disables icons disables the include directive data can not be retrieved from URIs prevents access to stylesheets and JavaScript files sets the backend to html5 disables docinfo files disables data-uri disables docdir and docfile disables source highlighting Asciidoctor extensions may still embed content into the document depending on whether they honor the safe mode setting. This is the default safe mode for the API. So if you want to render documents in the same way as the CLI does you have to set the safe mode to Unsafe . Without it you will for example not get the stylesheet embedded into the resulting document. Converting a document in unsafe mode File sourceFile = new File("includingcontent.adoc"); String result = asciidoctor.convertFile( sourceFile, Options.builder() .safe(SafeMode.UNSAFE) (1) .toFile(false) (2) .build()); assertThat(result, containsString("This is included content")); 1 Sets the safe mode from SECURE to UNSAFE . 2 Don’t convert the file to another file but to a string so that we can easier verify the contents. The example above will succeed with these two asciidoc files: includingcontent.adoc = Including content include::includedcontent.adoc[] includedcontent.adoc This is included content sourcemap Keeps track of the file and line number for each parsed block. This is useful for tooling applications where the association between the converted output and the source file is important. The default for this option is false . Setting the option sourcemap OptionsBuilder optionsBuilder = Options.builder().sourcemap(true); standalone If true , generates a standalone output document (which includes the shell around the body content, such as the header and footer). When converting to a file, the default value is true . Otherwise, the default value is false . Setting the option sourcemap OptionsBuilder optionsBuilder = Options.builder().standalone(false); This option replaces and works in the same way as the previous headerFooter . templateDirs Specifies a directory of Tilt -compatible templates to be used instead of the default built-in templates. Setting templateDirs option OptionsBuilder optionsBuilder = Options.builder().templateDirs(new File("templates_path")); toFile Via the option toFile it is possible to define if a document should be written to a file at all and to which file. To make the API return the converted document and not write to a file set toFile(false) . To make Asciidoctor write to the default file set toFile(true) . The default file is computed by taking the base name of the input file and adding the default suffix for the target format like .html or .pdf . That is for the input file test.adoc the resulting file would be in the same directory with the name test.html . This is also the way the CLI behaves. To write to a certain file set toFile(targetFile) . This is also necessary if you want to convert string content to files. The following example shows how to convert content to a dedicated file: Example for converting to a dedicated file File targetFile = //... asciidoctor.convert( "Hello World", Options.builder() .toFile(targetFile) (1) .safe(SafeMode.UNSAFE) (2) .build()); assertTrue(targetFile.exists()); assertThat( Files.readString(targetFile.toPath()), containsString("<p>Hello World")); 1 Set the option toFile so that the result will be written to the file pointed to by targetFile . 2 Set the safe mode to UNSAFE so that files can be written. See safe for a description of this option. The Asciidoctor Interface Locate Files Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
http://heisenbug.blogspot.com/2011/10/macs-and-me.html?showComment=1317906285227#main | don't count on finding me: Macs and me skip to main | skip to sidebar don't count on finding me Wednesday, October 5, 2011 Macs and me I am profoundly saddened since I woke up at 4:00am in the morning, and saw the news headline about the passing of Steve Jobs. I have seen this coming for a long time, as my father died in a very similar way back 1993 with only 52. Looking at the thin appearance of Jobs in the last month or even years I constantly get reminded of him. Basically the same story of suffering, loss of weight, liver transplant (in vain), death. RIP, Dad, RIP, Steve. I am writing this on a rusty vintage 2000 PowerBook G4 Titanium, I bought on eBay last year, because the video of my own 2001 TiBook went black. By today's web standards completely inadequate, it serves me well for news reading, terminal logins, etc. My son Pedro got his MacBook Pro 15'' delivered just today. An awesome piece of technology. My father bought the first Mac in 1986, just after opening his practice as a neurologist. This was two years after cutting all strings in Hungary and fleeing to Germany in a pretty bold move. Must have been a moment of total self-overestimation when I promised to my dad "if you buy that Mac Plus I'll write you the best software for it for your doctor's office". A crazy time began. At day the Mac was used to keep patient's data with a DTP program "RagTime", at 5pm I hauled the Mac home (in a big black bag) and started writing the program. Sometimes deep into the night. I used Turbo Pascal (and later MPW) after figuring out that the Lisp environment I preferred simply did not cut it due to insufficient support of the Toolbox. In the morning my father carried the Mac back and powered it up. Less than year later the program was ready for productive work. A Mac SE joined the party and we had a networked doctor's application with a really neat windowed user interface, that would put even today's programs to shame in this regard. There was even a time when we fancied marketing this product, but my university duties and the early death of my father simply negated all plans to this end. When I had my diploma in my hands I picked up the phone and called the guy who sold us the Mac Plus and a copy of "Inside Macintosh" back in '86. In the meantime he founded a pretty successful company around a networked admin solution called 'netOctopus' which was his baby. We occasionally met at Apple developer events and I new that he was a pretty damn good coder. He hired me and I was earning money by programming Macs! So yes, I love Macs and there is no reason that this will change in the foreseeable future. I kept telling to myself, should Jobs die one day, I'll put that Mac Plus (now in my basement and still functional) up for sale at eBay. My thought today: "screw it – too many fond memories attached". Posted by heisenbug at 9:39 PM Labels: family , mac , sadness 3 comments: MARCO ANTONIO MENELAU said... muito bonito gabor. Parabens. homenagemjusta a um grande homemn October 6, 2011 at 2:24 AM Cristina Menelau said... Gostei muito, me emocionei com sua história. Todos lamentamos a morte prematura de Jobs mas, a vida tem dessas surpresas. Um gênio sai de cena, aguardemos que outro apareça para preenchê-la proém, sem jamais esquecer os que se foram. October 6, 2011 at 6:04 AM RecaPortella said... Que história emocionante Gabor! Parabéns por conseguir em palavras descrever momentos e histórias como essa. Triste, porém cheia de ensinamentos em todos os sentidos. Agora é esperar o tempo levar um pouco dessa tristeza e continuar seguindo a vida lembrando sempre dos bons ensinamentos que grandes pessoas com essas nos deixaram! Bjs October 6, 2011 at 10:10 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ►  2022 (1) ►  February (1) ►  2014 (5) ►  November (1) ►  October (1) ►  August (1) ►  July (1) ►  January (1) ►  2013 (5) ►  September (1) ►  August (3) ►  February (1) ►  2012 (2) ►  December (1) ►  September (1) ▼  2011 (7) ►  December (1) ►  November (1) ▼  October (1) Macs and me ►  September (1) ►  August (1) ►  February (1) ►  January (1) ►  2010 (19) ►  December (5) ►  November (6) ►  October (1) ►  August (1) ►  July (2) ►  June (4) ►  2009 (12) ►  November (2) ►  October (1) ►  August (1) ►  June (1) ►  May (1) ►  March (4) ►  January (2) ►  2008 (22) ►  October (1) ►  September (3) ►  August (6) ►  July (3) ►  June (2) ►  May (1) ►  April (3) ►  March (1) ►  February (1) ►  January (1) ►  2007 (20) ►  December (2) ►  November (1) ►  October (1) ►  September (1) ►  August (1) ►  July (14) About Me heisenbug I am here and there. You may encounter me if you try, but no guarantees. Just a hint: I am mostly with my family. View my complete profile   | 2026-01-13T09:30:25 |
https://lists.debian.org/debian-devel-announce/2015/02/msg00004.html | --> Project Secretary appointment [ Date Prev ][ Date Next ] [ Thread Prev ][ Thread Next ] [ Date Index ] [ Thread Index ] Project Secretary appointment To : debian-devel-announce@lists.debian.org Subject : Project Secretary appointment From : Lucas Nussbaum < leader@debian.org > Date : Tue, 10 Feb 2015 08:03:16 +0100 Message-id : < [🔎] 20150210070316.GA16721@xanadu.blop.info > Mail-followup-to : debian-devel@lists.debian.org Dear Project Members, It's that time of the year again: the Project Secretary's appointment is going to expire soon, on February 19th. As per Constitution §7.2, the current Project Secretary and myself have agreed in (re-)appointing Kurt Roeckx as Project Secretary for another term. The new secretary term will start on February 20th, 2015, and last for 1 year. Kurt Roeckx Lucas Nussbaum Attachment: signature.asc Description: Digital signature Reply to: debian-devel-announce@lists.debian.org Lucas Nussbaum (on-list) Lucas Nussbaum (off-list) Prev by Date: MiniDebConf Bucharest. May 16-17, 2015. Call for Talks Next by Date: Updating the delegation for the Debian System Administrators (DSA) Previous by thread: MiniDebConf Bucharest. May 16-17, 2015. Call for Talks Next by thread: Updating the delegation for the Debian System Administrators (DSA) Index(es): Date Thread | 2026-01-13T09:30:25 |
https://rubygems.org/gems/thamble | thamble | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up thamble 1.2.0 Thamble exposes a single method, table, for easily creating HTML tables from enumerable objects. Gemfile: = install: = Versions: 1.2.0 July 07, 2022 (8.5 KB) 1.1.0 November 20, 2019 (9.5 KB) 1.0.2 January 28, 2016 (9 KB) 1.0.1 January 27, 2015 (9 KB) 1.0.0 January 07, 2014 (9 KB) Development Dependencies (3): activesupport >= 4 minitest >= 0 minitest-global_expectations >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 66,094 For this version 6,284 Version Released: July 7, 2022 6:40pm License: MIT Required Ruby Version: >= 1.9.2 Links: Homepage Changelog Source Code Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/register-extensions-manually/ | Manually Registering Extensions with javaExtensionRegistry | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Register Extensions Manually Registering Extensions with javaExtensionRegistry 3.0 3.0 2.5 Edit this Page Manually Registering Extensions with javaExtensionRegistry Extensions can be registered individually accessing the default extension registry directly from the Asciidoctor instance. Asciidoctor asciidoctor = Asciidoctor.Factory.create(); asciidoctor.javaExtensionRegistry() .treeprocessor(Tre.class); There is a method in the API for each extension point. asciidoctor.javaExtensionRegistry() .blockMacro(GistBlockMacroProcessor.class); asciidoctor.javaExtensionRegistry() .inlineMacro(IssueInlineMacroProcessor.class); asciidoctor.javaExtensionRegistry() .block(YellBlockProcessor.class); asciidoctor.javaExtensionRegistry() .includeProcessor(LsIncludeProcessor.class); asciidoctor.javaExtensionRegistry() .preprocessor(CommentPreprocessor.class); asciidoctor.javaExtensionRegistry() .postprocessor(CopyrightFooterPostprocessor.class); asciidoctor.javaExtensionRegistry() .treeprocessor(TerminalCommandTreeprocessor.class); extensionRegistry .docinfoProcessor(RobotsDocinfoProcessor.class); Each method is overloaded to accept: A Class As seen in the examples, in this case AsciidoctorJ will take care of the complete lifecycle (initialization, etc.) of the extension. An instance This is useful when the extension requires pre-initialization or has a complex creation. For example, the extension instance could be managed in a Spring context making use of injected components. A full canonical class name This allows to pass the extension as a String type. This can be used when the extension class is not known at compile time. String name macro name Optional and only for blockMacro , inlineMacro and block . Allows defining the name of the macro if it’s not set in the extension class. Register Extensions Bulk Extension Registration ( Extension Groups ) Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://lists.debian.org/debian-user-catalan/ | Debian Mailing Lists -- Index for debian-user-catalan mailing lists Skip Quicknav About Debian Getting Debian Support Developers' Corner Mailing Lists / Index for debian-user-catalan Debian Mailing Lists debian-user-catalan debian-user in Catalan Support for Debian users that speak Catalan. Language used on this list: Catalan. This list is not moderated; posting is allowed by anyone. Posting address: debian-user-catalan@lists.debian.org Subscribe / Unsubscribe Your email address: See these hints if you're having trouble unsubscribing Archives 2001 [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2002 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2003 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2004 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2005 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2006 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2007 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2008 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2009 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2010 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2011 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2012 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2013 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2014 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2015 [ Jan ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2016 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2017 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2018 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2019 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2020 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2021 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2022 [ Jan ] [ Feb ] [ Apr ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2023 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2024 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ May ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Nov ] [ Dec ] 2025 [ Jan ] [ Feb ] [ Mar ] [ Apr ] [ Jun ] [ Jul ] [ Aug ] [ Sep ] [ Oct ] [ Dec ] List archives get refreshed every 20 minutes. You can link to the most recent page in the archives for this list. Search for: Matching any words Matching all words Syntax help Sort by: Relevance Date (newest first) Hits per page: 10 50 100 Statistics Excerpt from the list usage statistics pages: , . Back to: Debian Lists || Debian Project homepage . Home About Social Contract Code of Conduct Free Software Partners Donations Contact Us Getting Debian Network install CD/USB ISO images CD vendors Pre-installed Debian Packages News Project News Events Documentation Release Info Installation manual Debian Books Support Debian International Security Information Bug reports Mailing Lists Mailing List Archives Ports/Architectures Miscellaneous Help Debian Developers' Corner Site map Search You may submit bugs against the list archives using the lists.debian.org pseudo-package or contact the maintainer at listmaster@lists.debian.org . See the Debian contact page for further information on contacting us. Copyright © 2015 SPI and others; See license terms Debian is a registered trademark of Software in the Public Interest, Inc. | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/sequel_postgresql_triggers | GitHub - jeremyevans/sequel_postgresql_triggers: Database enforced timestamps, immutable columns, and counter/sum caches Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / sequel_postgresql_triggers Public Notifications You must be signed in to change notification settings Fork 16 Star 97 Database enforced timestamps, immutable columns, and counter/sum caches License MIT license 97 stars 16 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights jeremyevans/sequel_postgresql_triggers master Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 100 Commits .github/ workflows .github/ workflows lib lib spec spec .ci.gemfile .ci.gemfile .gitignore .gitignore MIT-LICENSE MIT-LICENSE README.rdoc README.rdoc Rakefile Rakefile sequel_postgresql_triggers.gemspec sequel_postgresql_triggers.gemspec View all files Repository files navigation README MIT license Sequel PostgreSQL Triggers Sequel PostgreSQL Triggers is a small enhancement to Sequel allowing a user to easily handle the following types of columns: Timestamp Columns (Created At/Updated At) Counter/Sum Caches Immutable Columns Touch Propogation Foreign Key Arrays (Referential Integrity Checks) It handles these internally to the database via triggers, so even if other applications access the database (without using Sequel), things will still work (unless the database superuser disables triggers). To use this, load the pg_triggers extension into the Sequel::Database object: DB . extension :pg_triggers Then you can call the pgt_* methods it adds on your Sequel::Database object: DB . pgt_created_at ( :table_name , :created_at ) Most commonly, this is used in migrations, with a structure similar to: Sequel . migration do up do extension :pg_triggers pgt_created_at ( :table_name , :created_at , :function_name => :table_name_set_created_at , :trigger_name => :set_created_at ) end down do drop_trigger ( :table_name , :set_created_at ) drop_function ( :table_name_set_created_at ) end end Note that you only need to load this extension when defining the triggers, you don’t need to load this extension when your application is running. To use any of these methods before PostgreSQL 9.0, you have to add the plpgsql procedural language to PostgreSQL, which you can do with: DB . create_language ( :plpgsql ) If you want to load this extension globally for all PostgreSQL databases, you can do: require 'sequel_postgresql_triggers' However, global modification is discouraged and only remains for backwards compatibility. Triggers All of the public methods this extension adds take the following options in their opts hash: :function_name The name of the function to use. This is important to specify if you want an easy way to drop the function. :trigger_name The name of the trigger to use. This is important to specify if you want an easy way to drop the trigger. Methods that create trigger functions which can result in additional triggers firing (due to INSERT/UPDATE/DELETE queries) also take the following option: :trigger_depth_limit If given, should be an integer specifying the maximum trigger depth that the trigger will operate under. Any higher depth will result in the trigger silently exiting. This can be used to prevent unbounded trigger recursion. A value of true is interpreted as 1. Created At Columns - pgt_created_at pgt_created_at takes the table and column given and makes it so that upon insertion, the column is set to the CURRENT_TIMESTAMP, and that upon update, the column’s value is always set to the previous value. This is sort of like an immutable column, but it doesn’t bring up an error if you try to change it, it just ignores it. Arguments: table name of table column column in table that should be a created at timestamp column opts option hash Updated At Columns - pgt_updated_at Similar to pgt_created_at, takes a table and column and makes it so that upon insertion, the column is set to CURRENT_TIMESTAMP. It differs that upon update, the column is also set to CURRENT_TIMESTAMP. Arguments: table name of table column column in table that should be a updated at timestamp column opts options hash Counter Cache - pgt_counter_cache This takes many arguments and sets up a counter cache so that when the counted table is inserted to or deleted from, records in the main table are updated with the count of the corresponding records in the counted table. The counter cache column must have a default of 0 for this to work correctly. Use pgt_sum_cache with a Sequel expression in summed_column to handle any custom logic such as a counter cache that only counts certain rows. Arguments: main_table name of table holding counter cache column main_table_id_column column in main table matching counted_table_id_column in counted_table counter_column column in main table containing the counter cache counted_table name of table being counted counted_table_id_column column in counted_table matching main_table_id_column in main_table opts options hash Sum Cache - pgt_sum_cache Similar to pgt_counter_cache, except instead of storing a count of records in the main table, it stores the sum on one of the columns in summed table. The sum cache column must have a default of 0 for this to work correctly. Use a Sequel expression in summed_column to handle any custom logic such as a counter cache that only counts certain rows, or a sum cache that sums the length of a string column. Arguments: main_table name of table holding counter cache column main_table_id_column column in main table matching summed_table_id_column in summed_table sum_column column in main table containing the sum cache summed_table name of table being summed summed_table_id_column column in summed_table matching main_table_id_column in main_table summed_column column in summed_table being summed or a Sequel expression to be evaluated in the context of summed_table opts options hash Sum Through Many Cache - pgt_sum_through_many_cache Similar to pgt_sum_cache, except instead of a one-to-many relationship, it supports a many-to-many relationship with a single join table. The sum cache column must have a default of 0 for this to work correctly. Use a Sequel expression in summed_column to handle any custom logic. See pgt_sum_cache for details. This takes a single options hash argument, supporting the following options in addition to the standard options: :main_table name of table holding sum cache column :main_table_id_column primary key column in main table referenced by main_table_fk_column (default: :id) :sum_column column in main table containing the sum cache, must be NOT NULL and default to 0 :summed_table name of table being summed :summed_table_id_column primary key column in summed_table referenced by summed_table_fk_column (default: :id) :summed_column column in summed_table being summed or a Sequel expression to be evaluated in the context of summed_table, must be NOT NULL :join_table name of table which joins main_table with summed_table :join_trigger_name name of trigger for join table :join_function_name name of trigger function for join table :main_table_fk_column column in join_table referencing main_table_id_column, must be NOT NULL :summed_table_fk_column column in join_table referencing summed_table_id_column, must be NOT NULL Immutable Columns - pgt_immutable This takes a table name and one or more column names, and adds an update trigger that raises an exception if you try to modify the value of any of the columns. Arguments: table name of table *columns All columns in the table that should be immutable. Can end with options hash. Touch Propagation - pgt_touch This takes several arguments and sets up a trigger that watches one table for changes, and touches timestamps of related rows in a separate table. Arguments: main_table name of table that is being watched for changes touch_table name of table that needs to be touched column name of timestamp column to be touched expr hash or array that represents the columns that define the relationship opts options hash Foreign Key Arrays - pgt_foreign_key_array This takes a single options hash, and sets up triggers on both tables involved. The table with the foreign key array has insert/update triggers to make sure newly inserted/updated rows reference valid rows in the referenced table. The table being referenced has update/delete triggers to make sure the value before update or delete is not still being referenced. Note that this will not catch all referential integrity violations, but it should catch the most common ones. Options: :table table with foreign key array :column foreign key array column :referenced_table table referenced by foreign key array :referenced_column column referenced by foreign key array (generally primary key) :referenced_function_name function name for trigger function on referenced table :referenced_trigger_name trigger name for referenced table Force Defaults - pgt_force_defaults This takes 2 arguments, a table and a hash of column default values, and sets up an insert trigger that will override user submitted or database default values and use the values given when setting up the trigger. This is mostly useful in situations where multiple database accounts are used where one account has insert permissions but not update permissions, and you want to ensure that inserted rows have specific column values to enforce security requirements. Arguments: table The name of the table defaults A hash of default values to enforce, where keys are column names and values are the default values to enforce JSON Audit Logging - pgt_json_audit_log_setup and pg_json_audit_log These methods setup an auditing function where updates and deletes log the previous values to a central auditing table in JSON format. pgt_json_audit_log_setup This creates an audit table and a trigger function that will log previous values to the audit table. This returns the name of the trigger function created, which should be passed to pgt_json_audit_log . Arguments: table The name of the table storing the audit logs. Options: function_opts Options to pass to create_function when creating the trigger function. The audit log table will store the following columns: txid The 64-bit transaction ID for the transaction that made the modification (txid_current()) at The timestamp of the transaction that made the modification (CURRENT_TIMESTAMP) user The database user name that made the modification (CURRENT_USER) schema The schema containing the table that was modified (TG_TABLE_SCHEMA) table The table that was modified (TG_TABLE_NAME) action The type of modification, either DELETE or UPDATE (TG_OP) prior A jsonb column with the contents of the row before the modification (to_jsonb(OLD)) pgt_json_audit_log This adds a trigger to the table that will log previous values to the audting table for updates and deletes. Arguments: table The name of the table to audit function The name of the trigger function to call to log changes Note that it is probably a bad idea to use the same table argument to both pgt_json_audit_log_setup and pgt_json_audit_log . Caveats If you have defined counter or sum cache triggers using this library before version 1.6.0, you should drop them and regenerate them if you want the triggers to work correctly with queries that use INSERT ... ON CONFLICT DO NOTHING . When restoring a data-only migration with pg_dump , you may need to use --disable-triggers for it to restore correctly, and you will need to manually enforce data integrity if you are doing partial restores and not full restores. License This library is released under the MIT License. See the MIT-LICENSE file for details. Author Jeremy Evans <code@jeremyevans.net> About Database enforced timestamps, immutable columns, and counter/sum caches Resources Readme License MIT license Uh oh! There was an error while loading. Please reload this page . Activity Stars 97 stars Watchers 3 watching Forks 16 forks Report repository Releases 14 tags Packages 0 No packages published Uh oh! There was an error while loading. Please reload this page . Contributors 9 Languages Ruby 100.0% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://rubygems.org/gems/autoforme | autoforme | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up autoforme 1.14.0 AutoForme is an web administrative console for Sequel::Model that supports Roda, Sinatra, and Rails. It offers the following features: * Create, update, edit, and view model objects * Browse and search model objects * Edit many-to-many relationships for model objects * Easily access associated objects * Support autocompletion for all objects * Allow customization for all likely configuration points, using any parameters available in the request Gemfile: = install: = Versions: 1.14.0 October 02, 2025 (30.5 KB) 1.13.0 July 10, 2024 (29.5 KB) 1.12.0 June 29, 2022 (29.5 KB) 1.11.0 November 30, 2021 (44.5 KB) 1.10.0 August 27, 2021 (44 KB) Show all versions (25 total) Runtime Dependencies (4): enum_csv >= 0 forme >= 2.0.0 rack >= 0 sequel >= 3.0.0 Development Dependencies (10): capybara >= 2.1.0 minitest >= 5.0.0 minitest-global_expectations >= 0 minitest-hooks >= 1.1.0 rack_csrf >= 0 rails >= 0 roda >= 0 sinatra >= 0 sinatra-flash >= 0 tilt >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 81,507 For this version 2,849 Version Released: October 2, 2025 9:12pm License: MIT Required Ruby Version: >= 1.9.2 Links: Homepage Changelog Source Code Documentation Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/docinfo-processor/ | Docinfo Processor | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Write an Extension Docinfo Processor 3.0 3.0 2.5 Edit this Page Docinfo Processor Docinfo Processors are primarily targeted for the HTML and DocBook5 formats. A Docinfo Processor basically allows to add content to the HTML header or at the end of the HTML body. For the DocBook5 target format a Docinfo Processor can add content to the info element or at the very end of the document, just before the closing tag of the root element. Our example Docinfo Processor will add a robots meta tag to the head of the HTML output: A Docinfo Processor that adds a robots meta tag import org.asciidoctor.ast.Document; import org.asciidoctor.extension.DocinfoProcessor; import org.asciidoctor.extension.Location; import org.asciidoctor.extension.LocationType; @Location(LocationType.HEADER) (1) public class RobotsDocinfoProcessor extends DocinfoProcessor { (2) @Override public String process(Document document) { return "<meta name=\"robots\" content=\"index,follow\">"; (3) } } 1 The Location annotation defines whether the result of this Docinfo Processor should be added to the header or the footer of the document. Content is added to the header via LocationType.HEADER and to the footer via LocationType.FOOTER . 2 Every Docinfo Processor must extend the class DocinfoProcessor and implement the process() method. 3 Our example implementation simply returns the meta tag as a string. For the example to work make sure: standalone option is not set to true , otherwise these will not be added to the document. safe mode option is set to at least SECURE Options configuration example Options.builder() .standalone(true) .safe(SafeMode.SERVER) .build(); Treeprocessor Register Extensions Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://rubygems.org/gems/rack-test | rack-test | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up rack-test 2.2.0 Rack::Test is a small, simple testing API for Rack apps. It can be used on its own or as a reusable starting point for Web frameworks and testing libraries to build on. Gemfile: = install: = Versions: 2.2.0 December 23, 2024 (20.5 KB) 2.1.0 March 14, 2023 (20.5 KB) 2.0.2 June 28, 2022 (21 KB) 2.0.1 June 27, 2022 (20.5 KB) 2.0.0 June 24, 2022 (20.5 KB) Show all versions (31 total) Runtime Dependencies (1): rack >= 1.3 Development Dependencies (3): minitest >= 5.0 minitest-global_expectations >= 0 rake >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans, Bryan Helmkamp SHA 256 checksum: = ← Previous version Total downloads 727,766,787 For this version 68,356,678 Version Released: December 23, 2024 6:51pm License: MIT Required Ruby Version: >= 2.0 Links: Homepage Changelog Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://nixos.org/ | Nix & NixOS | Declarative builds and deployments Explore Download Learn Governance Community Blog Donate Search Framework Partnership Announcement Read Announcement Declarative builds and deployments. Nix is a tool that takes a unique approach to package management and system configuration. Learn how to make reproducible, declarative and reliable systems. Download Get started Reproducible Nix builds packages in isolation from each other. This ensures that they are reproducible and don’t have undeclared dependencies, so if a package works on one machine, it will also work on another. Declarative Nix makes it trivial to share development and build environments for your projects, regardless of what programming languages and tools you’re using. Reliable Nix ensures that installing or upgrading one package cannot break other packages . It allows you to roll back to previous versions , and ensures that no package is in an inconsistent state during an upgrade. Choose from over 120 000 Packages The Nix Packages collection ( Nixpkgs ) offers a large selection of packages for the Nix package manager. Search NixOS Packages and Options Search Examples Try new tools without fear Multiple languages, one tool Declarative dev-environments Minimal docker images Declarative cloud images Test your configurations Footer The Project Channel Status Packages search Options search Reproducible Builds Status Security Branding Summer of Nix Devices Get in Touch Forum Matrix Chat Commercial support Contribute Contributing Guide Donate Become a Sponsor Stay up to Date Blog Research & Publications NixOS Weekly (Archive) Copyright © 2026 NixOS contributors Imprint Privacy Policy CC-BY-SA-4.0 Connect with us: Scroll to top | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/installation/ | Installation | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Installation 3.0 3.0 2.5 Edit this Page Installation To start using AsciidoctorJ, you need to add the required dependency to the dependency management system of your choice, Maven, Gradle or Apache Ivy. If you don’t use a Dependency Management system please check the dependency graph and add all jars in it to your classpath. Declaring the dependency in a Maven build file (i.e., pom.xml) <dependencies> <dependency> <groupId>org.asciidoctor</groupId> <artifactId>asciidoctorj</artifactId> <version>3.0.0</version> (1) </dependency> </dependencies> Declaring the dependency in a Gradle build file (e.g., build.gradle) dependencies { compile 'org.asciidoctor:asciidoctorj:3.0.0' } Declaring the dependency in an SBT build file (e.g., build.sbt) libraryDependencies += "org.asciidoctor" % "asciidoctorj" % "3.0.0" (1) 1 Specifying the version of AsciidoctorJ implicitly selects the version of Asciidoctor Declaring the dependency in a Leiningen build file (e.g., project.clj) :dependencies [[org.asciidoctor/asciidoctorj "3.0.0"]] In addition to using AsciidoctorJ directly, you can invoke it as part of your build using the Maven or Gradle plugin. How to Install and Use the Asciidoctor Maven Plugin How to Install and Use the Asciidoctor Gradle Plugin The versions of Asciidoctor and AsciidoctorJ no longer align since version 1.6.0 of AsciidoctorJ. Please check the corresponding release notes to find out which version of Asciidoctor is packaged if you are embedding the library. If you use the distribution you can call asciidoctorj --version to get the version of Asciidoctor that is embedded in AsciidoctorJ. Distribution Command Line Interface Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/convert-to-epub3/ | Converting to EPUB3 | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Usage Convert Documents Converting to EPUB3 3.0 3.0 2.5 Edit this Page Converting to EPUB3 The Asciidoctor EPUB3 gem (asciidoctor-epub3) is bundled inside the AsciidoctorJ EPUB3 jar (asciidoctorj-epub3). To use it, simply add the asciidoctorj-epub3 jar to your dependencies. The version of the AsciidoctorJ EPUB3 jar aligns with the version of the Asciidoctor EPUB3 gem. Here’s how you can add the AsciidoctorJ EPUB3 jar to your Maven dependencies: <dependencies> <dependency> <groupId>org.asciidoctor</groupId> <artifactId>asciidoctorj-epub3</artifactId> <version>1.5.1</version> <scope>runtime</scope> </dependency> </dependencies> Once you’ve added the AsciidoctorJ EPUB3 jar to your classpath, you can set the backend attribute to epub3 . The document will be converted to the EPUB3 format. The asciidoctor-epub3 gem is alpha. While it can be used successfully, there may be bugs and its functionality may change in incompatible ways before the first stable release. In other words, by using it, you are also testing it ;) Let’s see an example of how to use AsciidoctorJ with the EPUB3 converter. spine.adoc = Book Title Author Name :imagesdir: images (1) include::content-document.adoc[] (2) 1 The EPUB3 converter requires the value of the imagesdir attribute to be images . 2 The EPUB3 converter must be run on a spine document that has at least one include directive (and no other body content) in order to function properly. content-document.adoc = Content Title Author Name [abstract] This is the actual content. == First Section And off we go. And finally we can convert the document to EPUB3 using AsciidoctorJ. asciidoctor.convertFile(new File("spine.adoc"), Options.builder().safe(SafeMode.SAFE).backend("epub3").build()); (1) (2) assertThat(new File("target/test-classes/index.epub").exists(), is(true)); 1 Currently, the EPUB3 converter must be run in SAFE or UNSAFE mode due to a bug 2 epub3 is the name of the backend that must be set to convert to EPUB3. Examples Ruby Runtime Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://rubygems.org/gems/sequel-annotate | sequel-annotate | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up sequel-annotate 1.7.0 sequel-annotate annotates Sequel models with schema information. By default, it includes information on columns, indexes, and foreign key constraints for the current table. On PostgreSQL, this includes more advanced information, including check constraints, triggers, comments, and foreign keys constraints for other tables that reference the current table. Gemfile: = install: = Versions: 1.7.0 May 20, 2021 (16 KB) 1.6.0 October 06, 2020 (15.5 KB) 1.5.0 May 04, 2020 (14.5 KB) 1.4.0 November 15, 2018 (12.5 KB) 1.3.1 September 27, 2018 (12 KB) Show all versions (9 total) Runtime Dependencies (1): sequel >= 4 Development Dependencies (4): minitest >= 5 minitest-global_expectations >= 0 pg >= 0 sqlite3 >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 640,747 For this version 415,672 Version Released: May 20, 2021 3:47pm License: MIT Required Ruby Version: >= 1.8.7 Links: Homepage Changelog Source Code Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/logs-handling/ | Logs Handling API | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Logs Handling API 3.0 3.0 2.5 Edit this Page Logs Handling API This API is inspired by Java Logging API (JUL). If you are familiar with java.util.logging.* you will see familiar analogies with some of its components. AsciidoctorJ (v1.5.7+) offers the possibility to capture messages generated during document rendering. While the API described here explains how to forward these messages to any receiver, AsciidoctorJ already logs all messages to the java.util.logging Logger with the name asciidoctor . The default log level of java.util.logging is INFO. That means you might see messages for provisional messages about possible invalid xrefs which could be valid xrefs that Asciidoctor just can’t resolve. The behavior of the java.util.logging logger can be configured with a properties file. For other ways to configure this behavior please check the documentation of java.util.logging.LogManager . To restrict the logger to only log messages with severity WARNING or higher create this file: logging.properties handlers = java.util.logging.ConsoleHandler .level = WARNING java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter java.util.logging.SimpleFormatter.format = %3$ To use this configuration when running asciidoctorj via the CLI pass the location of the file like this: # JAVA_OPTS="-Djava.util.logging.config.file=$PWD/logging.properties" asciidoctorj document.adoc Logs Handling API The easiest way to capture messages is registering a LogHandler through the Asciidoctor instance. Registering a LogHandler Asciidoctor asciidoctor = Asciidoctor.Factory.create(); asciidoctor.registerLogHandler(new LogHandler() { (1) @Override public void log(LogRecord logRecord) { System.out.println(logRecord.getMessage()); } }); 1 Use registerLogHandler to register one or more handlers. The log method in the org.asciidoctor.log.LogHandler interface provides a org.asciidoctor.log.LogRecord that exposes the following information: Severity severity Severity level of the current record. A log record always has one of the 6 severity levels: DEBUG INFO WARN ERROR FATAL UNKNOWN Cursor cursor Information about the location of the event, contains: LineNumber: relative to the file where the message occurred. Path: source file simple name, or <stdin> value when converting from a String. Dir: absolute path to the source file parent directory, or the execution path when converting from a String. File: absolute path to the source file, or null when converting from a String. These will point to the correct source file, even when this is included from another. String message Descriptive message about the event. String sourceFileName Contains the value <script> . For the source filename see Cursor above. String sourceMethodName The Asciidoctor Ruby engine method used to convert the file; convertFile or convert whether you are converting a File or a String. Logs Handling SPI Similarly to AsciidoctorJ extensions, the Log Handling API provides an alternate method to register Handlers without accessing Asciidoctor instance. Start creating a normal LogHandler implementation. package my.asciidoctor.log.MemoryLogHandler; import java.util.ArrayList; import java.util.List; import org.asciidoctor.log.LogHandler; import org.asciidoctor.log.LogRecord; /** * Stores LogRecords in memory for later analysis. */ public class MemoryLogHandler implements LogHandler { private List<LogRecord> logRecords = new ArrayList<>(); @Override public void log(LogRecord logRecord) { logRecords.add(record); } public List<LogRecord> getLogRecords() { return logRecords; } } Next, create a file called org.asciidoctor.log.LogHandler inside META-INF/services with the implementation’s full qualified name. META-INF/services/org.asciidoctor.log.LogHandler my.asciidoctor.log.MemoryLogHandler And that’s all. Now when a .jar file containing the previous structure is dropped inside classpath of AsciidoctorJ, the handler will be registered automatically. Register a Ruby Extension Read the Document Tree Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/ruby-refrigerator/actions/workflows/ci.yml | CI · Workflow runs · jeremyevans/ruby-refrigerator · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / ruby-refrigerator Public Notifications You must be signed in to change notification settings Fork 4 Star 283 Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights Actions: jeremyevans/ruby-refrigerator Actions --> All workflows Workflows CI CI Show more workflows... Management Caches CI CI Actions Loading... Loading Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> will be ignored since log searching is not yet available Show workflow options Create status badge Create status badge Loading Uh oh! There was an error while loading. Please reload this page . ci.yml --> will be ignored since log searching is not yet available 9 workflow runs 9 workflow runs Event Filter by Event Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching events. Status Filter by Status Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching statuses. Branch Filter by Branch Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching branches. Actor Filter by Actor Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching users. Add Ruby 4.0 to CI CI #45: Commit a4d5a25 pushed by jeremyevans 18m 13s master master 18m 13s View workflow file Use SimpleCov.add_filter block instead of string CI #44: Commit c6fe201 pushed by jeremyevans 1m 15s master master 1m 15s View workflow file Add JRuby 10.0 to CI CI #43: Commit 6b0fffd pushed by jeremyevans 11m 45s master master 11m 45s View workflow file Change ostruct require to erb require in test CI #42: Commit 35e4b8e pushed by jeremyevans 1m 19s master master 1m 19s View workflow file Work with ubuntu-latest using 24.04 by default in CI CI #41: Commit be6a7bb pushed by jeremyevans 1m 18s master master 1m 18s View workflow file Bump version to 1.8.0 CI #40: Commit b1f31d9 pushed by jeremyevans 1m 16s master master 1m 16s View workflow file Add Ruby 3.4 to CI CI #39: Commit 2ff5a29 pushed by jeremyevans 1m 16s master master 1m 16s View workflow file Use -W:strict_unused_block when running tests on Ruby 3.4+ CI #38: Commit f8f53c0 pushed by jeremyevans 1m 36s master master 1m 36s View workflow file Remove freezing of Gem::SpecificGemNotFoundException in Ruby 3.3 CI #37: Commit 6afe8b2 pushed by jeremyevans 1m 18s master master 1m 18s View workflow file You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/simple_mailer | GitHub - jeremyevans/simple_mailer: Simple email library with testing support Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / simple_mailer Public Notifications You must be signed in to change notification settings Fork 2 Star 5 Simple email library with testing support License MIT license 5 stars 2 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights jeremyevans/simple_mailer master Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 45 Commits .github/ workflows .github/ workflows lib lib spec spec .ci.gemfile .ci.gemfile .gitignore .gitignore MIT-LICENSE MIT-LICENSE README README Rakefile Rakefile simple_mailer.gemspec simple_mailer.gemspec View all files Repository files navigation README MIT license = simple_mailer simple_mailer is a very simple email library for ruby, with testing support. It uses ruby's standard net/smtp library to send the emails. Configuration is limited to setting the server that the email is sent to (defaults to localhost). Testing support is limited to appending the emails that would have been sent to an array. simple_mailer can be installed with: gem install simple_mailer Source is available at github: http://github.com/jeremyevans/simple_mailer == Usage There is no required configuration, you can use simple_mailer immediately: require 'simple_mailer' SimpleMailer.send_email('from@from.com', 'to@to.com', 'Subject', 'Body', 'HeaderKey'=>'HeaderValue') Or, you can include the SimpleMailer module in other classes: class Mailer include SimpleMailer def initialize(subject, body) @subject = subject @body = body self.smtp_server = 'smtp.example.com' end def email(from, to) send_email(from, to, @subject, @body) end end Mailer.new('Subject', 'Body').email('from@from.com', 'to@to.com') == Special Headers There are four special headers that simple_mailer processes: :smtp_to :: Override the actual SMTP recipients without modifying the message. :smtp_from :: Override the actual STMP sender without modifying the message. :cc :: Add a recipient to the message and include a CC header with that recipient. :bcc :: Add an recipient to the message without including that information in the message headers. All other headers are used verbatim in the message. == Configuration You can pass in options just like with the Mail gem. SimpleMailer.smtp_settings.update( :address => "smtp.gmail.com", :port => 587, :domain => "localhost", :user_name => "bob", :password => "secret", :authentication => :plain, ) == Testing Testing support is probably the main reason to use simple_mailer over using net/smtp directly. After you enter test mode, emails you send are available via the emails_sent option: SimpleMailer.test_mode! SimpleMailer.emails_sent # [] SimpleMailer.send_email('from@from.com', 'to@to.com', 'S', 'B') SimpleMailer.emails_sent # [[message, 'from@from.com', 'to@to.com']] == Author Jeremy Evans (code@jeremyevans.net) About Simple email library with testing support Resources Readme License MIT license Uh oh! There was an error while loading. Please reload this page . Activity Stars 5 stars Watchers 1 watching Forks 2 forks Report repository Releases No releases published Packages 0 No packages published Uh oh! There was an error while loading. Please reload this page . Contributors 2 Uh oh! There was an error while loading. Please reload this page . Languages Ruby 100.0% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctor/latest/html-backend/skip-front-matter/ | Skip Front Matter | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets Asciidoctor Features What’s New in 2.0 Install and Update Supported Platforms Install Using Ruby Packaging Install Using Linux Packaging Install on macOS Install on Windows Convert Your First File Converters Available Converters Custom Converter Converter Templates Convertible Contexts Generate HTML Stylesheets Default Stylesheet Stylesheet Modes Apply a Custom Stylesheet Embed a CodeRay or Pygments Stylesheet Manage Images Use Local Font Awesome Add a Favicon Verbatim Block Line Wrapping Skip Front Matter Generate DocBook Generate Manual Pages Process AsciiDoc Using the CLI asciidoctor(1) Specify an Output File Process Multiple Source Files Pipe Content Through the CLI Set Safe Mode CLI Options Process AsciiDoc Using the API Load and Convert Files Load and Convert Strings Generate an HTML TOC Set Safe Mode Enable the Sourcemap Catalog Assets Find Blocks API Options Safe Modes Safe Mode Specific Content AsciiDoc Tooling Syntax Highlighting Highlight.js Rouge CodeRay Pygments Custom Adapter STEM Processing MathJax and HTML Asciidoctor Mathematical STEM Support in the DocBook Toolchain AsciiMath Gem Extensions Register Extensions Log from an Extension Preprocessor Tree Processor Postprocessor Docinfo Processor Block Processor Compound Block Processor Block Macro Processor Inline Macro Processor Include Processor Localization Support Errors and Warnings Migration Guides Upgrade from Asciidoctor 1.5.x to 2.0 Migrate from AsciiDoc.py Migrate from DocBook XML Migrate from Markdown Migrate from Confluence XHTML Migrate from MS Word Asciidoctor 2.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community Asciidoctor Generate HTML Skip Front Matter Edit this Page Skip Front Matter Front matter for static site generators Many static site generators (i.e., Jekyll, Middleman) rely on front matter added to the top of the document to determine how to convert the content. Front matter typically starts on the first line of a file and is bounded by block delimiters (e.g., --- ). Here’s an example of a document that contains front matter: --- (1) layout: default (2) --- (3) = Document Title content 1 Front matter opening delimiter 2 Front matter data 3 Front matter closing delimiter The static site generator removes these lines before passing the document to the AsciiDoc processor to be converted. Outside of the tool, however, these extra lines can throw off the processor. skip-front-matter attribute If the skip-front-matter attribute is set via the API or CLI (e.g., -a skip-front-matter ), Asciidoctor will recognize the front matter and consume it before parsing the document. Asciidoctor stores the content it extracts in the front-matter attribute to make it available for integrations. Asciidoctor also removes front matter when reading include files . Verbatim Block Line Wrapping Generate DocBook Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/extensions/treeprocessor/ | Treeprocessor | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Extensions API Write an Extension Treeprocessor 3.0 3.0 2.5 Edit this Page Treeprocessor A Treeprocessor gets the whole AST and may do whatever it likes with the document tree. Examples for Treeprocessors could insert blocks, add roles to nodes with a certain content, etc. Treeprocessors are called by Asciidoctor at the end of the loading process after Preprocessors, BlockProcessors, MacroProcessors and IncludeProcessors but before Postprocessors that are called after the conversion process. Our example Treeprocessor will recognize paragraphs that contain terminal scripts like below, make listing blocks from them and add the role terminal . The custom role will allows us to customize the style. Example AsciiDoc document containing a terminal script To fetch the content of the URL invoke the following: $ curl -v http://127.0.0.1:8080 * Trying 127.0.0.1... * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.41.0 > Host: 127.0.0.1:8080 > Accept: */* > < HTTP/1.1 200 OK ... As the first line of the second block starts with a $ sign the whole block should become a listing block. The result when rendering this document with our Treeprocessor should be the same as if the document looked like this: To fetch the content of the URL invoke the following: [.terminal] ---- $ curl -v http://127.0.0.1:8080 * Trying 127.0.0.1... * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.41.0 > Host: 127.0.0.1:8080 > Accept: */* > < HTTP/1.1 200 OK ... ---- Note that a BlockProcessor would not work for this task, as a BlockProcessor requires a block name for which it is called. However, in this case the only way to identify this type of blocks is the beginning of the first line. The Treeprocessor could look like this: A Treeprocessor that processes terminal scripts. import org.asciidoctor.ast.Block; import org.asciidoctor.ast.Document; import org.asciidoctor.ast.StructuralNode; import org.asciidoctor.extension.Treeprocessor; import java.util.HashMap; import java.util.List; import java.util.Map; public class TerminalCommandTreeprocessor extends Treeprocessor { (1) public TerminalCommandTreeprocessor() {} @Override public Document process(Document document) { processBlock((StructuralNode) document); (2) return document; } private void processBlock(StructuralNode block) { List<StructuralNode> blocks = block.getBlocks(); for (int i = 0; i < blocks.size(); i++) { final StructuralNode currentBlock = blocks.get(i); if(currentBlock instanceof StructuralNode) { if ("paragraph".equals(currentBlock.getContext())) { (3) List<String> lines = ((Block) currentBlock).getLines(); if (lines != null && lines.size() > 0 && lines.get(0).startsWith("$")) { blocks.set(i, convertToTerminalListing((Block) currentBlock)); } } else { // It's not a paragraph, so recursively descend into the child node processBlock(currentBlock); } } } } public Block convertToTerminalListing(Block originalBlock) { Map<Object, Object> options = new HashMap<Object, Object>(); options.put("subs", ":specialcharacters"); Block block = createBlock( (4) (StructuralNode) originalBlock.getParent(), "listing", originalBlock.getLines(), originalBlock.getAttributes(), options); block.addRole("terminal"); (5) return block; } } 1 Every Treeprocessor must extend org.asciidoctor.extension.Treeprocessor and implement the method process(Document) . 2 The implementation basically iterates over the tree and invokes processBlock() for every node. 3 The method processBlock() checks for every node if it is a paragraph that has a first line beginning with a $ . If it encounters such a block it replaces it with the block created in the method convertToTerminalListing() . Otherwise it descends into the AST searching for these blocks. 4 When creating the new block we reuse the parent of the original block. The context of the new block has to be listing to get a source block. The content can be simply taken from the original block. We add the option 'subs' with the value ':specialcharacters' so that special characters are substituted, i.e. > and < will be replaced with &gt; and &lt; respectively. 5 Finally, we add the role of the node to terminal , which will result in the div containing the listing having the class terminal . Postprocessor Docinfo Processor Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctor/latest/install/ | Install and Update | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets Asciidoctor Features What’s New in 2.0 Install and Update Supported Platforms Install Using Ruby Packaging Install Using Linux Packaging Install on macOS Install on Windows Convert Your First File Converters Available Converters Custom Converter Converter Templates Convertible Contexts Generate HTML Stylesheets Default Stylesheet Stylesheet Modes Apply a Custom Stylesheet Embed a CodeRay or Pygments Stylesheet Manage Images Use Local Font Awesome Add a Favicon Verbatim Block Line Wrapping Skip Front Matter Generate DocBook Generate Manual Pages Process AsciiDoc Using the CLI asciidoctor(1) Specify an Output File Process Multiple Source Files Pipe Content Through the CLI Set Safe Mode CLI Options Process AsciiDoc Using the API Load and Convert Files Load and Convert Strings Generate an HTML TOC Set Safe Mode Enable the Sourcemap Catalog Assets Find Blocks API Options Safe Modes Safe Mode Specific Content AsciiDoc Tooling Syntax Highlighting Highlight.js Rouge CodeRay Pygments Custom Adapter STEM Processing MathJax and HTML Asciidoctor Mathematical STEM Support in the DocBook Toolchain AsciiMath Gem Extensions Register Extensions Log from an Extension Preprocessor Tree Processor Postprocessor Docinfo Processor Block Processor Compound Block Processor Block Macro Processor Inline Macro Processor Include Processor Localization Support Errors and Warnings Migration Guides Upgrade from Asciidoctor 1.5.x to 2.0 Migrate from AsciiDoc.py Migrate from DocBook XML Migrate from Markdown Migrate from Confluence XHTML Migrate from MS Word Asciidoctor 2.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community Asciidoctor Install and Update Edit this Page Install and Update To simplify installation, Asciidoctor is packaged as a gem and published to the gem hosting service at RubyGems.org . Asciidoctor is also distributed as a managed package for popular Linux distributions and macOS. In addition to running on Ruby, Asciidoctor can be executed on a JVM using AsciidoctorJ or in any JavaScript environment (including the browser) using Asciidoctor.js . Installation methods Asciidoctor can be installed using: Bundler, the package manager for popular Linux distributions, Homebrew or MacPorts for macOS, the gem install command (recommended for Windows users), or the Asciidoctor Docker image To update or uninstall Asciidoctor, you should use the same method you used to install it. Bundler is the preferred method of installation as it keeps the gems scoped to your project or workspace. However, this method of installation does not make the asciidoctor command available globally in your terminal. That’s when a package manager is more appropriate. The benefit of using your operating system’s package manager to install the gem is that it adds the asciidoctor command to your PATH and it handles installing Ruby and the RubyGems library if those packages are not already installed on your machine. On the other hand, if you’re familiar with Docker, using the Asciidoctor Docker image may give you the best isolation from your system. What’s New in 2.0 Supported Platforms Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
http://hackage.haskell.org/package/semigroupoids-1.1.2/docs/doc-index.html | semigroupoids-1.1.2: Haskell 98 semigroupoids: Category sans id (Index) Contents Index semigroupoids-1.1.2: Haskell 98 semigroupoids: Category sans id Index $> Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus -<- Data.Functor.Bind -<< Data.Functor.Bind ->- Data.Functor.Bind .> Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus .>> Data.Bifunctor.Apply <!> Data.Functor.Alt , Data.Functor.Plus <$ Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus <$> Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus <. Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus <..> Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus <.> Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus <<$>> Data.Bifunctor.Apply <<. Data.Bifunctor.Apply <<..>> Data.Bifunctor.Apply <<.>> Data.Bifunctor.Apply >>- Data.Functor.Bind Alt Data.Functor.Alt , Data.Functor.Plus apDefault Data.Functor.Bind Apply Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus Biapply Data.Bifunctor.Apply bifold1 Data.Semigroup.Bifoldable Bifoldable1 Data.Semigroup.Bifoldable bifoldMap1 Data.Semigroup.Bifoldable bifoldMap1Default Data.Semigroup.Bitraversable bifoldMapDefault1 Data.Semigroup.Bifoldable bifor1_ Data.Semigroup.Bifoldable Bifunctor Data.Bifunctor.Apply bilift2 Data.Bifunctor.Apply bilift3 Data.Bifunctor.Apply bimap Data.Bifunctor.Apply Bind Data.Functor.Bind BindTrans Data.Functor.Bind.Trans bisequence1 Data.Semigroup.Bitraversable bisequenceA1_ Data.Semigroup.Bifoldable Bitraversable1 Data.Semigroup.Bitraversable bitraverse1 Data.Semigroup.Bitraversable bitraverse1_ Data.Semigroup.Bifoldable Dual 1 (Type/Class) Data.Semigroupoid.Dual 2 (Data Constructor) Data.Semigroupoid.Dual first Data.Bifunctor.Apply fmap Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus fold1 Data.Semigroup.Foldable Foldable1 Data.Semigroup.Foldable foldMap1 Data.Semigroup.Foldable foldMap1Default Data.Semigroup.Traversable foldMapDefault1 Data.Semigroup.Foldable for1_ Data.Semigroup.Foldable Functor Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus getDual Data.Semigroupoid.Dual getSemi Data.Semigroupoid join Data.Functor.Bind liftB Data.Functor.Bind.Trans liftF2 Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus liftF3 Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus many Data.Functor.Alt , Data.Functor.Plus MaybeApply 1 (Type/Class) Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus 2 (Data Constructor) Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus o Data.Semigroupoid Plus Data.Functor.Plus returning Data.Functor.Bind runMaybeApply Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus runStatic Data.Semigroupoid.Static second Data.Bifunctor.Apply Semi 1 (Type/Class) Data.Semigroupoid 2 (Data Constructor) Data.Semigroupoid Semigroupoid Data.Semigroupoid sequence1 Data.Semigroup.Traversable sequenceA1_ Data.Semigroup.Foldable some Data.Functor.Alt , Data.Functor.Plus Static 1 (Type/Class) Data.Semigroupoid.Static 2 (Data Constructor) Data.Semigroupoid.Static Traversable1 Data.Semigroup.Traversable traverse1 Data.Semigroup.Traversable traverse1_ Data.Semigroup.Foldable unwrapApplicative Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus unwrapCategory Data.Semigroupoid WrapApplicative Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus WrapCategory Data.Semigroupoid WrappedApplicative Data.Functor.Bind , Data.Functor.Apply , Data.Functor.Alt, Data.Functor.Plus WrappedCategory Data.Semigroupoid zero Data.Functor.Plus Produced by Haddock version 2.9.2 | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/sequel_postgresql_triggers/actions/workflows/ci.yml | CI · Workflow runs · jeremyevans/sequel_postgresql_triggers · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / sequel_postgresql_triggers Public Notifications You must be signed in to change notification settings Fork 16 Star 97 Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights Actions: jeremyevans/sequel_postgresql_triggers Actions --> All workflows Workflows CI CI Show more workflows... Management Caches CI CI Actions Loading... Loading Sorry, something went wrong. Uh oh! There was an error while loading. Please reload this page . --> will be ignored since log searching is not yet available Show workflow options Create status badge Create status badge Loading Uh oh! There was an error while loading. Please reload this page . ci.yml --> will be ignored since log searching is not yet available 8 workflow runs 8 workflow runs Event Filter by Event Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching events. Status Filter by Status Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching statuses. Branch Filter by Branch Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching branches. Actor Filter by Actor Sorry, something went wrong. Filter Loading Sorry, something went wrong. No matching users. Add Ruby 4.0 to CI CI #31: Commit b5ff755 pushed by jeremyevans 28m 14s master master 28m 14s View workflow file Use SimpleCov.add_filter block instead of string CI #30: Commit 62299a4 pushed by jeremyevans 3m 39s master master 3m 39s View workflow file Add JRuby 10.0 to CI CI #29: Commit 3d4496c pushed by jeremyevans 11m 37s master master 11m 37s View workflow file Switch rdoc task to normal rake task, avoid rdoc/task require CI #28: Commit 50cb1b6 pushed by jeremyevans 1m 19s master master 1m 19s View workflow file Adds pgt_outbox_setup and pgt_outbox_events for Transactional Outbox Pattern CI #22: Pull request #19 synchronize by bougyman 1m 22s master master 1m 22s View #19 View workflow file Work with ubuntu-latest using 24.04 by default in CI CI #20: Commit 327cd90 pushed by jeremyevans 1m 55s master master 1m 55s View workflow file Add Ruby 3.4 to CI CI #19: Commit cd003bb pushed by jeremyevans 3m 23s master master 3m 23s View workflow file Use -W:strict_unused_block when running tests on Ruby 3.4+ CI #18: Commit 500ae6f pushed by jeremyevans 1m 25s master master 1m 25s View workflow file You can’t perform that action at this time. | 2026-01-13T09:30:25 |
https://upsilon.cc/~zack/tags/ | tags zack's home page / tags home research publications committees teaching hacking debian software talks blog about academia adsense agendadigitale agendadigitalebo archlinux artwork autoconf autotools awesome batteries bits bof bologna book bsp cad68 caterpillar cbproject cdbs centos cfp charity charliehebdo chromium cinema cla community conservancy contributors copyright core crossdistro ctte debcheckout debconf debconf10 debconf11 debconf12 debconf14 debhelper debian debsources dep dep8 derivatives devscripts donation dpl economics edf emacs endorsement eu facebook firmware floss fosdem fp fp7 france freedombox fsf fun gentoo ghm git gnome gnomeawesomeapplet gnu google gourmet gpg gpl grml gsoc gtd hack hardware harmony haskell howcanihelp howto ignaziomarino ikiwiki ilfatto ilrestodelcarlino interview irill iss italy java jesuischarlie kernel larepubblica lavoce lazyweb lca2011 lifehack linux logics lwn mancoosi meme motorbike mutt newspaper nmprocess nosoignons notmuch nyt ocaml opensuse opw orgmode paper paris pd perl phd podcast politics pts python qa radio radio2 rai rant rcbc rcbw rece redhat reproducible-builds research rfc rip roma ruby security shapado shuttleworth signature softwareheritage sponsor sprint squeeze support survey systemd tddd teaching tex thesis turbogears tv twid ubuntu vacation vcs vim web20 xml xmonad xquery xslt zonbu Copyright © 2007-2022 by Stefano Zacchiroli <zack@upsilon.cc> Homepage by Stefano Zacchiroli is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License . Last edited Mon 10 May 2010 10:40:39 PM CEST Wed 26 Dec 2007 05:23:43 PM CET --> | 2026-01-13T09:30:25 |
https://rubygems.org/gems/roda | roda | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up roda 3.100.0 Routing tree web toolkit Gemfile: = install: = Versions: 3.100.0 January 12, 2026 (189 KB) 3.99.0 December 12, 2025 (188 KB) 3.98.0 November 13, 2025 (188 KB) 3.97.0 October 13, 2025 (188 KB) 3.96.0 September 12, 2025 (188 KB) Show all versions (139 total) Runtime Dependencies (1): rack >= 0 Development Dependencies (9): erubi >= 0 json >= 0 mail >= 0 minitest >= 5.7.0 minitest-global_expectations >= 0 minitest-hooks >= 0 rack_csrf >= 0 rake >= 0 tilt >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 17,591,264 For this version 3,094 Version Released: January 12, 2026 6:00pm License: MIT Required Ruby Version: >= 1.9.2 Links: Homepage Changelog Source Code Documentation Mailing List Bug Tracker Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/asciidoctor-interface/ | The Asciidoctor Interface | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Usage Convert Documents The Asciidoctor Interface 3.0 3.0 2.5 Edit this Page The Asciidoctor Interface The main entry point for AsciidoctorJ is the Asciidoctor Java interface. You obtain an instance from the factory class Asciidoctor.Factory that provides a simple create method. If you need to get an instance of Asciidoctor using a certain gem path the factory org.asciidoctor.jruby.AsciidoctorJRuby.Factory provides multiple create methods to get an instance with a certain gem or load path: Methods to create an Asciidoctor instance Method Name Description org.asciidoctor.Asciidoctor.Factory .create() The default create method that is used most often. Only use other methods if you want to load extensions that are not on the classpath. org.asciidoctor.jruby.AsciidoctorJRuby.Factory .create(String gemPath) Creates a new Asciidoctor instance and sets the global variable GEM_PATH to the given String. The variable GEM_PATH defines where Ruby looks for installed gems. org.asciidoctor.jruby.AsciidoctorJRuby.Factory .create(List<String> loadPaths) Creates a new Asciidoctor instance and set the global variable LOAD_PATH to the given Strings. The variable LOAD_PATH defines where Ruby looks for files. So most of the time you simply get an Asciidoctor instance like this: Default way to create an Asciidoctor instance Asciidoctor asciidoctor = Asciidoctor.Factory.create(); As Asciidoctor instances can be created they can also be explicitly destroyed to free resources used in particular by the Ruby runtime associated with it. Therefore the Asciidoctor interface offers the method shutdown. After calling this method every other method call on the instance will fail! Destroying an Asciidoctor instance Asciidoctor asciidoctor = Asciidoctor.Factory.create(); asciidoctor.shutdown(); The Asciidoctor interface also implements the interface java.io.AutoCloseable which also shuts down the Ruby runtime. Therefore the previous example is equivalent to this: Automatically destroying an Asciidoctor instance try (Asciidoctor asciidoctor = Asciidoctor.Factory.create()) { Options emptyOptions = Options.builder().build(); asciidoctor.convert("Hello World", emptyOptions); } To convert AsciiDoc documents the Asciidoctor interface provides four methods: convert convertFile convertFiles convertDirectory Prior to Asciidoctor 1.5.0, the term render was used in these method names instead of convert (i.e., render , renderFile , renderFiles and renderDirectory ). AsciidoctorJ continues to support the old method names for backwards compatibility. Convert methods on the Asciidoctor interface Method Name Return Type Description convert String Parses AsciiDoc content read from a string or stream and converts it to the format specified by the backend option. convertFile String Parses AsciiDoc content read from a file and converts it to the format specified by the backend option. convertFiles String[] Parses a collection of AsciiDoc files and converts them to the format specified by the backend option. convertDirectory String[] Parses all AsciiDoc files found in the specified directory (using the provided strategy) and converts them to the format specified by the backend option. Here’s an example of using AsciidoctorJ to convert an AsciiDoc string. Converting an AsciiDoc string Options emptyOptions = Options.builder().build(); String html = asciidoctor.convert( "Writing AsciiDoc is _easy_!", emptyOptions); System.out.println(html); The convertFile method will convert the contents of an AsciiDoc file. Converting an AsciiDoc file String html = asciidoctor.convertFile( new File("sample.adoc"), Options.builder().build()); System.out.println(html); The convertFiles method will convert a collection of AsciiDoc files: Converting a collection of AsciiDoc files String[] result = asciidoctor.convertFiles( Arrays.asList(new File("sample.adoc")), Options.builder().build()); for (String html : result) { System.out.println(html); } The convertFile or convertFiles methods will only return a converted String object or array if you disable writing to a file, which is enabled by default. To disable writing to a file, create a new Options object, disable the option to create a new file with option.setToFile(false) , and then pass the object as a parameter to convertFile or convertFiles . To learn more check Conversion Options for a description of available customizations. When converting directly to files, the convertFiles method will return a String Array (i.e., String[] ) with the names of all the converted documents. Another method provided by the Asciidoctor interface is convertDirectory . This method converts all of the files with AsciiDoc extensions ( .adoc (preferred) , .ad , .asciidoc , .asc ) that are present within a specified folder and following given strategy. If the converted content is not written into files, convertDirectory will return an array listing all the documents converted. Converting all AsciiDoc files in a directory Options emptyOptions = Options.builder().build(); String[] result = asciidoctor.convertDirectory( new AsciiDocDirectoryWalker("src/asciidoc"), emptyOptions); for (String html : result) { System.out.println(html); } In conjunction with convertDirectory the DirectoryWalker interface. This provides a strategy for locating files to process that can be passed as the first parameter of the convertDirectory method. Currently, Asciidoctor provides two built-in implementations of the DirectoryWalker interface: Built-in DirectoryWalker implementations Class Type Description AsciiDocDirectoryWalker Concrete class Locates all files of given folder and all its subfolders. Ignores files starting with underscore (_). GlobDirectoryWalker Concrete class Locates all files of given folder following a glob expression. To learn more, see Locate Files . Convert Documents Conversion Options Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://docs.asciidoctor.org/asciidoctorj/latest/syntax-highlighting/lifecycle/ | Lifecycle of a SyntaxHighlighterAdapter | Asciidoctor Docs Asciidoctor Docs In this project AsciiDoc Language Syntax Quick Reference Processing Asciidoctor Ruby Asciidoctor.js JavaScript AsciidoctorJ Java Extensions Add-on Converters PDF Ruby EPUB3 Ruby reveal.js Ruby, JavaScript Source Compilers Reducer Ruby, JavaScript Extended Syntax Asciidoctor Diagram Ruby Tooling Build Automation Maven Tools Java Gradle Plugin Java Asciidoclet Java Text Editors / Viewers Browser Extension IntelliJ Plugin Chat List --> Source Tweets AsciidoctorJ Distribution Installation Usage Command Line Interface Convert Documents The Asciidoctor Interface Conversion Options Locate Files Safe Modes Examples Converting to EPUB3 Ruby Runtime Register a Ruby Extension Logs Handling API Read the Document Tree Write a Custom Converter Extensions API AsciidoctorJ Conversion Process Overview Understanding the AST Classes Write an Extension Block Macro Processor Inline Macro Processor Block Processor Include Processor Preprocessor Postprocessor Treeprocessor Docinfo Processor Register Extensions Manually Registering Extensions with javaExtensionRegistry Bulk Extension Registration ( Extension Groups ) Automatically Loading Extensions Logging Syntax Highlighter API Implement a Syntax Highlighter Adapter Lifecycle of a SyntaxHighlighterAdapter Format the Source Block Element Link and Copy External Resources Static Syntax Highlighting During Conversion Invocation Order Automatically Load a Syntax Highlighter Help & Guides Updating to New Releases v3.0.x migration guide Extension Migration: 1.6.x to 2.0.x Extension Migration: 1.5.x to 1.6.x Running in Frameworks Using AsciidoctorJ in an OSGi environment Running AsciidoctorJ on WildFly Running AsciidoctorJ with Spring Boot Accessing the JRuby Instance Loading Ruby Libraries Loading External Gems with GEM_PATH Optimization Using a pre-release version Using a Snapshot Version Development Project Layout Local Development Develop in an IDE Continuous Integration AsciidoctorJ 3.0 AsciiDoc Asciidoctor 2.0 Asciidoctor.js 3.0 2.2 AsciidoctorJ 3.0 2.5 Asciidoctor PDF 2.3 2.2 2.1 2.0 Asciidoctor EPUB3 2.3 Asciidoctor reveal.js 5.0 4.1 Maven Tools 3.2 Gradle Plugin Suite 5.0 4.0 Asciidoclet 2.0 1.5.6 Asciidoctor Diagram 3.0.1 Browser Extension Community AsciidoctorJ Syntax Highlighter API Lifecycle of a SyntaxHighlighterAdapter 3.0 3.0 2.5 Edit this Page Lifecycle of a SyntaxHighlighterAdapter AsciidoctorJ will create an own instance for every document that it converts. It will try to instantiate the class by calling a constructor that has three parameters: name The name of the syntax highlighter as it was referenced by the :source-highlighter attribute. In the previous example this was "myhighlightjs" . backend The name of the backend used to convert the document. This is for example "html5" . Note that SyntaxHighlighters can only be used for HTML based backends. options A map containing options for this syntax highlighter. Currently this contains the current org.asciidoctor.ast.Document for the key "document" . This means the syntax highlighter class could also have this constructor: public HighlightJsHighlighter(String name, String backend, Map<String, Object> options) { assertThat("myhighlightjs").isEqualTo(name); assertThat("html5").isEqualTo(backend); Document document = (Document) options.get("document"); assertThat("Syntax Highlighter Test").isEqualTo(document.getDoctitle()); } A constructor with only the first two, or only the first parameter is also allowed. AsciidoctorJ will call the constructor with the most matching parameters. Implement a Syntax Highlighter Adapter Format the Source Block Element Asciidoctor Home --> Docs Chat Source List (archive) @asciidoctor Copyright © 2026 Dan Allen, Sarah White, and individual Asciidoctor contributors. Except where noted, the content is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. The UI for this site is derived from the Antora default UI and is licensed under the MPL-2.0 license. Several icons are imported from Octicons and are licensed under the MIT license. AsciiDoc® and AsciiDoc Language™ are trademarks of the Eclipse Foundation, Inc. Thanks to our backers and contributors for helping to make this project possible. Additional thanks to: Authored in AsciiDoc . Produced by Antora and Asciidoctor . | 2026-01-13T09:30:25 |
https://rubygems.org/gems/sequel_postgresql_triggers | sequel_postgresql_triggers | RubyGems.org | your community gem host ⬢ RubyGems nav#focus mousedown->nav#mouseDown click@window->nav#hide"> Navigation menu autocomplete#choose mouseover->autocomplete#highlight"> Search Gems… Releases Blog Gems Guides Sign in Sign up sequel_postgresql_triggers 1.6.0 Database enforced timestamps, immutable columns, counter/sum caches, and touch propogation Gemfile: = install: = Versions: 1.6.0 January 18, 2024 (14.5 KB) 1.5.0 November 16, 2018 (14 KB) 1.4.0 January 05, 2018 (12.5 KB) 1.3.0 May 08, 2017 (11.5 KB) 1.2.0 September 28, 2016 (11 KB) Show all versions (13 total) Runtime Dependencies (1): sequel >= 0 Development Dependencies (2): minitest >= 5 minitest-global_expectations >= 0 Show all transitive dependencies Owners: Pushed by: Authors: Jeremy Evans SHA 256 checksum: = ← Previous version Total downloads 384,387 For this version 18,234 Version Released: January 18, 2024 7:43pm License: MIT Required Ruby Version: >= 1.9.2 Links: Homepage Documentation Download Review changes Badge Subscribe RSS Report abuse Reverse dependencies Status Uptime Code Data Stats Contribute About Help API Policies Support Us Security RubyGems.org is the Ruby community’s gem hosting service. Instantly publish your gems and then install them . Use the API to find out more about available gems . Become a contributor and improve the site yourself. The RubyGems.org website and service are maintained and operated by Ruby Central’s Open Source Program and the RubyGems team. It is funded by the greater Ruby community through support from sponsors, members, and infrastructure donations. If you build with Ruby and believe in our mission, you can join us in keeping RubyGems.org, RubyGems, and Bundler secure and sustainable for years to come by contributing here . Operated by Ruby Central Designed by DockYard Hosted by AWS Resolved with DNSimple Monitored by Datadog Gems served by Fastly Monitored by Honeybadger Secured by Mend.io English Nederlands 简体中文 正體中文 Português do Brasil Français Español Deutsch 日本語 | 2026-01-13T09:30:25 |
https://bundler.io/v4.0/man/bundle-cache.1.html | Bundler: bundle cache Bundler Docs Team Blog Repository bundle cache bundle-cache - Package your needed .gem files into your application bundle cache [ OPTIONS ] alias: package , pack Description Copy all of the .gem files needed to run the application into the vendor/cache directory. In the future, when running bundle install(1) , use the gems in the cache in preference to the ones on rubygems.org . Options --all-platforms Include gems for all platforms present in the lockfile, not only the current one. --cache-path=CACHE-PATH Specify a different cache path than the default (vendor/cache). --gemfile=GEMFILE Use the specified gemfile instead of Gemfile. --no-install Don't install the gems, only update the cache. --quiet Only output warnings and errors. Git And Path Gems The bundle cache command can also package :git and :path dependencies besides .gem files. This can be disabled setting cache_all to false. Support For Multiple Platforms When using gems that have different packages for different platforms, Bundler supports caching of gems for other platforms where the Gemfile has been resolved (i.e. present in the lockfile) in vendor/cache . This needs to be enabled via the --all-platforms option. This setting will be remembered in your local bundler configuration. Remote Fetching By default, if you run bundle install(1) after running bundle cache(1) , bundler will still connect to rubygems.org to check whether a platform-specific gem exists for any of the gems in vendor/cache . For instance, consider this Gemfile (5) : source "https://rubygems.org" gem "nokogiri" If you run bundle cache under C Ruby, bundler will retrieve the version of nokogiri for the "ruby" platform. If you deploy to JRuby and run bundle install , bundler is forced to check to see whether a "java" platformed nokogiri exists. Even though the nokogiri gem for the Ruby platform is technically acceptable on JRuby, it has a C extension that does not run on JRuby. As a result, bundler will, by default, still connect to rubygems.org to check whether it has a version of one of your gems more specific to your platform. This problem is also not limited to the "java" platform. A similar (common) problem can happen when developing on Windows and deploying to Linux, or even when developing on OSX and deploying to Linux. If you know for sure that the gems packaged in vendor/cache are appropriate for the platform you are on, you can run bundle install --local to skip checking for more appropriate gems, and use the ones in vendor/cache . One way to be sure that you have the right platformed versions of all your gems is to run bundle cache on an identical machine and check in the gems. For instance, you can run bundle cache on an identical staging box during your staging process, and check in the vendor/cache before deploying to production. By default, bundle cache(1) fetches and also installs the gems to the default location. To package the dependencies to vendor/cache without installing them to the local install location, you can run bundle cache --no-install . History In Bundler 2.1, cache took in the functionalities of package and now package and pack are aliases of cache . Choose version v4.0 v2.7 v2.6 v2.5 v2.4 v2.3 v2.2 v2.1 General Release notes Primary Commands bundle install bundle update bundle cache bundle exec bundle config bundle help Utilities bundle bundle add bundle binstubs bundle check bundle clean bundle console bundle doctor bundle env bundle fund bundle gem bundle info bundle init bundle issue bundle licenses bundle list bundle lock bundle open bundle outdated bundle platform bundle plugin bundle pristine bundle remove bundle show bundle version gemfile Edit this document on GitHub if you caught an error or noticed something was missing. Docs Team Blog About Repository | 2026-01-13T09:30:25 |
https://github.com/jeremyevans/autoforme | GitHub - jeremyevans/autoforme: Web Administrative Console for Roda/Sinatra/Rails and Sequel::Model Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} jeremyevans / autoforme Public Notifications You must be signed in to change notification settings Fork 14 Star 70 Web Administrative Console for Roda/Sinatra/Rails and Sequel::Model autoforme.jeremyevans.net License MIT license 70 stars 14 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights jeremyevans/autoforme master Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 507 Commits .github/ workflows .github/ workflows demo-site demo-site lib lib spec spec .ci.gemfile .ci.gemfile .gitignore .gitignore CHANGELOG CHANGELOG MIT-LICENSE MIT-LICENSE README.rdoc README.rdoc Rakefile Rakefile autoforme.gemspec autoforme.gemspec autoforme.js autoforme.js View all files Repository files navigation README MIT license AutoForme AutoForme is an administrative web front end to an ORM that uses Forme [1] for building the HTML forms. It is designed to integrate easily into web frameworks, and currently supports Roda, Sinatra, and Rails. The only currently supported ORM is Sequel::Model. github.com/jeremyevans/forme Installation gem install autoforme Links Demo Site autoforme-demo.jeremyevans.net RDoc autoforme.jeremyevans.net Source github.com/jeremyevans/autoforme Discussion Forum github.com/jeremyevans/autoforme/discussions Bug Tracker github.com/jeremyevans/autoforme/issues Features Create, update, edit, and view model objects Browse and search model objects Edit many-to-many relationships for model objects Easily access associated objects Support autocompletion for all objects Allow customization for all likely configuration points, using any parameters available in the request Basic Configuration AutoForme is configured using a fairly simple DSL. Here is an example for Sinatra: class App < Sinatra :: Base AutoForme . for ( :sinatra , self ) do order [ :name ] model Artist do columns [ :name ] end model Album do columns [ :artist , :name ] end end end Let’s break down how this works. You setup AutoForme using AutoForme.for , which takes 2 arguments, the controller type symbol (currently either :sinatra, :roda, or :rails), and the controller class (either a Sinatra::Base, Roda, or ActionController::Base subclass). You pass AutoForme.for a block, which is instance evaled at the framework level. This level sets the defaults. The order call in the framework block sets the default order for all models. The model calls in the framework block take a ORM model class. As only Sequel is currently supported, this should be a Sequel::Model subclass. The block passed to the model method is instance evaled at the model level, and sets the configuration for that model. In this example, the Artist model will only show the name column, and the Album model will only show the artist association and the name column. In your application, you can then to go ‘/Artist/browse’ or ‘/Album/browse’ to get to the web UI exposed to AutoForme. Design Principles Use Forme to generate the forms Do not modify/extend model or controller classes Assume that the web framework provides the layout Do not use templates, render form objects to strings Use a block-based DSL in the controller for configuration Allow customization on a per-request basis for everything Basic Implementation The web framework controllers call AutoForme.for to create AutoForme::Framework instances, which contain and set default values for AutoForme::Model instances. When a request comes in from the web framework, the AutoForme::Framework instance wraps request-level data in a AutoForme::Request. Then it creates an AutoForme::Action to handle this request. The AutoForme::Action either returns a string that the web framework then renders, or it redirects to another page. Advanced Configuration AutoForme doesn’t have all that many features compared to other admin frameworks, but the features it does have are extremely flexible. Most of the configuration you’ll do in AutoForme is at the model level (in the context of an AutoForme::Model instance), so we’ll start looking at the customization options there. The most common options are probably: columns This is an array of column/association name symbols to use for the model. column_options This is a hash of column options for the model, keyed by column symbol, with values that are hashes of column options. order This is an expression or an array of expressions by which to order returned rows. Note that for each of the customization options, you can do per-request customization by using a proc which is called with the type symbol and request (AutoForme::Request instance), which should return an appropriate object. columns Proc called with type symbol and request, should return array of column/association symbols column_options Proc called with column/association symbol, type symbol and request, should return hash of column options. order Proc called with type symbol and request, should return expression or array of expressions by which to order returned rows. Below is brief description of other available options. Note that just like the above options you can use Procs with most of these options to do customization on a per-request basis. association_links Array of association symbols for associations to display on the show/edit pages, can also be set to :all for all associations or :all_except_mtm for all associations except many to many associations. autocomplete_options Enable autocompletion for this model, with the given options. The following keys are respected: :callback Proc called with dataset and options hash containing :type, :request, and :query :display A SQL expression to search on and display in the result :limit The number of results to return :filter Similar to callback, but overriding the default filter (a case insensitive substring search on display) column_search_filter This should be a Proc that accepts a dataset, column, value, and request, and returns a filtered dataset. This allows for customizing the search filtering, so you can use non-columns/non-associations on the search form. eager Array of associations to eagerly load in separate queries eager_graph Array of associations to eager load in the same query (necessary if order or filter refers to them) filter A Proc called with a dataset, type symbol, and request that can be used to filter the available rows. Can be used to implement access control. redirect A Proc called with an object, type symbol, and request that can be used to override the default redirecting after form submittal. inline_mtm_associations Array of many to many association symbols to allow editing on the edit page lazy_load_association_links Whether to show the association links directly on the show/edit pages, or to load them via ajax on request mtm_associations Array of many to many association symbols to support editing on a separate page pagination_strategy Set to :filter to paginate using a filter instead of using offsets. This requires the column have an unambiguous order. per_page Number of records to show per page on the browse and search pages session_value Sets up a filter and before_create hook that makes it so access is limited to objects where the object’s column value is the same as the session value with the same name. supported_actions Array of action symbols to support for the model, should be a subset of :browse, :new, :show, :edit, :delete, :search, :mtm_edit These options are related to displayed output: form_attributes Hash of attributes to use for any form tags form_options Hash of Forme::Form options to pass for any forms created class_display_name The string to use on pages when referring to the model class. This defaults to the full class name. display_name The string to use when referring to a model instance. Can either be a symbol representing an instance method call, or a Proc called with the model object, the model object and type symbol, or the model object, type symbol, and request, depending on the arity of the Proc. link_name The string to use in links for the class. This defaults to class_display_name . edit_html The html to use for a particular object edit field. Should be a proc that takes the model object, column symbol, type symbol, and request and returns the html to use. page_footer Override the default footer used for pages page_header Override the default header used for pages show_html The html to use for displaying the value for an object field. Should be a proc that takes the model object, column symbol, type symbol, and request and returns the html to use. table_class The html class string to use for the browse and search tables view_options Hash with options passed when rendering the view (how these options are used varies in each of the supported web frameworks), e.g. view_options: {:layout => :formelayout} These hook options should be callable objects that are called with the model object and the request. after_create Called after creating the object after_destroy Called after destroying the object after_update Called after updating the object before_create Called before creating the object before_destroy Called before destroy the object before_edit Called before displaying object on edit page before_new Called before displaying object on new page before_update Called before updating the object There’s also an addition before_action hook that is called with the type symbol of the request, and the request before every page. In addition to being specified at the model level, almost all of these options can be specified at the framework level, where they operate as default values for models that don’t specify the options. Just like the model level, the framework level also allows customization on a per request basis, though framework-level Procs generally take the model class as an initial argument (in addition to the type symbol and request). Additionally, AutoForme.for accepts a :prefix option that controls where the forms are mounted: AutoForme . for ( :sinatra , self , :prefix => '/path/to' ) do model Artist end Means you can go to /path/to/Artist/browse to browse the artists. Javascript By default, AutoForme requires no javascript. The only optional part of AutoForme that requires javascript is the autocompleting. AutoForme also has javascript support for the progressive enhancement of the following: Loading association links via ajax if lazy_load_association_links is true. Adding and removing many-to-many associated objects via ajax for inline_mtm_associations AutoForme’s javascript support is contained in the autoforme.js file in the root of the repository. AutoForme’s autocompleting support also requires github.com/Pixabay/JavaScript-autoComplete Make sure to load the autoforme.js file after the DOM content has been loaded, such as at the end of the body. Reloading Code By default, AutoForme stores classes by reference. This can cause issues when using code reloading in development environments. You can call register_by_name to set Autoforme to store classes by name, so that if a class is removed and reloaded (giving a new class reference), it will use the new class instead of the reference to the old class. Example: class App < Sinatra :: Base AutoForme . for ( :sinatra , self ) do register_by_name model Artist end end Rails Because Rails separates routing from request handling, it can be little awkward to use AutoForme in Rails development mode. The best way to handle it is to call AutoForme.for in the related controller file, and have an initializer reference the controller class, causing the controller file to be loaded. Roda Because Roda uses a routing tree, unlike Rails and Sinatra, with Roda you need to dispatch to the autoforme routes at the point in the routing tree where you want to mount them. Additionally, the Roda support offers a Roda plugin for easier configuration. To mount the autoforme routes in the root of the application, you could do: class App < Roda plugin :autoforme do model Artist end route do # rest of routing tree autoforme end end To mount the routes in a subpath: class App < Roda plugin :autoforme do model Artist end route do r . on "admin" do autoforme end # rest of routing tree end end To handle multiple autoforme configurations, mounted at different subpaths: class App < Roda plugin :autoforme autoforme ( name: 'artists' ) do model Artist end autoforme ( name: 'albums' ) do model Album end route do r . on "artists" do autoforme ( 'artists' ) end r . on "albums" do autoforme ( 'albums' ) end # rest of routing tree end end TODO capybara-webkit tests for ajax behavior read_only fields for edit page one_to_many/many_to_many associations in columns configurable searching nested form objects License MIT Author Jeremy Evans <code@jeremyevans.net> About Web Administrative Console for Roda/Sinatra/Rails and Sequel::Model autoforme.jeremyevans.net Resources Readme License MIT license Uh oh! There was an error while loading. Please reload this page . Activity Stars 70 stars Watchers 5 watching Forks 14 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 7 Uh oh! There was an error while loading. Please reload this page . Languages Ruby 95.0% HTML 2.2% JavaScript 1.9% CSS 0.9% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T09:30:25 |
http://www.reddit.com/r/types | Reddit - The heart of the internet Skip to main content Open menu Open navigation Go to Reddit Home r/types Get App Get the Reddit app Log In Log in to Reddit Expand user menu Open settings menu :first-child]:h-full [&>:first-child]:w-full [&>:first-child]:mb-0 [&>:first-child]:rounded-[inherit] h-full w-full [&>:first-child]:overflow-hidden [&>:first-child]:max-h-full"> :first-child]:h-full [&>:first-child]:w-full [&>:first-child]:mb-0 [&>:first-child]:rounded-[inherit] h-full w-full [&>:first-child]:overflow-hidden [&>:first-child]:max-h-full"> r/types members online Create Post Feed About Best Open sort options Best Hot New Top Rising Change post view Card Compact Community highlights Blog post: Universal domain types :first-child]:h-full [&>:first-child]:w-full [&>:first-child]:mb-0 [&>:first-child]:rounded-[inherit] h-full w-full [&>:first-child]:overflow-hidden [&>:first-child]:max-h-full"> u/roman-kashitsyn • Blog post: Universal domain types I love types! As with most things in life, we can get 80% of type safety benefits with only 20% of extra effort. I wrote a blog post about simple classes of domain types that appear in almost any program but which most programming languages fail to make convenient to define: Universal domain types . I’d love to hear your feedback. And if you know more examples of such type classes, please let me know! The unimath Minotaur : ode to Vladimir Voevodsky u/introsp3ctor • The unimath Minotaur : ode to Vladimir Voevodsky The unimath Minotaur : ode to Vladimir Voevodsky r/aiArt • The unimath Minotaur : ode to Vladimir Voevodsky upvotes · comments My 2008 type s 6MT w/ aspec kit u/Commercial-Pipe-1802 • My 2008 type s 6MT w/ aspec kit Created Mar 17, 2008 Restricted Anyone can view, but only approved users can contribute 37 0 Moderators Moderator list hidden. Learn More View all moderators Reddit Rules Privacy Policy User Agreement Accessibility Reddit, Inc. © 2026. All rights reserved. Expand Navigation Collapse Navigation | 2026-01-13T09:30:25 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.