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

@hotglue/cli

v1.0.27

Published

hotglue CLI tools

Downloads

794

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ddasouzaddasouzahassansyyidhassansyyid

Keywords

hotglueclietl

Readme

@hotglue/cli npm version

The hotglue Command Line Interface (CLI)

Table of Contents

Installation

You can install the CLI globally (recommended) using

npm install -g @hotglue/cli

And then you can run it from anywhere using

hotglue --help

Alternatively, you may install it locally in a project folder using

npm install --save-dev @hotglue/cli

And then you can run the local installation from within that folder using

npx hotglue --help

Usage

Usage: hotglue <command>

Commands:
  hotglue config                  View global CLI settings (ie. apikey)
  hotglue config set              Configure global CLI settings (ie. apikey)
  hotglue env download            Download environment settings (ie. requirements.txt)
  hotglue env deploy              Deploy environment settings (ie. requirements.txt)
  hotglue etl download            Download ETL script files
  hotglue etl deploy              Deploy ETL script files
  hotglue snapshots download      Download snapshot files
  hotglue snapshots deploy        Deploy snapshot files
  hotglue flows list              List flows for a given environment
  hotglue jobs list               List all jobs for a given flow
  hotglue jobs download           Download jobroot files to the specified location
  hotglue tenants list            List the tenants in the environment

Options:
  -k, --apikey              Your API Key                                  [string]
  -e, --environment         Environment ID                                [string]
  -f, --flow                Flow ID                                       [string]
  -t, --tap                 Tap ID                                        [string]
  -u, --tenant              Tenant ID                                     [string]
  -j, --jobroot             A job root path                               [string]
  -d, --downwloadTo         The target download location                  [string]
  -s, --sourceFolder        The source directory                          [string]
  -o, --overwrite           Overwrite existing files?                     [boolean]

  -v, --version             Show version number                           [boolean]
  -h, --help                Show help                                     [boolean]

Configuration

The hotglue CLI derives its configuration from two places: the User/Profile settings and the Project settings.

The User settings are stored in a config.yaml file located at $HOME/.hotglue/. At the moment, it is only used to store your apikey.

The Project settings are stored in a hotglue rc-like file and can be created anywhere in your project's folder structure. A Project settings file can hold any of the CLI's parameters (including overriding the apikey, even though we do not recommend it) is used in order to define configuration values specific for that context

Project configuration files

The configuration files can use any of the following names: hotglue.yaml, .hotglue.yaml, .hotgluerc.yaml, .hotgluerc.yml, .hotgluerc, .hotgluerc.json, .hotgluerc.js

As the extensions suggest, the files support either yaml, json or js syntax (in case of JS, the config object has to be exported). However, we recommend using the yaml format.

Additional info

  • When deploying files, symbolic links are not followed.

Documentation