Server acts as a single entry point for all your worker nodes, as well as api clients. Essentially it is an HTTP REST API server with few methods that allow:
Redis database provider for `@nexrender/server`.
A CLI application which is responsible mainly for actual job processing and rendering, communication with the `nexrender-server`, and serves mainly as a consumer in the nexrender network model.
Allows nexrender to interact with an external SFTP server to upload results of rendering.
Allows nexrender to interact with an external FTP server to download or upload assets and/or results of rendering.
Encode your video to a specified format using built-in ffmpeg utility. You don't need to have ffmpeg installed on your system.
In case you are building your own application and just need to use a rendering part, or you wanna manually trigger jobs from your code, there is a way to use nexrender programmatically:
Copy your video/image sequence to a specified folder after rendering is finished
(alpha version)
Allows nexrender to interact with a Google Cloud Storage (GCS) bucket.
(alpha version)
MOGRT support for Nexrender
Cache your template source to a specified location and reuse it on subsequent runs
Upload video to an external storage provider ie. Amazon S3.
(alpha version)
(alpha version)
(alpha version)
(alpha version)
If you want to use nexrender API from browser/nodejs env you can use this module, instead of manually sending HTTP requests.
Create symbolic links between files or directories.
Allows nexrender to interact with an Amazon Web Services S3 storage.
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Serves a webpack app. Updates the browser on changes.
A simple zero-configuration command-line http server