version: '3.9'

services:
  onedev:
    hostname: "onedev-{{.Task.Slot}}"
    image: 1dev/server:6.3.10
    deploy:
      mode: replicated
      replicas: 1
      update_config:
        parallelism: 1
        order: stop-first
    volumes:
      - type: bind
        source: /var/run/docker.sock
        target: /var/run/docker.sock
      - type: volume
        source: onedev
        target: /opt/onedev
    networks:
      - dev
    # make sure linux sends tcp keep alive in case of long idle connections
    sysctls:
      - net.ipv4.tcp_keepalive_time=600
      - net.ipv4.tcp_keepalive_intvl=30
      - net.ipv4.tcp_keepalive_probes=10
    ports:
      - target: 6610
        published: 6610
        protocol: tcp
        mode: ingress
      - target: 6611
        published: 6611
        protocol: tcp
        mode: ingress
        
  onedev-agent:
    hostname: "onedev-agent-{{.Task.Slot}}"
    image: 1dev/agent:latest
    deploy:
      mode: replicated
      replicas: 3
      update_config:
        parallelism: 1
        order: stop-first
    # make sure linux sends tcp keep alive in case of long idle connections
    sysctls:
      - net.ipv4.tcp_keepalive_time=600
      - net.ipv4.tcp_keepalive_intvl=30
      - net.ipv4.tcp_keepalive_probes=10
    environment:
      serverUrl: http://onedev:6610/
      # Same Token for all replicas of the agent. Only one of three agents will work.
      agentToken: xxxxxxx-xxxxxx-xxxxx-xxxxxxx
      # Better security, but image needs to support it
      agentToken_file: /run/secrets/agenttoken
      # Unique Token per agent replica could be achieved using docker template. Requires custom tokens in OneDev server.
      agentToken: "xxxx-xxxx-xxx-xxx-{{ .Task.Slot }}"
      agentToken: "onedev-agent-{{ .Task.Slot }}"  # token mimics hostname
      agentToken_file: "/run/secrets/agenttoken-{{ .Task.Slot }}"
    volumes:
      - type: bind
        source: /var/run/docker.sock
        target: /var/run/docker.sock
      - type: volume
        source: onedev-agent
        # Because we have a NFS volume here, all agents work in the same directory. Might be better to use /agent/work/<hostname>. Agent needs to create that folder.
        target: /agent/work
    networks:
      - dev
 
volumes:
  onedev:
    driver_opts:
      type: "nfs"
      o: "addr=10.10.10.10,nolock,soft,rw,nfsvers=4,sync"
      device: ":/dev/onedev"
  onedev-agent:
    driver_opts:
      type: "nfs"
      o: "addr=10.10.10.10,nolock,soft,rw,nfsvers=4,sync"
      device: ":/dev/onedev-agent"