summaryrefslogtreecommitdiff
path: root/doc/todo/wishlist__91__webapp__93____58___add_an_option_to_install__SSH_key_on_remote.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/wishlist__91__webapp__93____58___add_an_option_to_install__SSH_key_on_remote.mdwn')
-rw-r--r--doc/todo/wishlist__91__webapp__93____58___add_an_option_to_install__SSH_key_on_remote.mdwn9
1 files changed, 0 insertions, 9 deletions
diff --git a/doc/todo/wishlist__91__webapp__93____58___add_an_option_to_install__SSH_key_on_remote.mdwn b/doc/todo/wishlist__91__webapp__93____58___add_an_option_to_install__SSH_key_on_remote.mdwn
deleted file mode 100644
index fe32f7dd7..000000000
--- a/doc/todo/wishlist__91__webapp__93____58___add_an_option_to_install__SSH_key_on_remote.mdwn
+++ /dev/null
@@ -1,9 +0,0 @@
-When adding a Remote server through the webapp, it set-up a specific SSH key for later sync.
-
-However, when the remote has been set-up manually, then later gets the assistant thrown at it, there doesn't appear to be a way to create and deploy such a key. This option could be offered in, e.g., the settings of the repo in the webapp.
-
-> I feel this is out of scope for the assistant. If the user is able to
-> manually add a git remote at the command line, then they should be able
-> to configure ssh keys too. I don't want to complicate the assistant with
-> a lot of code that tries to deal with half-configured things the user
-> manually set up. [[wontfix|done]] --[[Joey]]