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

@gstore-org/cli

v1.1.0

Published

This is the GStore cli used for automated tasks.

Downloads

102

Readme

GStore CLI

GStore CLI simplifies the integration of GStore into your automated workflows, such as backups and CI/CD pipelines. It provides a robust and user-friendly interface to streamline common tasks while ensuring reliability through optional file tracking and clean logging.

Features

  1. JSON-Based Configuration:
    Easily configure the CLI with a JSON file to declare the API key, API host, and actions to execute.

  2. File Tracking (Optional):
    Prevent duplicate file creations by specifying a trackingFile in your configuration. The CLI will track file paths and their corresponding remote IDs.

  3. Input Validation with Zod:
    All input files and configurations are validated using Zod, ensuring correctness and preventing errors.

  4. JSON Schema Generation:
    Generate JSON schemas directly through the CLI to enable autocompletion and validation for your configuration and tracking files.

  5. Clean Logging:
    Get clear and structured logs for every action executed, making it easier to debug and monitor your workflows.

How It Works

  1. Configuration File:
    Start by creating a JSON configuration file. Specify:

    • Your GStore API key.
    • The API host.
    • The actions you want to perform.
    • (Optional) A trackingFile path to keep a local record of file IDs.
  2. Actions:
    Actions can either:

    • Correspond directly to GStore API endpoints (e.g., create, delete, update).
    • Extend functionality with wrappers like createDir, which uploads all files in a directory.
  3. File Tracking:
    If you enable tracking, the CLI will map local file paths to their corresponding remote IDs. This ensures the same file isn’t created twice during subsequent runs.

Available Actions

The CLI focuses on actions that are most useful for automation, leaving out actions like reading or listing files. Currently supported actions include:

  • create: Upload a single file.
  • createDir: Upload all files within a specified directory.
  • delete: Delete a file by its remote ID.
  • update: Update an existing file.

Getting Started

Step 1: Install the CLI

Make sure you have Node.js installed, then install the CLI globally via npm:

npm install -g @gstore-org/cli

Step 2: Generating Schema

Generate JSON schemas for your configuration and tracking files to enable editor autocompletion:

gstore-cli generate-schema

Step 3: Create a Configuration File

Define your actions in a JSON configuration file, specifying your API details, actions, and optional tracking.

Example Configuration File (config.json):

{
  "$schema": "./config.schema.json",
  "key": "your-api-key",
  "host": "https://api.gstore.io",
  "trackingFile": "./tracking.json",
  "actions": [{ "name": "create", "data": { "path": "./image.jpg", "isPublic": true, "tags": ["image"] } }]
}

Step 4: Run the CLI

Execute the desired actions by pointing the CLI to your configuration file:

gstore-cli sync --configPath config.json