Skip to content

Latest commit

Β 

History

History
46 lines (30 loc) Β· 2.12 KB

HUB.md

File metadata and controls

46 lines (30 loc) Β· 2.12 KB

info

quickstart

🚒$ docker run bitmeal/nodegit:alpine

πŸ“„ Dockerfile

πŸ—ƒ bitmeal/nodegit-alpine@github

πŸ“Œtags: [<nodegit-version>-][<node-version>-]alpine

fixing those errors

πŸ‘β€πŸ—¨ match the containers and your requested (package.json/package-lock.json) nodegit versions

🚫 try ignoring (and rebuilding) your package-lock.json in the container

⚑ when debugging, remember: npm binary is masked - visit repo for more infos

options

  • NODEGIT_LINK_SILENT: disables output of npm interception and link process
  • NODEGIT_LINK_OFF: disables automatic nodegit linking
  • NODEGIT_LINK_ALWAYS: always link global nodegit, independently of detection result
  • NODEGIT_IGNORE_PACKAGE_LOCK: ignore package-lock.json when searching for nodegit dependency
  • NPM_LINK: append --link to npm install (and aliases) per default
  • NPM_NO_PACKAGE_LOCK: use npm with --no-package-lock option

overview

A precompiled nodegit version and some sugar 🍭 in a node:alpine container.

  • nodegit is installed as a global module
  • the global nodegit module will get linked automatically, when a nodegit dependency is detected
  • calls to npm are intercepted and evaluated for automatic linking
  • call npm directly as /usr/local/bin/npm
  • manually 'fetch' nodegit as a dependency npm npm install, npm link nodegit or /usr/local/bin/npm install --link

tags

builder

This list is updated automatically, for the latest build, in sync with the container images. The build badge tells wether all containers built successfully, or any failed. The build status per tag (-group) tells wether the tags are included in the last build. Previous versions may be available for tags with failed builds.

tags format: [<nodegit-version>-][<node-version>-]alpine