fig up should recreate multiple containers

[bfirsh]

If a service has multiple containers and fig up -d is run, it stops everything and starts one container for each service. This is not very helpful.

It should probably stop, recreate and start each container individually so you can do a rolling restart.

The behaviour of fig up when there are multiple containers running in the background needs a bit of thought. The whole daemon/up workflow needs thinking out properly. Maybe there should be a fig recreate command which handles the recreation of daemonised containers and fig up should just attach or something.

[marksteve]

How about a containers_count in fig.yml?

[bfirsh]

fig.yml is a definition of what types of service can run, not the "formation" in Heroku terminology.

Something that might make sense is a min_scale or initial_scale option or something like that.

[marksteve]

I see. Not really much of a PaaS user. I've been using fig to setup dev environments.

[dkerwin]

+1

[ekroymann]

+1 for initial_scale

[paulRbr]

The initial_scale option would make sense. The need to be able to describe nth time the same service as a minimum requirement for an application to run is very likely to happen.

[gastonmorixe]

👍