let abra app errors
show errors that docker stack ps --no-trunc does #339
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#339
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?
abra app ps/errors/logs
are already super helpful when debugging new recipes. The only time I break out of abra-flow is when some entrypoint/secret/config stuff is wrong, which mostly reveals by looking intodocker stack ps --no-trunc
. Not sure whats the difference toabra app ps
. It's not a very high priority thing for me, but could be useful!this would be a recent example me failing on go templating with onlyoffice :D
thanks for raising @yksflip! this is also the only time i'm breaking out of
abra
use and i'd like to fix that :) very close to not having the docker cli installed on my machine 🙃 need to figure out how to get that--no-trunc
output visible alright. perhaps showing both inps
anderrors
output...Converging on #501.