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

geppetto

v1.1.1

Published

SOA local development made easy. Run multiple processes with defined and common ENV's

Downloads

50

Readme

https://travis-ci.org/taterbase/geppetto #Geppetto

SOA local development made easy.

Geppetto makes it simple to script the launch of all your local services with the desired environment variables

##Contents

##Installation

npm install -g geppetto

##Usage

If you have a geppetto.json in the local directory, you can just run geppetto. If you have a file named something other than geppetto.json use the -f or --file flag.

geppetto -f config.json

Define a json configuration file with the processes that you want running. You can define a:

  • Required
    • command - The command being called to launch the process
  • Optional
    • dir - The directory you want the process to be launched from. dir supports $ENVIRONMENT variable expansion.
    • env - A hash of process specific environment variables you want the process to have
    • install - A sub level of options to perform to install the necessary files (if dir is nonexistent)for the process (install overrides git option)
    • postinstall - A sub level of options to perform after installation
    • git - If dir is nonexistent it will be cloned down locally
    • postgit - Sub level options to run on directory after cloning down with git
{
  "api_server": {
    "dir": "$PWD/node-server",
    "install": {
      "command": "curl",
      "arguments": ["-O", "https://example.com/api_server"]
    },
    "postinstall": {
      "command": "npm",
      "arguments": ["install"]
    },
    "command": "node",
    "arguments": [ "app.js" ],
    "env": {
      "PORT": "1337"
    },
  },
  "app_server": {
    "git": "https://github.com/me/app_server",
    "postgit": {
      "command": "bundle",
      "arguments": ["install"]
    },
    "command": "rails",
    "arguments": ["s"],
    "env": {
      "API_URL": "http://localhost:1337"
    }
  }
}

###Common Globals There are also top level keys that can be defined to set global common options:

  • _env Common environment variables for each service
{
  "_env": {"LEVEL": "1", "BOSS": "SnapBack"},
  "game": {"command": "cat", "arguments": ["index.js"], "env": {"LEVEL": "2"}}
}
//game env will be `{LEVEL: 2, BOSS: "SnapBack"}

###Commands

-r --run

You can run select services from a configuration file by passing in the -r or --run flag specifying which services.

geppetto -r worker -r webapp -r proxy

-e --export-env

You can "export" the environment variables for an app using a -e or --export-env flag and an optional app name.

geppetto -e [app-name]

If no app is specificed all _env values will be printed, if an app is specified its specific env variables will be printed as well. You can pipe these into a file and source it in bash.

Example output:

export SOME_ENV=your_value
export SOME_OTHER_ENV=your_other_value

Made with ⚡️ by @taterbase