From 9a126d18fd2c4132c35fdf4b13d22e88a7f10d93 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 4 Mar 2015 10:29:25 -0400 Subject: [PATCH] comment --- ...1_0dad4b86cda93dd5ca0c4fb049ff6d97._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/todo/Add_gitlab.com_as_cloud_provider/comment_1_0dad4b86cda93dd5ca0c4fb049ff6d97._comment diff --git a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_1_0dad4b86cda93dd5ca0c4fb049ff6d97._comment b/doc/todo/Add_gitlab.com_as_cloud_provider/comment_1_0dad4b86cda93dd5ca0c4fb049ff6d97._comment new file mode 100644 index 0000000000..ab80ad5ee3 --- /dev/null +++ b/doc/todo/Add_gitlab.com_as_cloud_provider/comment_1_0dad4b86cda93dd5ca0c4fb049ff6d97._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-03-04T14:23:05Z" + content=""" +This uses ssh, so the repository address can be pasted into the webapp +as a ssh server, and it should work already. + +It probably does make sense to add gitlab.com as a canned solution alongside +box.com and rsync.net in the webapp. + +Since the remote will be a full git repository, it should prompt the user +if they want to enable gcrypt to encrypt all the content client-side. + +If gitlab has a reasonable API for creating a new repository, the webapp +could optionally use that, instead of needing the user to create one +themselves. +"""]]