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-dashboard-proxy

v1.2.3

Published

An event based cache for gitlab dashboards using webhooks.

Downloads

8

Readme

gitlab-dashboard-proxy

An event based cache for gitlab dashboards using webhooks.

npm version Build Status Coverage Status Known Vulnerabilities JavaScript Style Guide

Install

Using Yarn:

yarn global add gitlab-dashboard-proxy

Using Docker:

docker pull nadavami/gitlab-dashboard-proxy

Usage

  1. Start gitlab-dashboard-proxy using Yarn:
export GITLAB_URL=https://gitlab.com
export PORT=8080 # Optional. Default is 3000

gitlab-dashboard-proxy
  1. Start gitlab-dashboard-proxy using Docker:
docker run -d -e GITLAB_URL=https://gitlab.com -p 8080:3000 nadavami/gitlab-dashboard-proxy
  1. Configure your dashboard to use <gitlab-dashboard-proxy url>/gitlab instead of GitLab's url.
  2. Configure your GitLab project or group to trigger a pipeline event webhook on <gitlab-dashboard-proxy url>/update.
  3. That's it!

Routes

  • GET /gitlab -> Proxies connections to GitLab and caches requests for projects
  • POST /update -> Clears a single project's cache based on a GitLab pipeline webhook
  • GET /cache -> Returns a JSON object containing cached paths
  • GET /cache/clear -> Clears the entire cache

Debugging

Debug logs can be switched on by setting the environment variable DEBUG=gitlab-dashboard-proxy.

Q&A

When would I need this?

We DDoSed our GitLab instance after having many dashboards monitor many pipelines. Just adding a single display that polls every 10s visibly increases server load. This project provides an event based cache to shield GitLab from the large number of API requests.

Wouldn't it be better to just have an event based pipeline dashboard?

Yes.

Shouldn't GitLab have a built-in dashboard?

Yes.