npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

coreos

v0.1.4

Published

the missing CoreOS cli for creating and managing clusters on different providers

Downloads

17

Readme

coreos

the missing CoreOS cli for creating and managing clusters on different providers

Warning:

Currently we only support Microsoft Azure Cloud. Feel free to PR your own account provider class.

Cli

Installation

npm install --global coreos

Usage

Please check --help with cli for further details.

coreos --help
Examples:
# Change to home dir so we can save config on "~/.coreos.json"
cd ~;

# Add an Azure Account
coreos account add \
    --provider="Azure" \
    --subscription="xxxx-xxxxx-xxxxxxx...." \
    --pem="/your/path/to/cer.pem";

# Say to CoreOS instance we will use this on next commands
coreos account setCurrent \
    --account="{account-id}"

# Now, lets say we want to add an azure-based node into our cluster
coreos node create \
    --location="West US"

# for instance you may want to access to node shell
coreos node ssh --node="{nodeid}"

# Or execute a command with local files (example, submitting an unit)
coreos node exec -- fleetctl submit :/my/local/unit.service

# Its easy right? If you think so, star this project!

See more examples

Node.js / io.js

Installation

npm install --save coreos

Usage

Please check API for further methods details.

Examples:
var CoreOS = require( 'coreos' );
var cos = new CoreOS({
        // Don't read configuration file
        loadConfigOnInit: false,
    });

// Add an Azure Account
var azure = new CoreOS.Account.Provider.Azure(
        {
            subscription: 'xxxx-xxxxx-xxxxxxx....',
            pem: fs.readFileSync( '/your/path/to/cer.pem' );
        },

        // Notice we are passing current CoreOS instance
        cos
    );

// Say to CoreOS instance we will use this
// on next commands
azure.setAsCurrent();


// Now, lets say we want to add an azure-based node
// into our cluster

cos.nodeCreate({
    location: 'West US',
})

// As it returns a promise (hell yeah!!), we can then
// do something with node's info
.then(function ( node ) {
    console.log( node );
});


// Its easy right? If you think so, star this project!

See more examples

Motivation

findhit entered Microsoft BizSpark program recently and we ended up choosing CoreOS as our cloud cluster OS. We did a bunch of internal bash scripts for handling cluster scaling and its resources but it ended up too hard to maintain.

As CTO, I've decided to create a cli manager as our scaling endpoint.

Contributing

Feel free to contribute by creating Issues or Pull Requests.