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

hubot-deploy-custom

v0.1.0

Published

An example script package for Hubot

Downloads

20

Readme

hubot-deploy-custom

Hubot Script for providing deploy ability with custom scripts

Adds a new command to hubot: Currently only supporting deploying to one target (prod) (name of hubot) deploy <target> <ref to deploy> (name of hubot) deploy <target> makes the default action defined in deploy.conf (name of hubot) deploy defaults to (name of hubot) deploy stage

Upgrading

Save your deploy.conf somewhere outside the node_modules folder

Config

renaming deploy.conf.example -> deploy.conf

Added a new filed to the config where you can put the repo name from gitlab so it knows which config to use to deploy on commit deployhook web-repo-name web-repo-name should be the name of the repositoriy add hubot.url.com/deploy as a push hook on your repo

HUBOT_DEPLOY_CUSTOM_CHANNEL put this into your environment so hubot knows where to post things to

Workflow for working with this addon

  1. commit all things
  2. (test it)
  3. Increase Version and commit a new tag
  4. push to server git push origin
  5. chat with hubot hubot deploy <target>

Upgrading

Save your deploy.conf to another location than node_modules

##From before 0.0.9 to 0.0.9 or after: Add HUBOT_DEPLOY_CUSTOM_CHANNEL to your environment

Work based on following people

Uses nice deploy script from visionmedia https://github.com/visionmedia/deploy

Matt Pegler for the inspiration http://www.pegler.co/2012/03/django-deployment.html

Directory Structure

Using the common directory structure for hubot script packages it will be easy to manage and allow others to easily contribute to your package.

script

This directory is home to a couple of development scripts; bootstrap and test they're used to bootstrap the development environment and run tests respectively.

src

This directory is home to the actual hubot scripts in the package. Your index.coffee entry point will load the scripts from this directory.

test

This directory is home to any tests you write for your scripts. This example package uses Mocha, Chai and Sinon to manage writing tests.

Advantages of Building a Package

Some of the advantages of building an npm package for your hubot script(s) are:

  • You don't need to rely on when hubot-scripts package is released.
  • You can specify dependencies in the package.json rather than have users manually specify them
  • You can easily add tests using your favourite frameworks and libraries