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

gitlab-autodeploy

v0.1.9

Published

Autodeploy utility

Downloads

3

Readme

gitlab-autodeploy

Handle gitlab post requests easier.

Autodeploy server example

Create an index.js in your 'adserver' with

const ad = require('gitlab-autodeploy')
const { repositoryIsUpdated, execOn } = ad.utils

ad.configServer({
  expressHostname: 'my.domain.com', // Domain to be used in gitlab hook config
  expressPostUrl: '/',              // Route used to listen post's from gitlab
  expressPort: 8000,                // Express port
  tcpPort: 9000,                    // Tcp port (to comunicate with other local servers)
  secretToken: 'someSecretToken'    // Received as x-gitlab-token header
})

ad.listen()

const repoNamePath = '/var/node/repoName'

// Handling a post from gitlab for repo 'repoName' 
ad.on('repoName', (payload, done) => {
  (async () => {
    if (await repositoryIsUpdated(repoNamePath)) {
      console.log('Repository already up to date')
    } else {
      console.log('Applying some changes')
      if (foo(payload)) {
        // Check something in payload
      }
      await execOn(repoNamePath, 'git fetch && get merge')
      done() // This must be called at the end
    }
  })()
})

Configuring your express application

Register gitlab-autodeploy in your application with

const express = require('express')
const app = express()

//
// Import and configure your modules
//

// Import and configure gitlab-autodeploy
const ad = require('gitlab-autodeploy')
ad.configClient({
  tcpPort: 9000,
  busyRoute: (req, res, next) => {
    // Make something when autodeploy is busy
  }
})
const adclient = ad.createClientRoute()

// And finally, use it in your application
// to comunicate with the autodeploy server.
app.use(adclient)

Further information will be added in the next weeks.