Ed Morley 9df32fadee Use clearer file and directory names for build output
This makes it easier to differentiate between the archives for
dependencies and that of the final build output by bob when sifting
through `/tmp/`. The archive type is now also apparent when reading
the console output.

Before:
```
Building formula foo in /tmp/bobrmyuSG:
    ...
Archiving.
/tmp/tmp4JUwdj
Deploying.
...
```

After (when combined with #28):
```
Building formula foo in /tmp/bob-rmyuSG:
    ...
Archiving.
Created: /tmp/bob-build-tmp4JUwdj.tar.gz
Deploying.
...
```
2017-05-24 19:52:00 +01:00
2014-04-02 11:45:25 -04:00
2014-03-17 13:09:21 -04:00
2017-05-12 14:59:33 +01:00
2016-03-29 12:07:36 +02:00
2014-04-02 11:33:29 -04:00

Binary Build Toolkit

This repo exists as a framework for the compilation and deployment of binaries and libraries on Heroku.

It is inspired by (and extracted from) kennethreitz/python-versions.

Intended Design

  • Flexible type hierarchy
  • Flat dependency resolution
  • Version agnostic (careful curation and naming conventions preferred)
  • Import already-deployed sub-dependencies during a build (optionally fetch from UPSTREAM_S3_BUCKET)

Powered By

  • Bash, mostly
  • A litle bit of Python
  • Boto

Getting Started (Staging)

  • $ heroku create build-toolkit-python-staging --buildpack https://github.com/kennethreitz/conda-buildpack.git
  • $ heroku config:set AWS_ACCESS_KEY_ID=xxx AWS_SECRET_ACCESS_KEY=xxx S3_BUCKET=xxx

Now that your Heroku app for building is created, push a repo containing your formula to the app (e.g. the python buildpack repo).

$ heroku run bash
  $ bob build runtimes/python-2.7.6
  $ bob deploy runtimes/python-2.7.6


S
Description
No description provided
Readme 2.4 MiB
Languages
Python 95.3%
Shell 4.7%