Difference between revisions of "Deployment"
Jump to navigation
Jump to search
| Line 69: | Line 69: | ||
For Windows, we have an installer which is not bad. This is a binary done with the help of NSIS. This bbinary is able to install kiwix and custom content. The installer is like a sophisticated copier, it just copy files from specific directories where the software and the content are to the target directory. The installer works on a portable version of Kiwix and you simply need to but the content you want in the "data" directory and this will be installed. To make it short, you do not need to rebuild an installer for each type of content. | For Windows, we have an installer which is not bad. This is a binary done with the help of NSIS. This bbinary is able to install kiwix and custom content. The installer is like a sophisticated copier, it just copy files from specific directories where the software and the content are to the target directory. The installer works on a portable version of Kiwix and you simply need to but the content you want in the "data" directory and this will be installed. To make it short, you do not need to rebuild an installer for each type of content. | ||
On Linux, the standard way to install a software is the package and I think this should not be different, that means that I don't think this would be a good idea to make a install script for a portable static compiled version of Kiwix. So, here the challenge is to start including kiwix in distro. package repository. That also means that the question is still open for the the content: how to install content on Linux? Maybe a script called kiwix-install-content would be useful? | |||
== Distribution approaches == | == Distribution approaches == | ||