Rename "server" subcommand to "swarm"? #49
Labels
No Label
automation
bug
community organising
democracy
design
documentation
duplicate
enhancement
finance
funding
help wanted
invalid
publishing
question
security
wontfix
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#49
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@kawaiipunk was suggesting
swarm
might be clearer thanserver
, particularly in the context of "upgrade--all
on the X".It's a fair point that the
server
commands currently expect to start with aserver 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 thinkswarm
is maybe more precise.The advantage of
server
(and downside ofswarm
) seems to be that it's more familiar. I also wonder ifswarm
might suggest multiple server nodes to people, which is only not required for Co-op Cloud, but not tested yet.r/lostgiteausers
For me, the term
swarm
seems more appropriate but don't feel strongly.We're over in coop-cloud/abra#92, pardon my mistake.