split out todo for webapp export config UI; close export todo!
This commit is contained in:
parent
d71c65ca0a
commit
abdff127f2
2 changed files with 12 additions and 10 deletions
|
@ -13,14 +13,5 @@ exported data.
|
|||
Would this be able to reuse the existing `storeKey` interface, or would
|
||||
there need to be a new interface in supported remotes?
|
||||
|
||||
--[[Joey]]
|
||||
> [[done]]! --[[Joey]]
|
||||
|
||||
Work is in progress. Todo list:
|
||||
|
||||
* Support configuring export in the assistant
|
||||
(when eg setting up a S3 special remote).
|
||||
|
||||
This is similar to the little-used preferreddir= preferred content
|
||||
setting and the "public" repository group. The assistant uses
|
||||
those for IA, which could be replaced with setting up an export
|
||||
tracking branch.
|
||||
|
|
11
doc/todo/webapp_export_remote_configuration_interface.mdwn
Normal file
11
doc/todo/webapp_export_remote_configuration_interface.mdwn
Normal file
|
@ -0,0 +1,11 @@
|
|||
Support configuring export remotes in the webapp
|
||||
|
||||
Remember the little-used preferreddir= preferred content
|
||||
setting and the "public" repository group. The webapp uses
|
||||
those for IA, which could be replaced with setting up an export
|
||||
tracking branch.
|
||||
|
||||
The UI for S3, WebDAV, directory special remote setup could also have a way
|
||||
to make it an export, and configure the directory to export. This would
|
||||
complicate the UI, so needs thought. --[[Joey]]
|
||||
|
Loading…
Reference in a new issue