|
Size: 913
Comment: Adding TOC
|
Size: 2549
Comment: addin conclusion
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Automated Build of the gpg4win installer = | = Automated Build of the gpg4win installer |
| Line 3: | Line 3: |
| <<TableOfContents(3)>> | At the moment, you can best build ~Gpg4win on a Debian system using the list of build dependency packages. You have to setup a system, install those dependencies and follow [[https://wiki.gnupg.org/Gpg4win/build|the instructions]]. To simplify the process and give all users the possibility to compile a gpg4win Installer on their own, we want to provide an automated solution that simplifies the process for all stakeholders. It will be easier for the developers, because they don't have to maintain a list of system dependencies, they just have to add them to a script, they use by themselves. And it will be easier for the users, because they don't have to care about technical details that aren't important for the process or the product itself. |
| Line 5: | Line 5: |
| At the moment, you can only build gpg4win on a Debian system with special dependencies. You have to setup a system by your own, install those dependencies and follow [[https://wiki.gnupg.org/Gpg4win/build|the instructions]]. To simplify the process and give all users the possibility to compile a gpg4win Installer on their own, we want to provide an automated solution that simplifies the process for all steakholders. It will be easier for the developers, because they don't have to maintain a list of system dependencies, they just have to add them to a script, they use by themselves. And it will be easier for the users, because they don't have to care about technical details that aren't important for the process or the product itself. | == Evaluating possibilities |
| Line 7: | Line 7: |
| == Evaluating possibilities == | === Docker |
| Line 9: | Line 9: |
| === Docker === | There is a Dockerfile that automatically creates an installer, you can find it on [[https://bitbucket.org/jsaalfeld/gpg4win-docker|BitBucket]]. The Problem with Docker itself is, that we can't trust the origin of the base images that are used to create the containers. We could create [[https://github.com/phusion/baseimage-docker|our own base images]], but that again would require a lot of webspace and we have to additionally maintain a base image. |
| Line 11: | Line 11: |
| === Vagrant === | === Vagrant |
| Line 13: | Line 13: |
| === Self-Scripted=== | Vagrant works very similar to Docker. But Vagrant uses other virtualization providers to create an Image, so the user needs Vagrant on the one side and a virtualization Provider (like Virtualbox) on the other side. Vagrant is system independent. Like with Docker, you [[https://atlas.hashicorp.com/boxes/search|pull an Image from a server]], but different than Docker, you can check where the image is coming from and where it is hosted. Also, the Images in the Vagrant System are directly maintained by [[https://wiki.debian.org/Teams/Cloud/VagrantBaseBoxes|a Debian Team]]. So the trust in that image is bigger. Of course, you can also create your own box image, to have full trust in the build image. Furthermore, like with Docker, we could host our own Image, but it would have the same disadvantages. === Conclusion Docker is on the rise at the moment, but the technology is still "bleeding" edge and isn't fully system independent. Vagrant works much like Docker, but has many advantages, like the full system independency or that you can choose your virtualization provider. Furthermore the trust in base images is bigger and it is easy to build a base-box by yourself, to have a fully trusted build system. = Vagrant |
Automated Build of the gpg4win installer
At the moment, you can best build Gpg4win on a Debian system using the list of build dependency packages. You have to setup a system, install those dependencies and follow the instructions. To simplify the process and give all users the possibility to compile a gpg4win Installer on their own, we want to provide an automated solution that simplifies the process for all stakeholders. It will be easier for the developers, because they don't have to maintain a list of system dependencies, they just have to add them to a script, they use by themselves. And it will be easier for the users, because they don't have to care about technical details that aren't important for the process or the product itself.
Evaluating possibilities
Docker
There is a Dockerfile that automatically creates an installer, you can find it on BitBucket. The Problem with Docker itself is, that we can't trust the origin of the base images that are used to create the containers. We could create our own base images, but that again would require a lot of webspace and we have to additionally maintain a base image.
Vagrant
Vagrant works very similar to Docker. But Vagrant uses other virtualization providers to create an Image, so the user needs Vagrant on the one side and a virtualization Provider (like Virtualbox) on the other side. Vagrant is system independent. Like with Docker, you pull an Image from a server, but different than Docker, you can check where the image is coming from and where it is hosted. Also, the Images in the Vagrant System are directly maintained by a Debian Team. So the trust in that image is bigger. Of course, you can also create your own box image, to have full trust in the build image. Furthermore, like with Docker, we could host our own Image, but it would have the same disadvantages.
Conclusion
Docker is on the rise at the moment, but the technology is still "bleeding" edge and isn't fully system independent. Vagrant works much like Docker, but has many advantages, like the full system independency or that you can choose your virtualization provider. Furthermore the trust in base images is bigger and it is easy to build a base-box by yourself, to have a fully trusted build system.