A modern programming language that makes developers happier.

kotlinlang

<@U092308M7> I saw those docs, but I need multiple docker images in multiple ci pipelines with some shared modules -- which could be a common setup for microservice infrastructure. Also, do you build and redeploy all the microservices for changes in any one of them or just each changed one seperately?

We are using nomad for cluster infra, so it handles versioning itself. I’m not devops guy (yet), so I’m afraid I can’t say how it all works right away :disappointed:

build and redeploy each one of them if the change is in a common module.

you really want to decouple the binary generation (docker image) from the deployment of that image also

but that is really not ktor oriented. once you get your docker image you should look at ci's docs

<@U7NQN5AQZ> Do you already have such a setup? I'm still trying to decide whether to go w/ ktor instead of Vert.x... and it partially depends on ease of deployment... I'm wondering how others are doing it.

ktor vs vertx should not change a thing when it comes to that part

im deploying ktor + dropwizard  to kubernetes with <http://distelli.com|distelli.com>

For comparison, you might want to ask in <#C0B8RC352|server>

<@U7NQN5AQZ> It *is* a *big* difference, since vertx has it's own deployment of microservices as verticles even w/o any orchestration like docker swarm... but since I'm on a docker swarm setup, I find it's a waste to have such a heavy thing... and ktor seems to be the only async server w/ coroutine support..

<@U7NQN5AQZ> Oh, <http://distelli.com|distelli.com> is another one of those automated deployers...? I guess I could try <#C0B8RC352|server>...

i use distelli as a basic CI, not the deployment part with kubernetes

<#C0B8RC352|server> would help indeed.

basically what i do with it is execute a bash script, which also was how i did it in my past with jenkins.

ktor tries to adhere to <https://12factor.net> as much as possible, and though some things are not there yet, we are trying to make it as devops friendly as we can. I have a list of like 40 items we need to support :scream:

<@U7NQN5AQZ> But how does your git repo and build scripts look?

no submodules,

one repo
```
- &lt;root&gt;
\ - kubernetes/&lt;manifests.yaml
  - Dockerfile
  - build.gradle
  - &lt;kotlin/java stuff&gt;
  - build.sh
```

build.sh
```
gradle build
docker build -t app:$COMMIT_HASH

docker push app:$COMMIT_HASH

# generate kubernetes manifest with good commit_hash 
kubectl apply -f kubernetes/&lt;manifest.yaml&gt;
```

<@U7NQN5AQZ> You have many microservices or just one?

<@U7NQN5AQZ> And one per idea project? Or many modules in one big project?

one per idea project although you could setup submodule to have only one project. that should not affect the way you do deployments though

Thanks for your help, I'll see what I can come up with.. :slightly_smiling_face: 