abra server interface is confusing? #34

New Issue

decentral1se · 2021-08-02T18:53:17Z

decentral1se commented

2021-08-02 18:53:17 +00:00

I'm thinking that abra server new hetzner and abra server rm are confusing since new creates a server but rm deletes a local docker context? Also add vs. new is like, two vague terms that can be easily be confused and I literally never remember myself. ls/add/rm are all local only, new/init do something on a remote.

Anyone feeling the same? We can handle UI/UX after we reach feature parity I guess.

Guessing at alternatives:

abra server:
- list/ls: list all managed VPSs
- create/mk: create VPS (hetzner, capsul, etc.)
- remove/del/rm: delete VPS (hetzner, capsul, etc.)
- config/cfg: configure connection details for VPS (SSH username/port/etc.)
- provision/prv: install docker/swarm/networking on VPS

It looks like go-abra can do everything now so end-users won't even have to install Docker locally on their dev machines, they'll just need our binary! So, the "docker context" becomes something of an implementation detail and doesn't need to be directly handled? We just need SSH connection details now and we build the context connection string ourselves internally.

I'd like to merge add/new into a single create? If you want a new server, then you abra server create ... and if you have one already and just want to "register" it with go-abra then you abra server create --existing and then abra server config to adjust SSH details?

I'm thinking that `abra server new hetzner` and `abra server rm` are confusing since `new` creates a server but `rm` deletes a local docker context? Also `add` vs. `new` is like, two vague terms that can be easily be confused and I literally never remember myself. `ls`/`add`/`rm` are all local only, `new`/`init` do something on a remote. Anyone feeling the same? We can handle UI/UX after we reach feature parity I guess. Guessing at alternatives: - `abra server`: - `list`/`ls`: list all managed VPSs - `create`/`mk`: create VPS (hetzner, capsul, etc.) - `remove`/`del`/`rm`: delete VPS (hetzner, capsul, etc.) - `config`/`cfg`: configure connection details for VPS (SSH username/port/etc.) - `provision`/`prv`: install docker/swarm/networking on VPS It looks like `go-abra` can do everything now so end-users won't even have to install Docker locally on their dev machines, they'll just need our binary! So, the "docker context" becomes something of an implementation detail and doesn't need to be directly handled? We just need SSH connection details now and we build the context connection string ourselves internally. I'd like to merge `add`/`new` into a single `create`? If you want a new server, then you `abra server create ...` and if you have one already and just want to "register" it with `go-abra` then you `abra server create --existing` and then `abra server config` to adjust SSH details?

❤️ 1

decentral1se added the

question

label 2021-08-02 18:53:17 +00:00

decentral1se commented

2021-08-02 19:16:56 +00:00

Hmmm maybe add/new can't be merged? create --existing is quite gross actually.

Hmmm maybe `add`/`new` can't be merged? `create --existing` is quite gross actually.

👀 1

decentral1se referenced this issue

2021-08-02 19:33:10 +00:00

Bootstrapping a new server takes too many steps? #35