Introduction

A zc.buildout recipe that configures a collective.transcode.daemon instance

For more info check out

Supported options

The recipe supports the following options:

listen_host
    hostname to listen

listen_port
    port to use

videofolder
    relative path of folder where transcoded videos are stored

secret
    a secret shared key used for authentication and encryption

profiles
    a python list of dicts specifying the supported transcoded
    profiles. The dict should contain
        i) the id of the profile,
        ii) the command to be executed with the first parameter to be the input and the second the output file
        iii) the list of supported mime types for this profile
    e.g. profiles = [ {'id':'low', 'cmd':'scripts/lowQualityTranscode %s %s', 'supported_mime_types': ['video/mpeg', 'video/3gpp'] } ]

Contributors

Dimitris Moraitis, unweb.me
Mike Muzurakis, unweb.me
Markos Gogoulos, unweb.me
Victor Rajewski, engagemedia.org
Christos Psaltis, unweb.me

Change history

0.2 (2010-07-22)

Release for collective.transcode.daemon 0.2 [dimo]

0.1 (2010-02-18)

Initial release [dimo]

Download

Metadata

Release files for collective.transcode.recipe 0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for collective.transcode.recipe 0.2
File	Size	Uploaded	Provenance
collective.transcode.recipe-0.2.zip	10.8 kB	Jul 22, 2010	Without provenance	Details

Release files / collective.transcode.recipe-0.2.zip

Download URL	collective.transcode.recipe-0.2.zip
Size	10.8 kB
Tags	Source
SHA-256 checksum How to use checksums	`09a0aa7b676b59e07b37c27b8ea31fdb26ab8613e9e1f74111e214f051b9b62a`
BLAKE2b-256 checksum How to use checksums	`bdc27dc27cdf5dfbcf68e43140b12f448c09e6c23c0cba41bcd175fa5946614a`
Upload date	Jul 22, 2010
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for collective.transcode.recipe 0.2

Report project as malware

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.

Release history Release notifications | RSS feed

This release

0.2 This release

Jul 22, 2010 1 release file No provenance

0.1

Feb 18, 2010 1 release file No provenance

collective.transcode.recipe 0.2