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-images

v0.3.0

Published

CLI tool to convert a gitlab repository to a gitlab docker image registry

Downloads

4

Readme

gitlab-images

gitlab-images is in alpha. Expect breaking changes, crashes and big explosions. Use under your responsability 😇

CLI tool to convert a gitlab repository to a managed gitlab docker image registry

Tested only with a custom gitlab instance, don't know if it works with gitlab.org

Installation

To install it, you will need to have already configured:

When you have your gitlab + runner + container registry, you can continue

  • Install the tool npm i -g gitlab-images
  • Create a new repository in your gitlab instance
    • For the examples I will use a repository at gitlab.mydomain.com/devops/images and a docker registry at registry.mydomain.com
  • git clone ssh://[email protected]/devops/images.git
  • cd images
  • gitlab-images install
    • The installation wizard should be self explanatory, just fill the questions
    • To see an example of the command, go to "gitlab-images install example output" section
    • IMPORTANT follow the message at the end of the installation!
  • Now you have your gitlab-images repo installed

When you push the changes, your runner should start a pipeline with 2 jobs: - 🛠️ docker-builder - 🏷️ docker-builder CI_SHA > production

Jobs with the emoji 🛠️ are builds, and with 🏷️ tagging jobs.

At this point, your repository is initialized with gitlab-images

Creating new images

README WIP

gitlab-images new <folder name>

Push your changes

gitlab-images install example output

Note: Markdown cannot show colors, so to see them you will need to install it 🙃

fox@foxdev:~/git/devops/lab$ gitlab-images install
Debugger attached.
gitlab-images v0.2.0
Wellcome to the installation wizard🧙 for gitlab-images

Target path '/home/fox/git/devops/lab'

? Is this the path where you want to install gitlab-images? Yes

No 'gitlab-images.config.yml' found. Assuming new installation

? Your gitlab registry (ex: registry.your-gitlab.com) registry.mydomain.com
? Where will be the images located? (ex: /devops/images) /devops/images

This configuration will be used to execute command
? Is 'registry.mydomain.com/devops/images' correct? Yes

-=Docker builder image=-

The docker builder meta image is the image that will be used to build your images
You can modify whatever you want in it, add debugging tooling for your docker images etc

? Coma separated list of tags for the runners that will build images exec:docker,service:docker-builder

  - exec:docker
  - service:docker-builder

? Are this tags correct? Yes
No README.md found. A new one will be created

-=Installation=-
We are going to make modifications inside the path

/home/fox/git/devops/lab

Its recommended first to have a repository initialized, so you can diff the changes, or revert if the tool brokes something

? Install? Yes
EXEC> mkdir .devops
EXEC> cp $TEMPLATES/install/.devops/gitlab-images.hbs.yml > ~Hydrate~ > .devops/gitlab-images.yml
EXEC> cp $TEMPLATES/install/.gitignore > .gitignore
EXEC> mkdir docker-builder
EXEC> cp $TEMPLATES/install/docker-builder/.config.yml > docker-builder/.config.yml
EXEC> cp $TEMPLATES/install/docker-builder/Dockerfile > docker-builder/Dockerfile
EXEC> cp $TEMPLATES/install/docker-builder/gitlab-images-0.2.0.tgz > docker-builder/gitlab-images-0.2.0.tgz
EXEC> cp $TEMPLATES/install/gitlab-images.config.hbs.yml > ~Hydrate~ > gitlab-images.config.yml
EXEC> cp $TEMPLATES/install/README.hbs.md > ~Hydrate~ > README.md

-=gitlab-images installed!=-
If is the first time installing gitlab-images (aka is not an update) follow this!
Before pushing the changes, the first docker-builder image must be manually created

Please run:
$  docker login registry.mydomain.com
$  gitlab-images docker build docker-builder
   - Select "production" tag
   - Push to registry: yes

To initialize the first docker-builder image

When you are done, you can commit and push the changes:
$  git add --all
$  git commit -m "Initialized gitlab-images"
$  git push

Installation done! 🚀