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

docker-container-proxy

v1.0.1

Published

command line tool for proxying docker containers easily

Downloads

11

Readme

npm version Build Status

Dockerproxy

A little command line tool based on ncarlier/redsocks to proxy all running docker containers, without the need to configure anything inside of them.

Installation

npm i -g docker-container-proxy

Run dockerproxy setup in order to never remember your proxy server address again..

Interface

Usage: dockerproxy [options] <command>

Proxy any Docker-Container

Options:
  -v, --version  output the version number
  -h, --help     output usage information

Commands:
  up|u           start proxying Docker-Containers
  down|d         stop proxying Docker-Containers
  config|c       Print the config
  setup|s        setup this command tool in order to use it without options
  help [cmd]     display help for [cmd]

Examples:
  $ dockerproxy up      # start the Docker Proxy
  $ dockerproxy down    # stop the Docker Proxy

Up

Usage: dockerproxy up [options]

Options:
  -a, --address [domain]      proxy server address
  -p, --port [number]         proxy server port (default: "8080")
  -n, --network <name>        docker network interface that should be proxied
  -w, --whitelistFile <path>  proxy server address
  --containerName <string>    proxy server Container Name (default: "docker_proxy")
  -h, --help                  output usage information

Down

Usage: dockerproxy down [options]

Options:
  --containerName <string>  proxy server Container Name (default: "docker_proxy")
  -h, --help                output usage information

Setup

Usage: dockerproxy setup [options]

Setup this command line tool in order to use it without options

Options:
  -h, --help  output usage information

Config

Usage: dockerproxy config [options]

Display the config

Options:
  -h, --help  output usage information

Example

There are two ways of using this command line tool:

  1. Recommended:
    • Configure the cli interactively for easier use later on (just type dockerproxy setup)
    • Use either dockerproxy up or dockerproxy down for starting or stopping the proxy.
  2. For starting right away or usage in scripts:
    dockerproxy start --address company-proxy-address.com --port 8080

    You can use --network to specify a docker interface that should get proxied. (by default all networks get proxied)

Development and Debugging

  1. Clone the repository and including the submodules (git submodule update --init --recursive)
  2. Launch command with node --inspect-brk dockerproxy.js setup.
    1. Follow this guide.
    2. Launch Attach to Remote Debug Task in VSCode.

Testing

Install bats (npm i -g bats) and expect (sudo apt-get install expect). Simply run npm run test afterwards.