10
edits
Julianharty (talk | contribs) (Added first draft of instructions for using zimwriterfs) |
Julianharty (talk | contribs) (→Preparations: added tip on creating a shared folder.) |
||
Line 7: | Line 7: | ||
# Would you like to use the classic ZIM file internal structures? e.g. <code>./-/</code> for CSS and <code>./A/</code> for articles (in HTML format), etc.? If so, there's no need to use the <code>--uniqueNamespace</code> command-line option. Otherwise please use it. | # Would you like to use the classic ZIM file internal structures? e.g. <code>./-/</code> for CSS and <code>./A/</code> for articles (in HTML format), etc.? If so, there's no need to use the <code>--uniqueNamespace</code> command-line option. Otherwise please use it. | ||
# Have you identified your welcome page and got a suitable icon? | # Have you identified your welcome page and got a suitable icon? | ||
# Have you created a shared location available to the running Docker image to make the content easier to access by zimwriterfs? | # Have you created a shared location available to the running Docker image to make the content easier to access by zimwriterfs?[1] | ||
# Would you like to distribute to a large base of users who may use a variety of machines and storage options? If so, it will be important to split the ZIM file into no more than 2GB chunks. | # Would you like to distribute to a large base of users who may use a variety of machines and storage options? If so, it will be important to split the ZIM file into no more than 2GB chunks. | ||
[1] I added a shared folder so I could easily share data between the running Docker image and my macbook. This had to be configured using the command line. See https://github.com/rocker-org/rocker/wiki/Sharing-files-with-host-machine for tips on how to do this. | |||
<code> | <code> |
edits