Sign inSign up

vshn/modulesync

By vshn

•Updated over 5 years ago

Align your repository configuration files. Plain simple.

Image
1

2.7K

vshn/modulesync repository overview

⁠ModuleSync

dockeri.co

Build Status GitHub issues GitHub PRs License

⁠Repository File Sync

Originally, a utility script to keep configuration files in sync for Puppet modules, ModuleSync⁠ allows you to keep files in sync across your many repositories on your Git servers. Pulls your repositories, applies and commits changes based on the file templates you prepare, and pushes the changes back to each repo. Support for creating GitHub PRs and GitLab MRs (since v2.0.0) in an automated fashion is included.

This Docker image runs ModuleSync with an unprivileged msync user in /app.

See Concierge⁠ if you want to sync multiple configurations from a single configuration repository.

⁠Supported Tags

  • latest size/layers based on
  • 2.0.0 size/layers based on
  • 1.3.0 size/layers based on
  • 1.2.0 size/layers based on
  • 1.1.0 size/layers based on
  • 1.0.0 size/layers based on
  • 0.10.0 size/layers based on
  • 0.9.0 size/layers based on

⁠Usage

In a GitLab CI configuration file:

  image: vshn/modulesync
  script:
    - msync update

In a Docker Compose file as a pseudo-service:

  modulesync:
    image: vshn/modulesync
    volumes:
      - .:/app

With Docker on the command line:

$ docker run --rm -v "$PWD":/app vshn/modulesync msync update

⁠Development

To add a new ModuleSync version tag:

  1. Add the version number to the update script⁠, and
  2. Run ./update.py and update the Docker build settings as indicated.

Please, run tox⁠ before contributing changes.

Tag summary

Content type

Image

Digest

Size

92.7 MB

Last updated

over 5 years ago

docker pull vshn/modulesync