Builds deb packages for things not publicly available.
In short we should be installing any dependency via a package manager of some description, but some projects don't provide deb packages. This builds simple packages for those projects that we can host on an internal apt repository.
Installing via a package manager means that we:
- Get nice versioning and simplified installs via configuration management
- More predicatable instance creation, no download links are dead or codebases no longer compiling
- Less need for development tools and compilers on production instances
The project aims to create a vagrant VM for any common packaging requirements. These VM's should build any packages during the provisioning stage, i.e users should be able to run vagrant up <machine> && vagrant destroy <machine> and have all packages available within the root directory.
A tester vagrant machine is available as a clean image for testing package installs.
Packaging machines currently available:
- bosun
- postgres (builds a range of postgres extensions)
The upload.sh script should be used to push any updated packages to an S3 backed apt repository via deb-s3, which you'll need to install if it's not already. This script expects two environment variables to be set:
- BUCKET: The S3 bucket holding the apt repo
- GPG_KEY: The GPG key ID used for signing the repository manifests
If your package doesn't fit nicely into one of the existing vagrant machines then you'll need to create a new instance. Check the Vagrantfile for the current usage. Each new machine must have the hostname set so that it can be targetted via Salt, you'll need to add this targetting to salt/top.sls.
Assuming you have a build host available, any steps required to package the new dependency should be added to the salt formulas for that build host. These will likely include: downloading sources or binaries, setting up install directory structures and packaging those structures via fpm.