#
# Catch-22 if put this in docker as we put the docker-compose.yml in git,
# same if we rebuild it from jenkins and put jenkins in docker,
# same if we put nginx in docker too.
# It might be that we need to not put those in docker even though they could.
# Or would this be solved if we just don't run docker-compose.yml by
# jenkins on git changes. Instead we have a docker-compose.yml just for
# those services (jenkins, gitbucket and possibly nginx) which is manually run?
# 


# Warning, none of this is tested yet or working


services-disabled:

  gitbucket:
    image: gitbucket/gitbucket:latest
    container_name: gitbucket
    # hostname: gitbucket.localdomain
    volumes:
      # Docker access
      # - /media/Data/GitBucketContainer:/gitbucket
      - /media/Data/Containers/GitBucket:/gitbucket
    restart: always
    ports:
      - "9093:8080"

  jenkins:
    image: jenkins/jenkins:lts
    container_name: jenkins
    # hostname: gitbucket.localdomain
    restart: always
    privileged: true
    user: root
    volumes:
      - /media/Data/Containers/Jenkins:/var/jenkins_home
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - "8080:8080"
      - "50000:50000"

   # jenkins-agent:
   #   image: jenkins/ssh-agent:jdk11
   #   privileged: true
   #   user: root
   #   container_name: agent
   #   expose:
   #     - 22
   #   environment:
   #     - JENKINS_AGENT_SSH_PUBKEY=ssh-rsa AAAAB3N

  nginx:
    image: nginx:1.16.0-alpine
    container_name: nginx
    # hostname: nginx.localdomain
    restart: always
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf:ro
    ports:
      - "8080:80"