read answers from /dev/tty: under curl ... | bash stdin is the
script itself, so read consumed the script's own lines; fall back
to defaults when there is no terminal
check that docker, the compose plugin and the daemon work and that
compose accepts the generated compose.yaml
start liqa with docker compose up -d in the install directory,
printing the manual start command if a check or the start fails
- read answers from /dev/tty: under `curl ... | bash` stdin is the
script itself, so `read` consumed the script's own lines; fall back
to defaults when there is no terminal
- check that docker, the compose plugin and the daemon work and that
compose accepts the generated compose.yaml
- start liqa with `docker compose up -d` in the install directory,
printing the manual start command if a check or the start fails
- read answers from /dev/tty: under `curl ... | bash` stdin is the
script itself, so `read` consumed the script's own lines; fall back
to defaults when there is no terminal
- check that docker, the compose plugin and the daemon work and that
compose accepts the generated compose.yaml
- start liqa with `docker compose up -d` in the install directory,
printing the manual start command if a check or the start fails
ars9
merged commit 1abd95f9e1 into master2026-10-02 15:53:43 +03:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
curl ... | bashstdin is thescript itself, so
readconsumed the script's own lines; fall backto defaults when there is no terminal
compose accepts the generated compose.yaml
docker compose up -din the install directory,printing the manual start command if a check or the start fails