How is this different from how compose worked years back? #607

Closed
opened 2026-03-07 21:20:21 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @pentago on GitHub (Apr 9, 2020).

How is this different from how compose worked years back?

Originally created by @pentago on GitHub (Apr 9, 2020). How is this different from how compose worked years back?
Author
Owner

@glours commented on GitHub (Apr 10, 2020):

There's no differences 😉
This repository is a collection of ready to use samples with different kind of technologies

@glours commented on GitHub (Apr 10, 2020): There's no differences 😉 This repository is a collection of ready to use samples with different kind of technologies
Author
Owner

@pentago commented on GitHub (Apr 10, 2020):

Its kind of pathetic that its made just now.
Why not 5 years ago? Regardless of the answer nobody serious and in sane mind will use docker compose in production nowadays over Kubernetes Yamls, Kustomize, J/ksonnet.

I dont get this move a slightest bit but okay for those just starting.

@pentago commented on GitHub (Apr 10, 2020): Its kind of pathetic that its made just now. Why not 5 years ago? Regardless of the answer nobody serious and in sane mind will use docker compose in production nowadays over Kubernetes Yamls, Kustomize, J/ksonnet. I dont get this move a slightest bit but okay for those just starting.
Author
Owner

@glours commented on GitHub (Apr 10, 2020):

"but okay for those just starting"

This repo is exactly for those starting with docker-compose

The compose specification has been open sourced this week, let's see what can happen

@glours commented on GitHub (Apr 10, 2020): > "but okay for those just starting" This repo is exactly for those starting with docker-compose [The compose specification](https://compose-spec.io/) has been open sourced this week, let's see what can happen
Author
Owner

@OneCricketeer commented on GitHub (May 3, 2020):

fwiw, I agree with sentiment that Fig/Compose should have taken off a lot more than "just recently"

Regardless of the answer nobody serious and in sane mind will use docker compose in production nowadays over Kubernetes Yamls, Kustomize, J/ksonnet

  1. I suggest you look at https://kelda.io
  2. Given that the spec is open sourced and becoming standardized, it opens up the market for people to parse Compose object models into other schedulers (not only k8s). For example, Kompose does exactly that
@OneCricketeer commented on GitHub (May 3, 2020): fwiw, I agree with sentiment that Fig/Compose should have taken off a lot more than "just recently" > Regardless of the answer nobody serious and in sane mind will use docker compose in production nowadays over Kubernetes Yamls, Kustomize, J/ksonnet 1. I suggest you look at https://kelda.io 2. Given that the spec is open sourced and becoming standardized, it opens up the market for people to parse Compose object models into other schedulers (not only k8s). For example, Kompose does exactly that
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#607