Bootstrapping a new server takes too many steps? #136
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#136
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?
Can become:
Where
create/c
will create a server, init it with swarm mode and install Docker on it for you. For the new VPS case. Andprovision/p
will init swarm mode and install Docker. For the existing server case.I'll also try and rope in automatic traefik deploy on server create/provision:
Then it'll just be, from scratch:
Went with just removing
server init
andserver create
->server new
to follow our other UI. I just need to implement the docker, swarm mode, traefik logic and then the UI/UX on this is feeling much better. I've added a similar interative question mode thing like inabra app new
so it is manageable with all the flags. Nearly there.Interface for this is now shaping up.