forked from coop-cloud/docs.coopcloud.tech
explain further the CLI weirdness & shorten title
This commit is contained in:
parent
f8e63b2ab2
commit
21e5c9d0f2
|
@ -68,11 +68,29 @@ docker context create <domain> --docker "host=ssh://<user>@<domain>:<port>"
|
|||
|
||||
Unfortunately, there is a limitation in our underlying command-line library implementation for `abra` ([ref](https://github.com/urfave/cli/issues/1113)) (and more fundamentally in the design of flags in the Go programming language itself ([ref](https://utcc.utoronto.ca/~cks/space/blog/programming/GoFlagUIImportance))). We're aiming to work with upstream to resolve the flag handling but this it is not yet clear when this will be resolved.
|
||||
|
||||
## Why can't `abra` support multiline definitions in the `.env` files?
|
||||
Currently, the following example of flexible flag usage is supported:
|
||||
|
||||
```
|
||||
abra app new gitea -S # generate secrets, after args
|
||||
abra app new -S gitea # generate secrets, before args
|
||||
```
|
||||
|
||||
But something like the following does not work as expected:
|
||||
|
||||
```
|
||||
abra app new -S gitea -p
|
||||
```
|
||||
|
||||
Where the position of flags is mixed before & after args. `-p` is ignored :cry:
|
||||
|
||||
We're still waiting for upstream patch which resovles this.
|
||||
|
||||
## Why can't `abra` support multiline in `.env` files?
|
||||
|
||||
We're sorry, it's an issue with an upstream dependency. See [`#291`](https://git.coopcloud.tech/coop-cloud/organising/issues/291) for more.
|
||||
|
||||
## I need some feature from the old depreciated bash abra?
|
||||
|
||||
There is an archive of the [old code here](https://git.coopcloud.tech/coop-cloud/abra-bash).
|
||||
|
||||
You can install it alongside the [supported version of Abra](https://git.coopcloud.tech/coop-cloud/abra) by using these commands:
|
||||
|
|
Loading…
Reference in New Issue