https://github.com/bitmeal/nodegit-alpine

✨ a node:alpine based docker image, shipping precompiled nodegit versions 🚢
https://github.com/bitmeal/nodegit-alpine

alpine ci ci-cd cicd docker docker-container docker-image git node nodegit nodejs

Last synced: 2 days ago
JSON representation

✨ a node:alpine based docker image, shipping precompiled nodegit versions 🚢

• Host: GitHub
• URL: https://github.com/bitmeal/nodegit-alpine
• Owner: bitmeal
• Created: 2021-03-25T21:44:54.000Z (over 3 years ago)
• Default Branch: master
• Last Pushed: 2024-10-25T02:04:49.000Z (14 days ago)
• Last Synced: 2024-10-26T15:34:23.509Z (13 days ago)
• Topics: alpine, ci, ci-cd, cicd, docker, docker-container, docker-image, git, node, nodegit, nodejs
• Language: JavaScript
• Homepage: https://hub.docker.com/r/bitmeal/nodegit
• Size: 122 KB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# `nodegit:alpine`

A `node:alpine` based container with precompiled nodegit

```bash

docker pull bitmeal/nodegit:alpine

```

> view @ [Docker HUB](https://hub.docker.com/r/bitmeal/nodegit) 🚢

## important infos

How does it work?

* nodegit is installed globally in `/usr/local/lib/node_modules`

* the `npm` binary is masked from `/opt/linker/bin/npm` and `npm` calls are intercepted and evaluated

* the global nodegit version is *linked* (`npm link nodegit`), if a dependency on nodegit is detected (from `package.json` or directly)

**Visit docker hub page for configuration options!**

> ⚡ when debugging, remember that `npm` is masked and calls are intercepted

> 

> ⚡ to *install* (read: fetch as dependency) nodegit manually, call `npm link nodegit`

> 

> ⚡ to call `npm` directly, use `/usr/local/bin/npm`

>

> ⚠ **don't try to use this container to add a nodegit dependency to a project that did not depend on it beforehand! running `npm install nodegit` will not add it to your `package.json`!**

## why?

*Because nodegit is nice for automation!*

*Because nodegit in a container is **pain!***

*Because nodegit want's to be installed from source.*

## versions

Builds images for the latest *N* node.js versions and latest *M* nodegit versions (visit docker hub to find *N* and *M*). `lts-alpine` and `alpine` are referenced directly as base image, to avoid mismatches between official node images and these nodegit images.

Tags follow the official node image convention, introducing an additional leading versioning component. Images may be referenced as shown below.

`alpine`, as `current-alpine` is built against latest nodegit version only! To use a specific version of nodegit, you have to use a specific version of node.js as well. Omitting a version specification for nodegit will get you `latest`. 

*No versioning of alpine versions!* Nodejs and nodegit versioning only.

```

[-][-]alpine

```

* `alpine`, `current-alpine`, `latest-current-alpine`: latest nodegit version, based on `alpine`/`current-alpine`

* `lts-alpine`, `latest-lts-alpine`: latest nodegit version, based on `lts-alpine`

* `-lts-alpine`: specified nodegit version, based on `lts-alpine`

* `-alpine`, `-alpine`: latest nodegit version, based on respective node image (e.g. `14-alpine`/`fermium-alpine`)

* `--alpine`, `--alpine`: specified nodegit version, based on respective node image

* ⚡ **No explicit `latest` tag!** `node:latest` refers to a debian based image and breaks the naming convention

## platforms

* `linux/amd64`

* `linux/arm64`