Missing FOO server connection details when symlinking ~/.abra/servers/FOO #340
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#340
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?
If you follow https://docs.coopcloud.tech/operators/handbook/#sharing-abra then you suddenly get a lot of symlinked servers which
abra
can manage. But if you runabra server ls
, you have no connection details! You need toabra server add ...
for each server to complete the details.We can try to automate creating these connection details but sometimes there are different usernames/ports being used. We could try find these from the
~/.ssh/config
file but a lot of folks don't use that.It might be worth just erroring out then if we can't create a reliable context so that at least folks are not left thinking they have some obscure ssh problem but instead, just need to run
abra server add ...
.This is stopping more smooth onboarding of shared ~/.abra/...` set ups.
/cc @Frando related: #338 (comment)
decentral1se referenced this issue2022-08-09 13:45:42 +00:00
coop-cloud/abra#262 solves this for now.