comments

doc/todo/dockerized_external_special_remotes/comment_2_61a23adb5b871b178d3fb5a51602cf46._comment

@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2018-12-05T16:24:17Z"
+ content="""
+Couldn't the docker image come with its own copy of git-annex?
+Not super space efficient, but it ensures that the special remote has
+access to a version of git-annex with the features it needs.
+"""]]

doc/todo/dockerized_external_special_remotes/comment_3_a044848ea54aebc2196376f9a59ccc70._comment

@@ -0,0 +1,24 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2018-12-05T16:27:47Z"
+ content="""
+I think this could be a good idea, although I would not want to be forced
+to use docker as the only way to install an external special remote either.
+
+It seems that the minimum needed is a way to add a shell script to
+PATH with the name of the external special remote program, so git-annex can
+run it as usual. Or git-annex could invoke `docker run` itself, but I like
+having a shell script because it means git-annex doesn't need to know about
+docker and other containerization technologies.
+
+OTOH, I can see it would be nice if `git annex enableremote` could somehow
+get everything set up to use docker, and `git annex init` could fully set
+up autoenable=true special remotes.
+
+A balance could be for `git annex enableremote` to set up the shell script,
+perhaps in `.git/annex/externals/`. Store a few values like which docker
+image to use in the remote config, and generate the shell script from that.
+Then when a user needs to pass extra parameters to docker, or if they want
+to use rkt etc, they can just edit the shell script.
+"""]]