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

@sapphirecode/dcm

v1.2.4

Published

Managing docker compose configurations, volumes and networks

Downloads

243

Readme

Docker-Compose Management

Version: 1.2.0

Open docker-compose management cli

Setup

Installation: npm i -g @sapphirecode/dcm

Each service has its own folder under services/ all necessary docker-compose files and configs should be stored there.

Docker-compose files have to be named docker-compose.yml and be at the top level of each individual service folder.

In dependencies.json all dependencies of a service can be defined. The start and stop order of services is determined by the dependencies.

The file passive.json can be used to deactivate services, those will not be started automatically, but they can be started manually by running docker-compose up -d in the service's folder or by including the flag --include-passive when using the cli.

Networks can be defined in networks.json. Available options are internal to set docker's network internal flag and subnet to define a specific subnet for a network. With interface_name you can specify the interface name for the network.

Volume settings are placed in volumes.json. By default all volumes in this file are added to the backup filter. To prevent them from getting backed up, set the option backup to false. Additionally single folders can be excluded from the backup using the backup_exclude option. Instead of backing up the whole volume, you can use backup_include to include only specific folders.

Commands

Global Options:

  • --delay=<seconds>: Delay before executing the command
  1. Pulling images: pull

This command simply pulls all images and exits.

  1. Starting services: up

This command starts all services in the correct order and creates the necessary networks and volumes if they don't already exist. Available options are: --pull to pull images before starting the services and --include-passive to include passive services.

  1. Stopping services: down

Stops all services including the passive ones.

  1. Restarting services: restart

Restarts all services, has the same effect as running down and up separately.

  1. Creating a backup filter: create_filter

Creates a filter file for rsync to create a backup of all configured volumes.