A tool to clean up old Docker tags from DigitalOcean container registry
Check if the process is running inside a Docker container
docker package
No description provided.
Work with IANA language tags.
NodeJS lib, with which you can easily find the latest version of Docker Hub images
Manage docker-compose from Node.js
List of standard HTML tags
Docker Remote API module.
a few common utility template tags for ES2015
DVR Tuner Server for Japanese TV.
Full BCP 47 language subtag data from the official IANA repository, in JSON format with multiple indices.
Check if the process is running inside a container (Docker/Podman)
TypeScript definitions for docker-modem
Get all git semver tags of your repository in reverse chronological order.
List of standard SVG tags.
Docker remote API network layer module.
A simple service worker used for the static template in sandpack, allowing users to develop websites like they would locally in the browser.
A Pulumi package for interacting with Docker in Pulumi programs
[](https://slack.pulumi.com) [](https://www.npmjs.com/package/@pulumi/docker-build) [ and [Puppeteer](https://github.com/GoogleChrome/puppeteer).
[@Redocly](https://redocly.com) CLI is your all-in-one API documentation utility. It builds, manages, improves, and quality-checks your API descriptions, all of which comes in handy for various phases of the API Lifecycle. Create your own rulesets to make
Track and report tags of followed Docker images.
Tag the Git repo for Docker Hub to build the image for Elastic Beanstalk
Dependabot-Docker provides support for bumping Docker image tags via Dependabot. If you want support for multiple package managers, you probably want the meta-gem dependabot-omnibus.
Dependabot-Docker-Compose provides support for bumping Docker Compose image tags via Dependabot. If you want support for multiple package managers, you probably want the meta-gem dependabot-omnibus.
Fluentd output plugin to resolve container name from docker container-id in record tags.
Baha is a command-line utility that assists in the creation of docker images. It addresses some of Dockerfiles shortcomings and encourages smaller, reusable, tagged images.
Extend docker-compose by adding support to: - include files - run services (and their dependencies) by tag - automatically detect service directories by git repository
A Ruby library for interacting with OCI/Docker registries using the native HTTP/tar/sha format to navigate repositories and retrieve tags, metadata and other useful information.
This project was mainly created to automate the build, tag, and push process of docker via rake tasks and reuse these across multiple projects. It also provides tasks for generating Kubernetes replication controllers, creating them in Kubernetes, and running rolling-update on Kubernetes. I recognize the code is not high quality and I expect there are many bugs. Hell, there are no unit tests! Use with extreme caution! This gem is currently in active development with a high risk of breaking changes every release (hence a <1 version).
# Squash Migrations Periodically squash migrations to reduce overhead of the `db:migrate` Rake task. ## Creating a release 1. Create a new pull request that: - Bumps the version in `rails-squash-migrations.gemspec` - Updates `CHANGELOG.md` to include all noteworthy changes, the release version, and the release date. 2. After the pull request lands, checkout the most up to date `main` branch and build the gem: ```console $ docker run --rm -it -v $(pwd):$(pwd) -w $(pwd) ruby gem build ``` 3. Publish the gem: ```console $ docker run --rm -it -v $(pwd):$(pwd) -w $(pwd) ruby gem push rails-squash-migrations-X.Y.Z.gem ``` 4. Create and publish a git tag: ```console $ git tag X.Y.Z $ git push https://github.com/Pioneer-Valley-Books/rails-squash-migrations.git X.Y.Z ```
# ruby unshare (runshare) This tool allows to unshare Linux namespaces. The implementation is similar to the unshare(1) tool. ## Installation Add this line to your application's Gemfile: ```ruby gem 'runshare' ``` And then execute: $ bundle Or install it yourself as: $ gem install runshare ## Usage > require "runshare" > RUnshare::unshare For example: cat > test.rb require "runshare" pid = RUnshare::unshare( :clone_newpid => true, :clone_newns => true, :clone_newcgroup => true, :clone_newipc => true, :clone_newuts => true, :clone_newnet => true, :clone_newtime => true, :fork => true, :mount_proc => "/proc", # docker export $(docker create hello-world) | tar -xf - -C rootfs :root => "/tmp/rootfs" ) if pid == 0 # child puts "--- #{Process.pid}" if system("/hello") != true raise "bad" end puts "--- done" else # parent puts "-- unshare=#{pid}, pid=#{Process.pid}" puts "-- exit=#{Process.waitpid(pid)}" end ^D sudo ruby -I ./lib ./test.rb ## Quick start $ rake compile && echo 'require "runshare"; RUnshare::unshare(:clone_newuts => true)' | irb install -c tmp/x86_64-linux/runshare/2.4.10/runshare.so lib/runshare/runshare.so cp tmp/x86_64-linux/runshare/2.4.10/runshare.so tmp/x86_64-linux/stage/lib/runshare/runshare.so Switch to inspect mode. require "runshare"; RUnshare::unshare ## Ruby <2.5 If your app is single threaded and you are observing: eval:1: warning: pthread_create failed for timer: Invalid argument, scheduling broken Just ignore it with some degree of bravity. You also can silence it by setting: $VERBOSE = nil ## Development After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment. To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.com/sitano/runshare. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. ## License The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
pikuri-memory gives a pikuri-core agent durable, long-lived memory: facts about the user and their work that persist across conversations. It wires a +recall+ tool plus an automatic per-turn prefetch onto an agent via +c.add_extension Pikuri::Memory::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-vectordb+. Recall is automatic and synchronous (embed + vector search, milliseconds); capture is automatic and asynchronous (an off-the-interaction-path extraction queue), so a turn never blocks on "what should I remember?". Storage is mem0 (https://github.com/mem0ai/mem0) reached over a thin Faraday HTTP client — the append-only +add+ / read-time +search+ model. Only the *user's own words* are fed to extraction (a write-side hygiene rule that structurally drops system/assistant/tool-sourced junk), and recalled context enters the chat as a +:system+ message so it is provenance-tagged and excluded from the next extraction pass. This release ships the Ruby client + extension + tool against a *bring-your-own* mem0 endpoint; a self-managed mem0 sidecar supervisor (the +ChromaServer+-style docker pattern) is a follow-on.
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.