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

splunkdev-cli

v0.1.9

Published

Splunk development command line interface.

Downloads

24

Readme

The Splunk Dev Command Line Interface (CLI)

When developing Splunk apps, you can use the Splunk Dev command-line interface (CLI) to make it easier to create and manage apps. The Splunk Dev CLI uses Yeoman for templates and Grunt for watch tasks.

Prerequisites

The Node Package Manager (NPM) is used to configure and set up the Splunk Dev CLI, so Node.js must be installed first. To download the latest version of Node.js (we recommend version 0.10.x or later), go to the Node.js website.

Install the Splunk Dev CLI

To install the Splunk Dev CLI (along with dependencies such as Yeoman), open a command prompt and enter the following command:

npm install -g splunkdev-cli

Now you'll have access to the Splunk Dev CLI globally, from anywhere on your system.

Using the Splunk Dev CLI

Use the splunkdev command to access the Splunk Dev CLI.

Usage

To use the Splunk Dev CLI, open a command prompt and use the splunkdev command as follows, where optional items are in square brackets:

splunkdev options

splunkdev command [command options] [options]

Options

The following table lists the possible command-line options.

Commands

The following table lists the splunkdev commands.

Examples

To get help for the splunkdev command:

splunkdev –h

splunkdev –-help

To get help for the splunkdev commands apps and watch:

splunkdev apps –h

splunkdev watch –-help

splunkdev apps

Use the splunkdev apps command to list and manage your Splunk apps. If you don't specify any options, all non-system, enabled apps are listed.

Usage

splunkdev apps [appname] [options]

Options

The following table lists the possible command-line options.

Examples

List installed apps:

splunkdev apps

List all apps, including disabled and system apps:

splunkdev apps --disabled –-system

List all the apps that start with "test":

splunkdev apps test*

Remove the app called "my_app":

splunkdev apps my_app –-remove

Remove all apps with names that start with "test":

splunkdev apps "test*" –-remove

Change the state of the "my_app" app to disabled:

splunkdev apps my_app --state disabled

Change the state of the "my_app" app to enabled:

splunkdev apps my_app --state enabled

splunkdev config

Use the splunkdev config command to configure the CLI login credentials for the current Splunk instance. These credentials are used by splunkdev commands that communicate with splunkd, such as watch, reload, and settings.

Usage

splunkdev config [options]

Options

The following table lists the possible command-line options.

Examples

Set the CLI login credentials:

splunkdev config

splunkdev create

Use the splunkdev create command to create a Splunk app. You'll be asked whether to restart Splunk afterwards.

Usage

splunkdev create appname

splunkdev create [options]

Options

The following table lists the possible command-line options.

Examples

Create an app called "my_app" without installing node dependencies locally:

splunkdev create my_app

Create an app called "my_app2" and install local node-based tools:

splunkdev create my_app2 -d

splunkdev reload

Use the splunkdev reload command to reload resources and configurations for all apps, without restarting Splunk.

Usage

splunkdev reload [options]

Options

The following table lists the possible command-line options.

splunkdev settings

Use the splunkdev settings command to specify whether to use minified files in Splunk.

Usage

splunkdev settings [options]

Options

The following table lists the possible command-line options.

Examples

Use unminified CSS and JS files in the web environment:

splunkdev settings -m false

splunkdev service

Use the splunkdev service command to start, stop, and restart Splunk services. If a particular service is not specified, the action is performed on all services.

Usage

splunkdev service {start | stop | restart} [options]

Options

The following table lists the possible command-line options.

Examples

Start all Splunk services:

splunkdev service start

Restart all Splunk services:

splunkdev service restart

Stop all Splunk services:

splunkdev service stop

Start the splunkd service:

splunkdev service stop -s splunkd

Restart the splunkweb service:

splunkdev service restart --service splunkweb

splunkdev watch

Use the splunkdev watch command to watch for changes to a specific app or to Splunk. When a change occurs that requires restarting a Splunk service or reloading a configuration file, that action is performed automatically. For example, changes to app configuration or Python files require the app resources to be reloaded, and changes to the app's navigation file require splunkweb to be restarted.

To stop the current watch task, press Ctrl+C.

Usage

splunkdev watch [options]

Options

The following table lists the possible command-line options.

Examples

Watch for changes to the "my_app" app:

splunkdev watch --app my_app