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

self-deployment

v1.0.6

Published

A fly.io-inspired deploy tool for self-managed SSH servers

Downloads

748

Readme

self-deployment

A fly.io-inspired deploy tool for self-managed SSH servers. Build Docker images locally and deploy them to your own VPS/servers via SSH.

Installation

npm install -g self-deployment

Or install locally:

npm install self-deployment

Quick Start

  1. Initialize a project:

    self-deploy init
  2. Edit deploy.toml with your server configuration.

  3. Build and deploy:

    self-deploy build
    self-deploy deploy

Configuration (deploy.toml)

app = "my-app"
registry = "localhost:5000"

[build]
  dockerfile = "Dockerfile"
  context = "."
  buildArgs = { NODE_ENV = "production" }

[[servers]]
  name = "prod-1"
  host = "192.168.1.10"
  port = 22
  user = "ubuntu"
  password = "your-password-here"

[[servers]]
  name = "prod-2"
  host = "192.168.1.11"
  port = 22
  user = "ubuntu"
  privateKey = "~/.ssh/id_rsa"

[deploy]
  image = "my-app:latest"
  port = 3000
  restartPolicy = "unless-stopped"
  env = { NODE_ENV = "production" }

Required Fields

  • app - Application name
  • [[servers]] - At least one server configuration
  • [deploy] section with:
    • image - Docker image name
    • port - Port to expose

Server Options

Each server requires:

  • name - Server identifier (e.g., "prod-1")
  • host - IP address or hostname
  • port - SSH port (default: 22)
  • user - SSH username
  • Either password or privateKey for authentication

Commands

self-deploy init

Creates a sample deploy.toml in the current directory.

self-deploy build

Builds the Docker image locally using the configuration in deploy.toml.

self-deploy build                    # Uses deploy.toml
self-deploy build -c custom.toml    # Custom config

self-deploy push

Pushes the built image to a Docker registry.

self-deploy push                    # Push to registry in config

self-deploy deploy

Deploys the application to all configured SSH servers.

self-deploy deploy                  # Deploy to all servers
self-deploy deploy -s prod-1       # Deploy to specific server

self-deploy status

Shows deployment status on all servers.

self-deploy status

self-deploy logs

Fetches logs from the deployed container.

self-deploy logs                   # Logs from first server
self-deploy logs -s prod-1        # Logs from specific server

self-deploy stop

Stops the running container on a server.

self-deploy stop                  # Stop on first server
self-deploy stop -s prod-1       # Stop on specific server

Docker Registry

For local development, you can run a local Docker registry:

docker run -d -p 5000:5000 --name registry registry:2

Then set registry = "localhost:5000" in your deploy.toml.

License

MIT