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

moldock

v1.0.0-beta

Published

a cli tool to breakdown moleculer projects and dockerize them individually

Downloads

3

Readme

Moleculer logo

moldock (Moleculer Dockerized)

A CLI tool to deconstruct moleculer projects into their own dependant projects, to be able to dockerize them individually

☠ The Problem

Moleculer structures all it's services in a services folder as follows:

Project
├───services
│     ├───api.service.js
│     ├───greeter.service.js
│     └───otherService.service.js
├───etc

When you try to dockerize the services, it creates an image with all the dependencies of all the services and copies all the services in that image. So if you want the API service to be in it's individual container, everything for all the other services will be copied. Also you will have to create an individual docker-compose.yml

That causes a lot of manual work and a bloated docker image

🎉The Solution

moldock:

moleculer-dockerized or moldock for short takes the project and asks you what packages are needed for each service. It then creates a folder with all the services as their own projects with their corrosponding package.json, Dockerfile, docker-compose.yml, docker-compose.env

It creates a new directory one level up from where the project is and appends -moldock to the directory. This directory will contain all the destructured services in their respective folders. Each service folder will be a combination of the name of the project and the name of the service like so project-service

Project-moldock
├───Project-api
│     ├───services
│     │      └───api.service.js
│     ├───Dockerfile
│     ├───docker-compose.yml
│     ├───docker-compose.env
│     ├───package.json
│     └───etc
├───Project-greeter
│     ├───services
│     │      └───greeter.service.js
│     ├───Dockerfile
│     ├───docker-compose.yml
│     ├───docker-compose.env
│     ├───package.json
│     └───etc
├───Project-otherService
│     ├───services
│     │      └───otherService.service.js
│     ├───Dockerfile
│     ├───docker-compose.yml
│     ├───docker-compose.env
│     ├───package.json
│     └───etc
├───etc

🤷‍♂️Assumptions

  1. You don't want to copy these folders:

    • node_modules
    • test
    • tests
    • .vscode
    • data
    • db
    • .git
  2. You have a docker hub account

  3. You want to copy everything in the project to each service

  4. Your services are in a services folder named <service name>.service.js

🔻Installation

npm i -g moldock

🖥Usage

  1. Change directory to the moleculer project
  2. Run moldock --dockerUser <your docker user>
  3. Select the dependecies of each service
  4. Profit

🛣Roadmap

  • [ ] Auto infer required modules and select them by default
  • [ ] Add a flag to auto build docker image
  • [ ] Add a flag to auto push docker image
  • [ ] Remove --dockUser and auto capture it from system
  • [ ] Add an option for main folder append string
  • [ ] Use chalk and boxed to make it look pretty