Rename "server" subcommand to "swarm"? #49

New Issue

3wordchant · 2021-03-10T21:16:25Z

3wordchant commented

2021-03-10 21:16:25 +00:00

@kawaiipunk was suggesting swarm might be clearer than server, particularly in the context of "upgrade --all on the X".

It's a fair point that the server commands currently expect to start with a server init, which really init's a swarm rather than the server itself, server rm removes the Docker context not the actual VPS, server apps lists the swarm apps. So I think swarm is maybe more precise.

The advantage of server (and downside of swarm) seems to be that it's more familiar. I also wonder if swarm might suggest multiple server nodes to people, which is only not required for Co-op Cloud, but not tested yet.

@kawaiipunk was suggesting `swarm` might be clearer than `server`, particularly in the context of "upgrade `--all` on the X". It's a fair point that the `server` commands currently expect to start with a `server init`, which really init's a swarm rather than the server itself, `server rm` removes the Docker context not the actual VPS, `server apps` lists the swarm apps. So I think `swarm` is maybe more precise. The advantage of `server` (and downside of `swarm`) seems to be that it's more familiar. I also wonder if `swarm` might suggest multiple server nodes to people, which is only not required for Co-op Cloud, but not tested yet.

3wordchant added the

question

design

labels 2021-03-10 21:16:25 +00:00

3wordchant closed this issue

2021-03-10 21:17:38 +00:00

3wordchant commented

2021-03-10 21:17:55 +00:00

r/lostgiteausers