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

indocker

v1.0.2

Published

A very simple tool that lets you execute commands/scripts inside a Docker container

Downloads

5

Readme

Indocker is a very simple tool that lets you execute commands/scripts inside a Docker container.

Why

One of the less obvious uses of Docker containers is not as a service package, but as a tool. Let me explain.

Imagine you are working on the next cool thing and all your great code builds without a hiccup on your machine, but then you push it and the automated build fails. You dig in and it turns out, that the tools you're using to build locally are not installed on the build server, or even worse, there is some version mismatch.

One way to go would be to try and install the correct versions on the build box. Then have everyone in the team synchronize their dev boxes, so they do not run into the same problem. And every time you need a change in the build environment you and your team will need to do this again.

If only there was a way to wrap your build environment in a nice package, that can be versioned and distributed as a single entity. Enter Docker. Just create an image with everything you need and use it as a build environment, that is exactly the same every time for everyone.

Unfortunately, this is easier said, than done. Building the image aside, when using the image, figuring out all the correct volume mappings, working folder, user settings, etc. can be rather tedious. And this is the motivation behind indocker - it will help you run inside a (tool) container by providing sensible defaults for this particular type of use.

Dependencies

You'll need to have Docker installed on your system.

Installation

With npm:

  npm i -g indocker

With yarn:

  yarn global add indocker

Example

To run make in myorg/my-build-img with the current directory mounted inside the container and set as a working directory:

  indocker -i myorg/my-build-img make

Usage

For a list of all options do:

  indocker --help