[](https://travis-ci.org/ImageIntelligence/blingtron)
[](https://badge.fury.io/py/blingtron)
**Welcome to Blingtron!**
> Assembles the upgraded [Blingtron 5000](http://www.wowhead.com/item=111821/blingtron-5000), a savage, yet generous, robot. While he will give out gifts to players once per day, he will also fight other Blingtron units to the death. (4 Hrs Cooldown)
Blingtron is a simple command line too (CLI) aimed at helping developers run their Image Intelligence projects.
## Installation
```
$ pip install blingtron
```
Projects that use Blingtron are expected to have a `bling.json` file at the root of the project directory structure. For an example of what a bling.json file might look like, checkout [bling.example.json](./bling.example.json).
* `name`: The name of your project
* `registry`: The username of your account for your image registry
* `run`: The command that's executed when a Docker container runs your image (remotely)
* `start`: The arguments passed into `docker run`(locally)
* `packer`: The location of your Packer configuration directory
* `packer_exec_path`: (optional) The absolute path to your Packer executable
* `env`: An object of custom environ variables you can pass into all `bling` commands
See [imageintelligence/skeleton-python](https://github.com/ImageIntelligence/skeleton-python) and [imageintelligence/skeleton-scala](https://github.com/ImageIntelligence/skeleton-scala) for more examples.
## Usage
```
>>> bling --help
bling.py
usage:
bling start
bling stop
bling run
bling build [--publish] [--debug]
commands:
start starts app inside an interactive container
stop stops running container
run starts app inside a container, executing the specified run command
build invokes `packer build` with packer template json file
options:
--publish publishes the build artifact to a remote registry
--debug enables debug mode
-h --help shows this
-v --version shows version
```
Example workflow:
```
$ bling build
$ bling start
```
## Development
Clone the project:
```
$ git clone git@github.com:ImageIntelligence/blingtron.git
```
Setup your virtualenv:
```
$ mkvirtualenv blingtron
```
Attach `bling` to your shell:
```
$ python setup.py develop
```
## Deployment
Create a `~/.pypirc` and replace the username and password with real credentials:
```
[distutils]
index-servers =
blingtron
[blingtron]
repository=https://pypi.python.org/pypi
username=xxx
password=yyy
```
Register this package to the Cheeseshop:
```
$ python setup.py register -r blingtron
```
Build a distributable and upload:
```
$ python setup.py sdist upload -r blingtron
```
Metadata
Release files for blingtron 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| blingtron-0.1.6.tar.gz | 7.6 kB | Without provenance | Details for blingtron-0.1.6.tar.gz |
Release files / blingtron-0.1.6.tar.gz
| Download URL | blingtron-0.1.6.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
367492ce2dd0b05951d8d9e1e0f19a8fd8c4f5468642a49feff952e45352a429
|
|
BLAKE2b-256 checksum How to use checksums |
56c48e4a600a27e33a31ea9e1b77edcef0193dd31a6ac0b121223b7c94dfcfa4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for blingtron 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.