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 🙏

© 2026 – Pkg Stats / Ryan Hefner

zipdeploy

v0.0.1

Published

Zip a directory and upload it to a url

Readme

zipdeploy

This is a "poor man's DevOps tool". With a "poor man" I mean a startup without investors.

Understand, a baba is a poor man, but he is free and wise.

Introduction

zipdeploy consists of two components. The server components accept a posted zip file and extracts it in a configured folder. The client component zips a folder together and uploads it to a url.

Server

The server component is written in php and is initialized like this:

require_once "ZipDeploy.php";

$zipDeploy=new ZipDeploy();
$zipDeploy->createTarget("hello");
$zipDeploy->dispatch();

The ZipDeploy.php file referenced in the require_once statement is this one.

If we save this file as publish.php, and make it available on a url, we can then post or upload files to:

http://our.server/publish.php?target=hello

And have it extracted in the folder "hello" relative to where the script is saved. We can set some other options related to our target like this:

$zipDeploy->
    createTarget("hello")->
    setTargetDir("/some/path/on/the/server")->
    setKey("my_secret_key");

This will cause the contents of the uploaded zip file to be extracted to /some/path/on/the/server, and it will also require a key to be sent along with the request. The request will have to look like this:

http://our.server/publish.php?target=hello&key=my_secret_key

Or else the server will reject it.

Client

In order to talk to a server set up in the way specified above, there is also a client component. The client component comes in two flavors, one is a command line tool, the other is a grunt task. They are both contained in the same npm package, so install them with:

npm install zipdeploy

You might want to install it using -g if you use the command line option and with --save-dev if it will be part of your npm project as a grunt task. But this is standard npm stuff, and beyond the scope of this readme file.

In order to use the command line version, run:

zipdeploy --target=hello path/to/my/dir http://our.server/publish.php

In order to define a grunt task, use:

grunt.initConfig({
	zipdeploy: {
		publish: {
			dir: "path/to/my/dir",
			url: "http://our.server/publish.php",
			target: "hello",
			key: "my_secret_key"
		}
	}
});