Instiki has a mechanism for uploading wiki files. It seems that users are able to modify previously uploaded files.
The wiki files are stored on the file system, not in the database. Therefore, instiki2git currently does not back them up.
instiki2git should optionally support tracking the wiki files in the git repository. This would include the following:
- The command-line interface gets an option
--instiki for the path of the Instiki installation.
- The command-line interface gets a boolean option
--track-files. This requires --instiki to be given.
- Every time instiki2git runs with
--track-files, it should update the directory files the repository with the files in <instiki path>/webs/<web name>/files. Using the already implemented operation for adding a file to the git object database, this can be done without copying if the file has not been modified since the last run.
- To keep things simple, there should be commits updating
files separate from the ones that update pages. For example, on every run, one could process the revisions, producing a commit if necessary, and then do the same for files.
Instiki has a mechanism for uploading wiki files. It seems that users are able to modify previously uploaded files.
The wiki files are stored on the file system, not in the database. Therefore, instiki2git currently does not back them up.
instiki2git should optionally support tracking the wiki files in the git repository. This would include the following:
--instikifor the path of the Instiki installation.--track-files. This requires--instikito be given.--track-files, it should update the directoryfilesthe repository with the files in<instiki path>/webs/<web name>/files. Using the already implemented operation for adding a file to the git object database, this can be done without copying if the file has not been modified since the last run.filesseparate from the ones that update pages. For example, on every run, one could process the revisions, producing a commit if necessary, and then do the same for files.