Omnibus build scripts
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
config
files
package-scripts/apitools-monitor
.gitignore
.kitchen.yml
.travis.yml
Berksfile
Berksfile.lock
CONTRIBUTING.md
Gemfile
Gemfile.lock
LICENSE.txt
Makefile
README.md
Rakefile
Vagrantfile
omnibus.rb
packaging_and_repo.md

README.md

apitools-monitor Omnibus project

This project creates full-stack platform-specific packages for apitools-monitor!

Installation

You must have a sane Ruby 1.9+ environment with Bundler installed. Ensure all the required gems are installed:

$ bundle install --binstubs

Usage

Build

You create a platform-specific package using the build project command:

$ bin/omnibus build apitools-monitor

The platform/architecture type of the package created will match the platform where the build project command is invoked. For example, running this command on a MacBook Pro will generate a Mac OS X package. After the build completes packages will be available in the pkg/ folder.

Clean

You can clean up all temporary files generated during the build process with the clean command:

$ bin/omnibus clean apitools-monitor

Adding the --purge purge option removes ALL files generated during the build including the project install directory (/opt/apitools-monitor) and the package cache directory (/var/cache/omnibus/pkg):

$ bin/omnibus clean apitools-monitor --purge

Help

Full help for the Omnibus command line interface can be accessed with the help command:

$ bin/omnibus help

Kitchen-based Build Environment

Every Omnibus project ships will a project-specific Berksfile that will allow you to build your omnibus projects on all of the projects listed in the .kitchen.yml. You can add/remove additional platforms as needed by changing the list found in the .kitchen.yml platforms YAML stanza.

This build environment is designed to get you up-and-running quickly. However, there is nothing that restricts you to building on other platforms. Simply use the omnibus cookbook to setup your desired platform and execute the build steps listed above.

The default build environment requires Test Kitchen and VirtualBox for local development. Test Kitchen also exposes the ability to provision instances using various cloud providers like AWS, DigitalOcean, or OpenStack. For more information, please see the Test Kitchen documentation.

Once you have tweaked your .kitchen.yml (or .kitchen.local.yml) to your liking, you can bring up an individual build environment using the kitchen command.

$ bin/kitchen create ubuntu-12.04
$ bin/kitchen converge ubuntu-12.04

Then login to the instance and build the project as described in the Usage section:

$ bundle exec kitchen login ubuntu-12.04
[vagrant@ubuntu...] $ cd ~/apitools-monitor
[vagrant@ubuntu...] $ bundle install
[vagrant@ubuntu...] $ ...
[vagrant@ubuntu...] $ sudo chmod -R a+rwx /opt
[vagrant@ubuntu...] $ bundle exec bin/omnibus build apitools-monitor
[vagrant@ubuntu...] $ ...
[vagrant@ubuntu...] $ exit
$ cd pkg
$ gem install package_cloud
$ package_cloud push APItools/monitor <your deb or rpm>

For a complete list of all commands and platforms, run kitchen list or kitchen help.