docker-microservices-gradle-plugin

KO | EN

gitlite — search

#javascript #python #ai #typescript #llm #go #golang #android #machine-learning #java #kubernetes #security #pytorch #openai

docker-microservices-gradle-plugin

(★ 8)

A gradle plugin that helps running microservices on docker containers

docker-microservices-gradle-plugin 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# docker-microservices-gradle-plugin

[![Build Status](https://travis-ci.org/michalborek/docker-microservices-gradle-plugin.svg?branch=master)](https://travis-ci.org/michalborek/docker-microservices-gradle-plugin.svg?branch=master) [![Coverage Status](https://coveralls.io/repos/michalborek/docker-microservices-gradle-plugin/badge.svg?branch=master)](https://coveralls.io/r/michalborek/docker-microservices-gradle-plugin?branch=master)

To see how to apply a plugin in your build.gradle [visit plugin page on Gradle Plugins site](https://plugins.gradle.org/plugin/pl.greenpath.gradle.docker.microservices).

This Gradle plugin allows to start many docker containers at once in specified order. Started dockers are linked 
together so they can communicate directly.

This plugin uses `docker` command (not a REST API). But in future releases it may change.

We created it because it was hard for us to start many microservices in development environment when using Spring Boot. 
This plugin was created for our convenience but we are open to any ideas that would make it useful for others.

To configure the plugin, use the `docker` extension block:

docker {
      // port to be published to host (mandatory)
      port 8080

// linked microservices, that should be dockerRun'ed and linked together with this one
      linkedMicroservices 'auth', 'orders', 'accounts'

// name of the container (default: project.name with '/' replaced with '-')
      containerName 'microservice'

// name of the image (default: project.name with '/' replaced with '-')
      imageName 'microservice'

// extra arguments passed on the command line to docker run
      runExtraArgs '-v', '/host:/inside_docker'

// run the container in background (default: true)
      runDetached true
      
      // when set to false dockerfile won't be generated (default: true)
      generateDockerfile false

// define dockerfile manually. The drawback of this solution is that order of execution 
      // of these commands is not preserved.
      dockerfile {
        from ubuntu:14.04
        expose 8080
        expose 9090
        env 'NAME', 'value'
        copy 'source', 'destination'
        workdir '/path/to/workdir'
        volume  '/var/volume'
        user 'deamon'
        add 'some.jar', 'test.jar'
        cmd java "java -jar test.jar"
      }
      
      // use microservice template
      dockerfile microserviceTemplate

// or you can mix these two approches
      dockerfile {
        template microserviceTemplate
        env 'name', 'value'
        ...
      }
      
      // instead of defining such a custom generation you can also define string based Dockerfile
      // The advantage of this solution compared to copying pure Dockerfile is that you can define 
      // own parameters.
      dockerfile """
         FROM java:8
         EXPOSE 9012
         CMD java -jar ${project.file}-${project.version}.jar
      """
      
    }
**Notice:** You should not mix closure/template based dockerfile declaration with string based.
In such a case the string definition will always be taken.

The microserviceTemplate shown above generates dockerfile that works well with default 
Spring Boot configuration, that is:

FROM java:8
    EXPOSE port # by default docker.port attribute
    ADD jarFile '.'
    CMD java -jar $jarFile

where `jarFile` is a name generated as `projectName.projectVersion.jar`.

**Hint:** If you want to be dependant on all other projects (e.g. you have a web UI microservice that 
is dependent on any other. as `linkedMicroservices` value you can set:

rootProject.getSubprojects().findAll { it.name != project.name }.collect {it.name}

**Note:** In current plugin implementation you need to copy this jar to `build/docker/` but we have it on to do list.

Feel free to post feature requests and bugs using GitHub.

Hot swap functionality (Experimental)
-------------------------------------

To enable hot swap you need to add springloaded package to buildscript classpath:

buildscript {
      repositories {
        mavenCentral()
      }
      dependencies {
        classpath('org.springframework:springloaded:1.2.5.RELEASE')
      }
    }

and enable hot swap:

docker {
      dev {
        enableHotSwap true
        imageName 'imageName:version' // 'java:8' is default image name for hot swap runs
      }
    }

Having done it you need to invoke **:dockerBootRun** task. 
Java classes will be automatically reloaded as well as static resources.
 
**Note:** In Intellij IDEA you need to enable auto-make of project or compile the class manually.

docker-microservices-gradle-plugin

docker-microservices-gradle-plugin 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

docker-microservices-gradle-plugin

docker-microservices-gradle-plugin 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README