This is a sample package
my package description
��my package
My package eve-utils
a rewrite version of my package nvlang
 [](https://circleci.com/gh/megatroom/check-my-package-version)
My package esi-service
My package web-server
My package
A description of my package
My package description
My package configurator
my package for test
My package description
My package
"my package"
My package description
## How to install ```bash npm i @biancakaritas/my-package ```
My package description
My Package
My package description
My Package
My Package Description
first publish my package!
Online store library
Semantic versioning and release automation tool following the Conventional Commits specification
Tool to check and compare binary sizes of Rust projects
Maxima Package Manager
MoosicBox clippier package
A Cargo subcommand that merges all Rust source files in a package into a single file.
A Rust implementation of sort-package-json that sorts package.json files according to well-established npm conventions
Configuration-driven REST backend library for Rust with PostgreSQL — define schemas, tables, and APIs in JSON, get a production-grade REST service.
A cli for typst packages.
A cargo subcommand for cross-compilation, no need docker!
Access Rust crate documentation from the CLI
Nargo compiler and toolchain
ruby package for demo purposes
Some summary
aaaaa
My favorite rails apps tools
My solution for the cyrus-code-challenge, packaged into a CLI gem.
This package is not supported in the same sense that my other packages are, but since it is such a fun playground, I am very open to contributions, suggestions, and bug fixes. I just can't put this project at the top of my priority list the way I can/do the others, so it may take me longer to get to than normal.
A packaged version of my gist https://gist.github.com/ushu/129b3340c51a205157c1e2daa1da55fa. It calls the Heroku CLI to grabs the necessary info, then prints the result on STDOUT.
[Cejo] Miscellaneous Unix automation and services utilities [Sections] [Ops] Bundle of automation tasks [Media] Management of media [Projects] Instructions to install FLOSS Project [Distro] A one-do-it-all package porcelain for most use Distro Linux package managers [Install] [rubygems] gem install cejo [local] rake [Why Cejo?] Named after my grandparents: Celina & Joseph [License] GPL version 3
A nice Ruby interface to your system's MIDI services. MIDIator was inspired by Topher Cyll's fantastic Practical Ruby Projects book. In it, Topher describes how to interact with the MIDI providers in OSX, Linux, and Windows. As I was reading the book, I noticed some things I would do differently, which got me thinking that maybe it would be valuable to package up my modifications to the book's code and release it as a gem.
Is there a gem author around you? Did you meet any author of the gems used? Did you contact with any author of the gems used on the Internet? Do you think that "the author is cool!", "the author is awesome!" or "I respect the author!"? Do you want to be a gem author? This talk doesn't describe about how to create a gem because it is easy. "gem" is a package of Ruby library (, tool and so on) for easy to install. This talk describes about developing a library that is gem content. This talk is based on my experience as a library developer. This talk describes about how to write codes, how to write documents, release, support and mental set for a better "library developer". I hope that this talk is a trigger for increasing the number of better "library developers".
Simple tool to resize AWS instances with EBS root.
# Footman This gem is still growing. ## Installation Depends upon having reprepro tool installed (if debian based) or createrepo installed (if red hat based). Ruby 1.9.+ is required to use this gem. 'createrepo' (rpm) tool does not require any pre-setup to the repository or watched directory. - - - 'reprepro' (deb) tool requires pre-setup. The repository directory for deb files must contain: <pre><code> conf/ conf/distributions conf/options conf/override.precise </pre></code> options file is empty, but needed to make reprepro happy distributions file will contain: <pre><code>Origin: Tyler Label: Tyler's Personal Debs Codename: precise Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.precise DscOverride: override.precise Origin: Tyler Label: Tyler's Personal Debs Codename: lenny Architectures: i386 amd64 source lpia Components: main Description: Tylers Personal Debian Repository DebOverride: override.lenny DscOverride: override.lenny </code></pre> Note that the code name is for each distribution repository you support. for each distribtuion repository you support there must be an override file. override file can be left empty, footman will fill it out when a new package is added. The watched directory must have sub directorys named after each of the distribution repositories you support. For example my watched directory at /path/ will have two subdirectories: <pre><code>/path/lenny/ /path/precise/</code></pre> Packages must be dropped into the subdirectory that corrosponds with the distribution they were built on. - - - Add this line to your application's Gemfile: gem 'footman' And then execute: $ bundle Or install it yourself as: $ gem install footman Or locally: $ gem build footman.gemspec $ gem install footman --local ## Usage footman path/to/watch path/to/repo ## Contributing 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create new Pull Request
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.