verdaccio-gitlab - private npm registry (Verdaccio) using gitlab-ce as authentication and authorization provider

  •        43

Use GitLab Community Edition as authentication provider for the private npm registry Verdaccio, the sinopia fork. You need at least node version 8.x.x, codename carbon.

https://github.com/bufferoverflow/verdaccio-gitlab

Dependencies:

gitlab : 3.5.1
global-tunnel-ng : 2.5.3
http-errors : 1.6.3
node-cache : 4.2.0
verdaccio : 3.6.0

Tags
Implementation
License
Platform

   




Related Projects

sinopia - Private npm repository server

  •    Javascript

It allows you to have a local npm registry with zero configuration. You don't have to install and replicate an entire CouchDB database. Sinopia keeps its own small database and, if a package doesn't exist there, it asks npmjs.org for it keeping only those packages you use. Use private packages.

codebox-npm - Serverless private npm registry using https://serverless.com/

  •    Javascript

Codebox npm is a serverless npm registry to allow companies that wish to keep their intellectual property. It allows sharing of npm modules within a company but additionally allows access to all of the modules on public npm. One other major difference is that it replaces npm login authentication to be via github / github enterprise. Users are always required to be authenticated when using codebox as their npm registry. It is currently compatible with the latest version of the npm & yarn cli.

npm-register - Your own private npm registry and backup server

  •    Javascript

Your own private npm registry and backup server. Designed to be easy to set up and maintain, performant, and stable. This project allows you to have your own npm registry. This server works with the necessary npm commands just like the npmjs.org registry. You can use it to not worry about npm going down or to store your private packages. It performs much faster than npmjs.org and can even be matched with a CDN like Cloudfront to be fast globally.

registry-issue-archive - An archive of the old npm registry issue tracker

  •    

This is an arrchive of the old issue tracker for the npm registry and only exists for historical purposes. Registry documentation lives has not moved and continues to live in the github.com/npm/registry repository.


npmhub - :mag_right: A browser extension for exploring npm dependencies on GitHub repos

  •    Javascript

npmhub is a browser extension that lets you explore npm dependencies on GitHub and GitLab repos. When viewing a repository's file list containing a package.json, this extension will display links and descriptions for each dependency at the bottom of the page. GitHub Enterprise, GitLab Enterprise and Community Edition are also supported by authorizing your own domain in the options.

package-quality - Measurements of quality for packages, especially for npm

  •    Javascript

Measurements of quality for packages, initially for npm.replacing yourpackage with (surprise!) the name of your package. You can choose between badge or mini-badge; the latter is courtesy of shields.io.

node-reggie - An experimental light weight alternative to a full blown npm registry

  •    Javascript

Reggie is an experimental light weight alternative to a full blown npm registry. Also, there aren't any tests yet. I know, I know, but this is an experiment... bear with me.

wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!

  •    Rust

This tool seeks to be a one-stop shop for building and working with rust- generated WebAssembly that you would like to interop with JavaScript, in the browser or with Node.js. wasm-pack helps you build and publish rust-generated WebAssembly to the npm registry to be used alongside any other javascript package in workflows that you already use, such as webpack or greenkeeper. We generate a wasm-pack.log file if wasm-pack errors on you, and you can customize the log verbosity using the verbosity flag.

npmgraph.an - 2d visualization of npm

  •    Javascript

Visualization of npm shows dependency graph of an npm package. Note, due to https://github.com/anvaka/npmgraph.an/issues/1 the website talks with npm registry through heroku-hosted proxy. This may have negative impact on latency.

gitlab-shell - Replacement for gitolite

  •    Ruby

GitLab Shell handles git commands for GitLab and modifies the list of authorized keys. GitLab Shell is not a Unix shell nor a replacement for Bash or Zsh. Maybe you wonder why in the case of git push over http(s) the Rails app doesn't handle authentication before delegating to GitLab Shell. This is because GitLab Rails doesn't have the logic to interpret git push commands. The idea is to have these interpretation code in only one place and this is GitLab Shell so we can reuse it for ssh access. Actually GitLab Shell executes all git push commands without checking authorizations and relies on the pre-receive hooks to check authorizations. When you do a git pull command the authorizations are checked before executing the commands (either in GitLab Rails or GitLab Shell with an API call to GitLab Rails). The authorization checks for git pull are much simpler since you only have to check if a user can access the repo (no need to check branch permissions).

gitlab-mirrors - A set of scripts adding the ability of managing remote mirrors to GitLab.

  •    Shell

The gitlab-mirrors project is designed to fill in a feature which is currently missing from GitLab: the ability to mirror remote repositories. gitlab-mirrors creates read only copies of remote repositories in gitlab. It provides a CLI management interface for managing the mirrored repositories (e.g. add, delete, update) so that an admin may regularly update all mirrors using crontab. It operates by interacting with the GitLab API using python-gitlab. Note: if you are upgrading then see docs/upgrade for notes on upgrading.

go-gitlab - A GitLab API client enabling Go programs to interact with GitLab in a simple and uniform way

  •    Go

Release v0.6.0 (released on 25-08-2017) no longer supports the older V3 Gitlab API. If you need V3 support, please use the f-api-v3 branch. This release contains some backwards incompatible changes that were needed to fully support the V4 Gitlab API. For complete usage of go-gitlab, see the full package docs.

gitlab-ci-multi-runner - This repository is a mirror for automated DockerHub builds. Please go to:

  •    Go

This is the repository of the official GitLab Runner written in Go. It runs tests and sends the results to GitLab. GitLab CI is the open-source continuous integration service included with GitLab that coordinates the testing. The old name of this project was GitLab CI Multi Runner but please use "GitLab Runner" (without CI) from now on. Contributions are welcome, see CONTRIBUTING.md for more details.

docker-gitlab - Dockerized GitLab

  •    Shell

Dockerfile to build a GitLab image for the Docker opensource container platform. GitLab CE is set up in the Docker image using the install from source method as documented in the the official GitLab documentation.

vim - My Vim configuration more Python, Javascript, Vue

  •    Vim

You can use Docker to try it. Or use the GitLab registry, where the image is automatically built weekly and all dependent packages are updated.

npmrc - Switch between different .npmrc files with ease and grace.

  •    Javascript

Switch between different .npmrc files with ease and grace. If you use a private npm registry, you know the pain of switching between a bunch of different .npmrc files and manually managing symlinks. Let that be a problem no more! npmrc is here to save the day, by making it dead simple to switch out your .npmrc with a specific named version. It also tries to protect you from your own stupid self by making sure you don't accidentally overwrite an .npmrc that you actually want to keep.

gitlab-plugin - A Jenkins plugin for interfacing with GitLab

  •    Java

This plugin allows GitLab to trigger builds in Jenkins when code is committed or merge requests are opened/updated. It can also send build status back to GitLab. Most of the current maintainers of the plugin are no longer using GitLab on a daily basis, and therefore have less time to contribute to it. If you are a regular user and would like to help out, please consider volunteering as a maintainer. There are verified bugs that need fixes, open PRs that need review, and feature requests that range from simple to complex. If you are interested in contributing, contact Owen (email address in git log) for additional access.