# Autolive: AWS medialive automation
The core idea of this proyect is to offload video transcoding from an NGNIX-RTMP server to AWS Medialive, replacing FFMPEG for transcoding and reducing server load from NGINX server.
NGINX RTMP: https://github.com/arut/nginx-rtmp-module
## How to make it work:
Install Nginx with rtmp module.
Git clone Autolive into preferred dir.
Set AWS details in conf.py.
Simlink autolive to /usr/local/bin/autolive.
Change nginx.conf to trigger autolive. (using nginx-rtmp exec options)
## AWS resources needed:
DynamoDB table that defines channel details. (schema comming soon)
s3 bucket for AWS medalive outputs.
CDN distribution. (optional)
## CLI options:
‘-s’, ‘–streamkey’ –> (string) | Define streamkey. Streamkey should reference dynamodb table.
‘-a’, ‘–action’ –> (string) | Define what action to perform: ‘create’, ‘delete’.
‘-A’, ‘–application’ –> (string) | manually define Nginx rtmp application, default ‘live’.
## Notes:
ATM only pull channels are supported. Lots of improvment needed but core functionality is working.
Metadata
Release files for autolive 0.0.3
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 | |
|---|---|---|---|---|
| autolive-0.0.3.tar.gz | 6.6 kB | Without provenance | Details |
Release files / autolive-0.0.3.tar.gz
| Download URL | autolive-0.0.3.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b04b1cf78e723f7b60fa7d1c2e9ce033d8f50013296f5c143de5d4d3a702f77a
|
|
BLAKE2b-256 checksum How to use checksums |
efd1984aed9155753c69decc8dce297072540b220db2fe7cf3fcabc5decf8ad6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.10.0 pkginfo/1.2.1 requests/2.23.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.19.5 CPython/3.6.9
|
Security for autolive 0.0.3
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.