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

cloyster

v0.0.11

Published

Git deploy cluster based on ploy and node-discover

Downloads

4

Readme

cloyster

Think ploy + node-discover

Any ploy server you start via cloyster will discover other cloyster processes on the network and automatically propogate your git deployments to all other nodes within the cluster.

There is work to be done but this is already usable.

status

Currently pushing to a single node and propogating to all other nodes works. Commands such as ls, log, mv, rename, etc do not propogate throughout the network.

install

npm install -g cloyster

usage

usage:

  cloyster server DIRECTORY PORT
  cloyster server { -d DIRECTORY | -p PORT | -a AUTHFILE | -f BOUNCER | -n CLUSTER-NAME }

    Create a cloyster http server, hosting repositories in DIRECTORY and listening
    on PORT for incoming connections.
 
    If AUTHFILE is given, it should be a json file that maps usernames to
    token strings to use for basic auth protection for cloyster actions.
    
    Type `cloyster help ssl` to show ssl options.
    
    You can specify a BOUNCER module with -f to use a custom http router.

    If CLUSTER-NAME is given, it will be used as part of the node-discover encryption
    key. This will allow you to to run multiple clusters without having to 
        change the default node-discover port.

  cloyster ls { -r REMOTE | --verbose, -v | --format=FORMAT }
 
    List the running process branch names at REMOTE.
    
    Verbose formatting will use `branch,hash,repo,port`.
 
  cloyster work { -r REMOTE | --format=FORMAT }

    List the working directories from checked out git commits.
    The default FORMAT is `repo,commit,time,branch`.
 
    Active branches are shown with a trailing *.

  cloyster clean

    Remove unused working directories. These are the directories listed in
    `cloyster work` without a *.

  cloyster log NAME { -n ROWS | -f | -b BEGIN | -e END }

    Show ROWS of log output for the branch NAME like `tail`.
    Default -n value: screen height.
 
    Stream live updates when `-f` is set like `tail -f`.
    Slice log records for NAME directly with `-b` and `-e`.
 
  cloyster log { -n ROWS | -f | -b BEGIN | -e END | --color=true }

    Show ROWS of log output for all branches.
    Lines will be prefaced with a colored branch name when stdout is a tty.

  cloyster mv SRC DST { -r REMOTE }
 
    Move the branch name SRC to the DST branch name at REMOTE.
 
  cloyster rm NAME { -r REMOTE }
 
    Remove the branch name at NAME, killing any running processes.
 
  cloyster restart NAME { -r REMOTE }
 
    Restart the process at NAME.
 
  cloyster stop NAME { -r REMOTE }
 
    Stop the process at NAME.
 
  cloyster redecloyster NAME { -r REMOTE }
 
    Redecloyster the process at NAME, re-running install and test scripts.
 
  cloyster help [TOPIC]
 
    Show this message or optionally a TOPIC.
    
    Topics: ssl

OPTIONS

  For `cloyster ls`, `cloyster mv`, `cloyster rm` commands that take a REMOTE parameter:
  
  REMOTE can be a git remote name or a remote URL to a cloyster server. If there
  is exactly one cloyster remote in set up as a git remote, it will be used by
  default.

license

MIT