Handling Missing ~/.ssh Host entries can be improved #570
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#570
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?
When adding a new server via abra the process is not as user friendly as it can be #537. The requirement
1. a server with SSH access...
implies simply being able to runssh user@website.org
and be into a server. However, as the Docs mention later:This is not as clear as it can be (as it needs a specifically formatted
host
entry #566). When following the New Operators Tutorial for the second time, I made the mistake to not add an SSH entry which then threw the following stacktrace.This is a confusing UX. The first message written is
INFO[0000] successfully created...
the result is an empty folder and is added to the servers list. I see two viable things to slightly improve the UX for new Operator onboarding andabra
Step 1. Create SSH host entry
Oh yeh, totally agree 🤘 Great Report ™
decentral1se referenced this issue2024-03-27 06:18:36 +00:00