Create a docker release and push it to a registry
The Nx Plugin for Docker to aid in containerizing projects.
docker package
Check if the process is running inside a Docker container
checks the all of the hyperlinks in a markdown text to determine if they are alive or dead
Docker dictionary for cspell.
🚇 Hermes bytecode compiler for Metro.
Find broken links, missing images, etc in your HTML. Scurry around your site and find all those broken links.
Manage docker-compose from Node.js
Docker Remote API module.
[@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
app-builder precompiled binaries
Multi-channel AI gateway with extensible messaging integrations
The official command line interface for managing LaunchDarkly feature flags.
Various JavaScript/TypeScript utilities of wide relevance to the MetaMask codebase
Command-line interface for mermaid
The buf CLI is a tool for working with Protocol Buffers.
Check if the process is running inside a container (Docker/Podman)
TypeScript definitions for docker-modem
A command-line tool for validating and enforcing best practices in Docker Compose files.
[](https://cdk.dev) [](https://github.com/aws/jsii
The official MongoDB driver for Node.js
Create cross-toolchain from https://github.com/rust-cross/manylinux-cross/tree/main
semantic-release plugin to create or update a changelog file
Cartage provides a repeatable means to create a package for a server-side application that can be used in deployment with a configuration tool like Ansible, Chef, Puppet, or Salt. The package is created with vendored dependencies so that it can be deployed in environments with strict access control rules and without requiring development tool presence on the target server(s). This is the last release of cartage. It's been a fun ride, but Docker-based images are our future at Kinetic Commerce. There is one feature that remains useful, the release-metadata output. We have created a new, more extensible format for which we will be creating a gem to manage this. One example of the implementation can be found at: https://github.com/KineticCafe/release-metadata-ts We will also be replacing `cartage-rack` with a new gem supporting this new format.
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).
No description provided.
No description provided.