Helper to require() directories.
TypeScript definitions for require-dir
require dir
require dir
require-dir for all file types
Yet another Node.js helper to require all files in directory
node require dir
require folders that may have modules inside
node require dir
Use the :dir pseudo-class in CSS
Generate a unique filename for use in temporary directories or caches.
Node.js path.parse() ponyfill
Call require pretending your are at another directory
Walk up ancester's dir up to root
find the closest package.json
Convert directories to glob compatible strings
Node helper module to `require()` complete directories.
Node JS directory compare
A node module to get your node module started
Resolve a URI relative to an optional base URI
Resolve a directory that is either local, global or in the user's home directory.
Recursively mkdir, like `mkdir -p`
Finds the first parent directory that contains a given file or directory.
Find a file by walking up the directory tree
Easily and non-intrusively require files from sub-folders. Without polluting global namespace, or having modules clobber each other, include RequireDir and initialize it to get access to #dir and #dir_r
A gem to require all files in a directory
Basic utility to require a directory.
By adding a .base file to your application base dir, helps you augment $LOAD_PATH, auto-require files, and set constants to important paths.
By adding a .base file to your application base dir, helps you augment $LOAD_PATH, auto-require files, and set constants to important paths.
Create dump file in temporary folder of root directory, if folder not present in dir then it will create one. Usage: open interactive prompt by typing 'irb' and require 'generate_dump_file'. again, require File.expand_path('../config/environment', __FILE__) and then run GenerateDumpFile.create
Gem to interact with the Rls.io/u url shortner and /p/ paste filecontent gem. Usage: require 'rlsgem' Rlsgem.cut('http://www.too.long.url/and/sub/dirs') or Rlsgem.paste_file('Paste title','/path/of/file/to/paste')
Required is a utility to require all files in a directory. Why would one want to require a whole bunch of files at once? I have used this gem on 2 projects to: - require dozens of jar files when working on a JRuby project - pull in all files before running code coverage (rcov), to find code that is otherwise dead/untouched Options for required include the ability to recursively descend through subdirectories, include/exclude files based on pattern matching, and to specify the order of requires based on filename. An array of all the files that were loaded is returned. Quick example: require 'required' required "some/path/to/dir" See the README for more examples, and description of options.
OCRAN (One-Click Ruby Application Next) packages Ruby applications for distribution. It bundles your script, the Ruby interpreter, gems, and native libraries into a self-contained artifact that runs without requiring Ruby to be installed on the target machine. Three output formats are supported on all platforms: - Self-extracting executable (.exe on Windows, native binary on Linux/macOS) - Directory with a launch script (--output-dir) - Zip archive with a launch script (--output-zip) This is a fork of OCRA maintained for Ruby 3.2+ compatibility. Migration guide: replace OCRA_EXECUTABLE with OCRAN_EXECUTABLE in your code. Usage: ocran helloworld.rb # builds helloworld.exe / helloworld ocran --output-dir out/ app.rb ocran --output-zip app.zip app.rb See readme at https://github.com/largo/ocran Report problems at https://github.com/largo/ocran/issues
= Mcrypt - libmcrypt bindings for Ruby Mcrypt provides Ruby-language bindings for libmcrypt(3), a symmetric cryptography library. {Libmcrypt}[http://mcrypt.sourceforge.net/] supports lots of different ciphers and encryption modes. == You will need * A working Ruby installation (>= 1.8.6 or 1.9) * A working libmcrypt installation (2.5.x or 2.6.x, tested with 2.5.8) * A sane build environment == Installation Install the gem: gem install ruby-mcrypt --test -- --with-mcrypt-dir=/path/to/mcrypt/prefix If you're installing on Ubuntu: sudo apt-get install mcrypt libmcrypt-dev gem install ruby-mcrypt If you want to run the longer test suite, do this instead: MCRYPT_TEST_BRUTE=1 \ gem install ruby-mcrypt --test -- --with-mcrypt-dir=/path/to/mcrypt/prefix Put this in your code: require 'rubygems' require 'mcrypt' Or in Rails' environment.rb: gem "ruby-mcrypt", :lib => "mcrypt" == Usage crypto = Mcrypt.new(:twofish, :cbc, MY_KEY, MY_IV, :pkcs) # encryption and decryption in one step ciphertext = crypto.encrypt(plaintext) plaintext = crypto.decrypt(ciphertext) # encrypt in smaller steps while chunk = $stdin.read(4096) $stdout << crypto.encrypt_more(chunk) end $stdout << crypto.encrypt_finish # or decrypt: while chunk = $stdin.read(4096) $stdout << crypto.decrypt_more(chunk) end $stdout << crypto.decrypt_finish == Known Issues * Test coverage is lacking. If you find any bugs, please let the author know. == Wish List * IO-like behavior, e.g. crypto.open($stdin) { |stream| ... } == Author * Philip Garrett <philgarr at gmail.com> == Copyright and License Copyright (c) 2009-2013 Philip Garrett. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
pikuri-assistant ships the demo +bin/pikuri-assistant+ binary on top of pikuri-core + pikuri-skills + pikuri-mcp: an interactive chat agent the user hand-edits to declare a +Pikuri::Mcp::Registry+ of MCP servers. The +Pikuri.prompt+ search path picks up this gem's +prompts/pikuri-assistant.txt+ automatically on require — same multi-gem prompt-dir pattern as pikuri-code.
# Otto AsciiDoc-powered static site generator with Jekyll-style conventions: layouts, includes, data files, posts, drafts, permalinks, and custom collections. ## Install ```sh gem install ottogen ``` Requires Ruby 3.0 or newer. ## Quickstart ```sh mkdir mysite && cd mysite otto init otto build otto serve open http://127.0.0.1:8778/ ``` For a longer walkthrough including AsciiDoc syntax, see [GUIDE.md](GUIDE.md). ## Commands | Command | Description | |---|---| | `otto init [DIR]` | Scaffold a new site (current dir if omitted) | | `otto build` | Render the site to `_build/` | | `otto build --drafts` | Include posts from `_drafts/` | | `otto watch` | Rebuild on file change | | `otto serve` | Serve `_build/` on port 8778 | | `otto generate PAGE` | Create a new page in `pages/` | | `otto post "Title"` | Create a new dated post in `_posts/` | | `otto clean` | Delete `_build/` | | `otto doctor` | Sanity-check project layout | ## Project layout ``` my-site/ ├── .otto # marker ├── config.yml # site config ├── assets/ # copied verbatim into _build/ ├── pages/ # AsciiDoc pages, output mirrors path ├── _layouts/ # ERB layouts (.html.erb) ├── _includes/ # ERB partials ├── _data/ # YAML/JSON files exposed as site.data.* ├── _posts/ # YYYY-MM-DD-slug.adoc └── _drafts/ # undated drafts (excluded by default) ``` ## Configuration (`config.yml`) ```yaml title: My Otto Site description: Things I write url: https://example.com baseurl: "" permalink: /:year/:month/:day/:slug/ collections: recipes: output: true ``` `permalink` accepts these tokens: `:year`, `:month`, `:day`, `:slug`, `:title`. Templates ending in `/` produce pretty URLs (`<path>/index.html`). ## Pages and posts Both support YAML front matter: ```adoc --- layout: default title: Hello tags: [ruby, cli] --- = Hello Welcome to {site_title}. This page is at {page_url}. ``` Pages live under `pages/`; posts under `_posts/` with `YYYY-MM-DD-slug.adoc` names. Layouts wrap rendered AsciiDoc; partials in `_includes/` are pulled in via `<%= partial 'header.html' %>`. ## License MIT
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.