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-pages-webhook

v0.2.0

Published

Set up your gitlab-pages server base on gitlab's web hook!

Downloads

15

Readme

Readme

Github-pages is cool,but what about gitlab?This project helps you to set up a web hook server for your gitlab,so you can deoply your gitlab-pages,it's easier and powerful then your image,try it out.

Install

npm install -g gitlab-pages-webhook

Web hook server configuration

Start a web hook server

//gitlab-pages-webhook [listen port] [gitlab host,...]
gitlab-pages-webhook 8163 http://mygitlab.com,http://mygitlab2.com

gitlab hosts tells the hook to filter which host to listene,in this case,only gitlab host http://mygitlab.com and http://mygitlab2.com will deploy to your server,http://mygitlab3.com will not.

Set a nginx proxy to your web hook server,such as

server {
    listen 80;
    server_name  myserver.com;
    root /home;
    index index.html index.htm;

    error_page 405 =200 @405;
    location @405{
  	root /home;
	proxy_method GET;
    	proxy_pass http://static_backend;
    }
    access_log  off;
    error_log off;
    location / {
        # First attempt to serve request as file, then
        # as directory, then fall back to displaying a 404.
        try_files $uri $uri/ /index.html;
        # Uncomment to enable naxsi on this location
        #include /etc/nginx/naxsi.rules
        #autoindex on;
    }
    location ~* ^/.*/$ {
        #alias /usr/share/doc/;
        #autoindex on;
        #allow 127.0.0.1;
        #allow ::1;
        #deny all;
    }
    location /doc/ {
        alias /usr/share/doc/;
        autoindex on;
        allow 127.0.0.1;
        allow ::1;
        deny all;
    }
    location /deploy/ {
        proxy_pass http://127.0.0.1:8163;
    }
}

Web Hook Guide

Add your web hook server URL to your repo

YourPorject --> Settings --> Web Hooks --> URL values is Your web hook server RUL --> click "Add web Hook"。

Make sure your repo is Publick

YourPorject --> Settings --> Edit Project --> select Public mode: Public access。

deploy a branch(default is master) and a tag

The web hook server is http://myserver.com/deploy/[?branch=branch1&tag=v1.0.0]

eg. switch to branch1

http://myserver.com/deploy/?branch=branch1

switch branch1 and tag v1.0.1:

http://myserver.com/deploy/?branch=branch1&tag=v1.0.1

use bower|grunt|gulp task

//run bower update task
http://myserver.com/deploy/?bower=update

//run grunt default task,task name is required!
http://myserver.com/deploy/?grunt=default

//run gulp default task,task name is required!
http://myserver.com/deploy/?gulp=default

//run bower update then run gulp default task
http://myserver.com/deploy/?bower=update&gulp=default