Hayaku - lightweight Python utility to generate Dockerfile and distribute tiny python apps without including sources
[](https://travis-ci.org/msoedov/hayaku)
## Instalation
```shell
pip install hayaku
```
## Why?
Disclaimer this repo being made just for fun in certain circumstances and have non opinionated approach for doing things.
The purpose of this is to wrap your existing tooling written in python into containers and then ship/distribute it without complicated
workflow around git repo's.
## Approach
0. Autodetect of required pip packages which needs to be installed
1. Encode py sources with base64/zip/bzip
2. Put encoded data into of generated `Dockerfile` ENV (According to POSIX we can put up to 256Mb into env variable)
```shell
ENV PY_LIB "{body}"
```
3. Extract it during docker build
```shell
RUN python -c "import os,base64;b=os.getenv('PY_LIB');b=base64.b64decode(b);print(b.decode('utf-8'))" | tee app.py
```
4. So the final generated Dockerfile will looks like this
```shell
hayaku app.py
FROM python:3.6
MAINTAINER Erlich Bachman
WORKDIR /app
RUN pip install requests
ENV PY_LIB "aW1wb3J0IGJhc2U2NAppbXBvcnQgb3MKZnJvbSB...."
RUN python -c "import os,base64;b=os.getenv('PY_LIB');b=base64.b64decode(b);print(b.decode('utf-8'))" | tee app.py
CMD python app.py
```
which you can ship as a file, build and push image to private docker registry, etc...
## Seriosly ?
It's up to you. It worked for my limited usecase and I hope it might be helpfull for somebody else. As it said in disclamer: this repo being made just for fun in certain circumstances and have non opinionated approach for doing such things.
[](https://travis-ci.org/msoedov/hayaku)
## Instalation
```shell
pip install hayaku
```
## Why?
Disclaimer this repo being made just for fun in certain circumstances and have non opinionated approach for doing things.
The purpose of this is to wrap your existing tooling written in python into containers and then ship/distribute it without complicated
workflow around git repo's.
## Approach
0. Autodetect of required pip packages which needs to be installed
1. Encode py sources with base64/zip/bzip
2. Put encoded data into of generated `Dockerfile` ENV (According to POSIX we can put up to 256Mb into env variable)
```shell
ENV PY_LIB "{body}"
```
3. Extract it during docker build
```shell
RUN python -c "import os,base64;b=os.getenv('PY_LIB');b=base64.b64decode(b);print(b.decode('utf-8'))" | tee app.py
```
4. So the final generated Dockerfile will looks like this
```shell
hayaku app.py
FROM python:3.6
MAINTAINER Erlich Bachman
WORKDIR /app
RUN pip install requests
ENV PY_LIB "aW1wb3J0IGJhc2U2NAppbXBvcnQgb3MKZnJvbSB...."
RUN python -c "import os,base64;b=os.getenv('PY_LIB');b=base64.b64decode(b);print(b.decode('utf-8'))" | tee app.py
CMD python app.py
```
which you can ship as a file, build and push image to private docker registry, etc...
## Seriosly ?
It's up to you. It worked for my limited usecase and I hope it might be helpfull for somebody else. As it said in disclamer: this repo being made just for fun in certain circumstances and have non opinionated approach for doing such things.
Metadata
Release files for hayaku 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hayaku-0.1.2.tar.gz | 2.6 kB | Details |
Release files / hayaku-0.1.2.tar.gz
| Download URL | hayaku-0.1.2.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e746d63b5a5d3904767ae4fad90b012fcc8f996a550452e9d5fb5c9c4592e661
|
|
BLAKE2b-256 checksum How to use checksums |
62176011908ddf35abc1d1b23e827a7e67f0726d9745761851010c9d0f03a861
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |