Skip to content

Latest commit

 

History

History
84 lines (55 loc) · 3.36 KB

README.md

File metadata and controls

84 lines (55 loc) · 3.36 KB
Raw

An GIT-sync Docker image

Docker Stars Docker Pulls Docker Automated buil GitHub forks GitHub stars

Docker which periodically updates from a remote git location

Supported tags and respective Dockerfile links

This image is updated via pull requests to the martinvw/docker-git-sync GitHub repo.

What is this GIT-sync Docker image

It's just a docker which periodically updates from a remote git location

How to use the image (command line)

$ docker run --name git-sync -d -e GIT_SYNC_REPO="https://github.com/martinvw/resume.git" martinvw/git-sync

Using Docker-compose

Create the following docker-compose.yml and start the container with docker-compose up -d

version: "3"

services:
   gitsync:
      image: martinvw/git-sync
      restart: always
      environment:
        GIT_SYNC_REPO: ssh://git@gitlab:22/martinvw/resume.git
        GIT_SYNC_FORCE_ACCEPT_SSH_HOST_KEY: gitlab_web_1.nginx-proxy
        GIT_SYNC_FORCE_ACCEPT_SSH_PORT_KEY: 22_
       volumes:
         - 'website_sources:/git/Website:z'
         - './restricted_rsa.pub:/root/.ssh/id_rsa.pub'
         - './restricted_rsa:/root/.ssh/id_rsa'
       restart: always
   
   nginx:
      image: 'nginx:latest'
      depends_on:
       - gitsync
      volumes:
       - 'website_sources:/usr/share/nginx/html:ro'
      restart: always

volumes:
  website_sources:
    driver: local

networks:
  default:
    external:
      name: nginx-proxy

Used together with jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion.

Supported Docker versions

This image is officially supported on Docker version 1.13.1.

Support for older versions (down to 1.6) is provided on a best-effort basis.

User Feedback

Issues

If you have any problems with or questions about this image, please contact us through a GitHub issue.

Contributing

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Documentation

License

When not explicitly set, files are placed under License MIT