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

@dellasera/plugdo

v0.2.0

Published

plugdo Stack command line tool

Downloads

3

Readme

plugdo

plugdo Stack command line tool

oclif Version CircleCI Appveyor CI Codecov Downloads/week License

Usage

$ npm install -g @dellasera/plugdo
$ plugdo COMMAND
running command...
$ plugdo (-v|--version|version)
@dellasera/plugdo/0.2.0 darwin-x64 node-v8.11.3
$ plugdo --help [COMMAND]
USAGE
  $ plugdo COMMAND
...

Commands

plugdo apply

execute the release plan

USAGE
  $ plugdo apply

See code: src/commands/apply.js

plugdo bundle

Bundle import and export a stack configuration

USAGE
  $ plugdo bundle

OPTIONS
  -c, --create=create  name of the stack to be saved
  -l, --load=load      name of the stack to be imported
  -n, --name=name      the name will replace the stack name of the bundle for a new one
  -p, --path=path      directory path of the bundle for creation or import

DESCRIPTION
  Create bundle
  > plugdo bundle --create="stackName" --path="~/desktop/bundles"

  Load bundle
  > plugdo bundle --load="stackName" --path="~/desktop/bundles" --name="newStackName"

See code: src/commands/bundle.js

plugdo create

create stack, server, workspace and db

USAGE
  $ plugdo create

OPTIONS
  -a, --accesskey=accesskey      cloud access key
  -b, --branch=branch            github branch. It define the current code change in the deployment pipeline
  -c, --configs=configs          driver configurations, you can define many separated by comma
  -d, --db=db                    db name (lowercase without white spaces)
  -e, --envpath=envpath          define the file of the env variables required by the workspace
  -f, --path=path                workspace local path

  -g, --github=github            github url including the user and password. Example
                                 https://username:[email protected]/username/repository.git

  -h, --githubcopy=githubcopy    github url to be copied. Example
                                 https://username:[email protected]/username/repository.git

  -i, --server=server            server name (lowercase without white spaces)

  -k, --secretkey=secretkey      cloud secret key

  -l, --links=links              name of the workspaces linked by host name in the network

  -m, --description=description  component description

  -o, --os=os                    server OS. "linux" is the default and you can change it to "windows"

  -p, --port=port                port number for inbound access, you can define many separated by comma

  -r, --image=image              docker image name to be used in docker compose file

  -s, --stack=stack              stack name (lowercase without white spaces)

  -t, --type=type                define the workspace type, by default is static

  -u, --domain=domain            domain name of the workspace

  -w, --workspace=workspace      workspace name (lowercase without white spaces)

  -x, --expose=expose            port number exposed of the docker image

DESCRIPTION
  When you create a server, the configs of AWS driver is documented in the following link:
  - https://docs.docker.com/machine/drivers/aws/#options

See code: src/commands/create.js

plugdo delete

delete stack, server, workspace and db

USAGE
  $ plugdo delete

OPTIONS
  -d, --db=db                db name (lowercase without white spaces)
  -f, --force
  -i, --server=server        server name (lowercase without white spaces)
  -n, --none                 change the updated value to false
  -s, --stack=stack          stack name (lowercase without white spaces)
  -w, --workspace=workspace  workspace name (lowercase without white spaces)

See code: src/commands/delete.js

plugdo hello

Describe the command here

USAGE
  $ plugdo hello

OPTIONS
  -n, --name=name  name to print

DESCRIPTION
  ...
  Extra documentation goes here

See code: src/commands/hello.js

plugdo help [COMMAND]

display help for plugdo

USAGE
  $ plugdo help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

plugdo inspect

get the information of the stacks

USAGE
  $ plugdo inspect

OPTIONS
  -i, --server=server        server name (lowercase without white spaces)
  -s, --stack=stack          stack name (lowercase without white spaces)
  -w, --workspace=workspace  workspace name (lowercase without white spaces)

See code: src/commands/inspect.js

plugdo plan

create the release plan

USAGE
  $ plugdo plan

OPTIONS
  -j, --json
  -s, --show

See code: src/commands/plan.js

plugdo update

update stack, server, workspace and db

USAGE
  $ plugdo update

OPTIONS
  -a, --accesskey=accesskey      cloud access key
  -b, --branch=branch            github branch. It define the current code change in the deployment pipeline
  -b, --image=image              docker image name to be used in docker compose file
  -c, --configs=configs          driver configurations, you can define many separated by comma
  -d, --db=db                    db name (lowercase without white spaces)
  -d, --description=description  component description
  -e, --envpath=envpath          define the file of the env variables required by the workspace
  -f, --path=path                workspace local path

  -g, --github=github            github url including the user and password. Example
                                 https://username:[email protected]/username/repository.git

  -h, --githubcopy=githubcopy    github url to be copied. Example
                                 https://username:[email protected]/username/repository.git

  -i, --server=server            server name (lowercase without white spaces)

  -k, --secretkey=secretkey      cloud secret key

  -l, --links=links              name of the workspaces linked by host name in the network

  -n, --none                     change the updated value to false

  -o, --os=os                    server OS. "linux" is the default and you can change it to "windows"

  -p, --port=port                port number for inbound access, you can define many separated by comma

  -s, --stack=stack              stack name (lowercase without white spaces)

  -t, --type=type                define the workspace type, by default is static

  -u, --domain=domain            domain name of the workspace

  -w, --workspace=workspace      workspace name (lowercase without white spaces)

  -x, --expose=expose            port number exposed of the docker image

DESCRIPTION
  When you update a server, the configs of AWS driver is documented in the following link:
  - https://docs.docker.com/machine/drivers/aws/#options

See code: src/commands/update.js