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

dorky

v2.1.2

Published

DevOps Records Keeper.

Downloads

8,044

Readme

dorky

     __            __
 .--|  .-----.----|  |--.--.--.
 |  _  |  _  |   _|    <|  |  |
 |_____|_____|__| |__|__|___  |
                        |_____|

DevOps Records Keeper

dorky npm

Made with love in India && javascript

Let us assume that we need to create a project.

The project obviously contains some code and some secret variables like database information, API keys, etc. This data cannot be shared on public VCS (GitHub), but at times is required to be accessible remotely to be shared among reliable sources.

Anyhow, we shall store it on a private storage, using dorky, that stores it on a S3 or Google-Drive.

AWS S3

Steps to use with S3:

Create a S3 bucket, AWS_ACCESS_KEY and AWS_SECRET_KEY.

Dorky Usage

Please use your own repository, this repository sample_project is just for demonstration.

To list files in the project.

  1. Initialize dorky setup in the root folder of your project, using dorky --init aws.
  2. List the files using dorky --list.

    This command will not list the files that are excluded in .dorkyignore.

To push files to S3 bucket.

  1. Initialize dorky setup in the root folder of your project, using dorky --init aws.
  2. List the files using dorky --list, (make sure to add excluded file or folder patterns to .dorkyignore, to minimize the list).
  3. Add files to stage-1 using dorky --add file-name.
  4. Push files to S3 bucket using dorky --push.

To remove a file from project.

  1. Remove files using dorky --rm file-name. [Removes file from stage-1 ]
  2. Push files to S3 bucket using dorky --push. [Removes file from S3 bucket ]

To pull files from S3 bucket.

  1. Use dorky --pull to pull the files from S3 bucket.

Google Drive

Steps to use with Google Drive:

Dorky Usage

Please use your own repository, this repository sample_project is just for demonstration.

To list files in the project.

  1. Initialize dorky setup in the root folder of your project, using dorky --init google-drive.
  2. List the files using dorky --list.

    This command will not list the files that are excluded in .dorkyignore.

To push files to Google Drive.

  1. Initialize dorky setup in the root folder of your project, using dorky --init google-drive.
  2. List the files using dorky --list, (make sure to add excluded file or folder patterns to .dorkyignore, to minimize the list).
  3. Add files to stage-1 using dorky --add file-name.
  4. Push files to Google Drive using dorky --push.

To remove a file from project.

  1. Remove files using dorky --rm file-name. [Removes file from stage-1 ]
  2. Push files to Google Drive using dorky --push. [Removes file from Google Drive ]

To pull files from Google Drive.

  1. Use dorky --pull to pull the files from Google Drive.

To-Do

[ ] Add stages for variables. [ ] Convert to TypeScript.