-
Notifications
You must be signed in to change notification settings - Fork 13
We continue here, what started at https://projects.vdr-developer.org/git/vdr-plugin-live.git
License
MarkusEh/vdr-plugin-live
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This is a "plugin" for the Video Disk Recorder (VDR). Written by: Thomas Keil <[email protected]> Sascha Volkenandt <[email protected]> Currently maintained by: Markus Ehrnsperger ( MarkusE @ https://www.vdr-portal.de) Previously Maintained by: Dieter Hametner <[email protected]> Christian Wieninger <[email protected]> Jasmin Jessich <[email protected]> Project's homepage: https://github.com/MarkusEh/vdr-plugin-live Project's old homepage: http://live.vdr-developer.org Latest version available at: https://github.com/MarkusEh/vdr-plugin-live See the file COPYING for license information. Description: ============ Live, the "Live Interactive VDR Environment", is a plugin providing the possibility to interactively control the VDR and some of it's plugins by a web interface. Unlike external utility programs that communicate with VDR and it's plugins by SVDRP, Live has direct access to VDR's data structures and is thus very fast. Requirements: ============= VDR >= 2.4.0 gcc >= v8, must support -std=c++17 PCRE2 >= 10.38 - https://github.com/PhilipHazel/pcre2/releases Tntnet >= 2.2.1 - http://www.tntnet.org/download.hms // https://web.archive.org/web/20160314183814/http://www.tntnet.org/download.html Cxxtools >= 2.2.1 - http://www.tntnet.org/download.hms // https://web.archive.org/web/20160314183814/http://www.tntnet.org/download.html Tntnet provides basic Web server functions for live and needs cxxtools. Boost provides some data structures we need. While currently relying on the full blown package we might provide a stripped down version in the future. PCRE2 provides filtering for recordings using Perl regexp language. If you don't need filtering, PCRE2 is optional. If you optionally want to regenerate the i18n-generated.h header file for backward compatible i18n (VDR version prior to 1.5.7) you also need: (See also the Internationalization section below) Locale::PO - Perl module from CPAN www.cpan.org The default i18n-generated.h header contains all translations from GIT. Users that just want to stay on bleeding development edge of live do not need Locale::PO installed. How to get Locale::PO - Use search function on www.cpan.org to obtain module. - Check if your distribution provides the package. (e.g. in Debian the package name is liblocale-po-perl) If you added new translations in your language specific .po file and still want to use an VDR older than version 1.5.7 you must regenerate i18n-generated.h by calling make with the target generate-i18n. Only in this case you need to have Locale::PO installed on your system. Installation: ============= If you compile the plugin outside of the VDR source codes you must copy the resulting binary to VDRs directory where the other plugins are expected. In order to work correctly you must copy the subdirectory 'live' from the source distribution to the directory where the VDR plugins look for their resource files. The pure VDR default for this config directory is: /video/plugins, but this depends also from the parameters -c or -v (see 'vdr --help' for details). cp -a <live-src-dir>/live <vdr-resource-dir>/plugins Setup: ====== Live provides a username/password protection, so that it can be used from the internet. The default username and password are: admin/live The default port is 8008. You can also specify this parameter via command line: -p PORT, --port=PORT use PORT to listen for incoming connections (default: 8008) -i IP, --ip=IP bind server only to specified IP, may appear multiple times (default: 0.0.0.0, ::0) Additional SSL options are available now. See "How to make LIVE listen for SSL connections" section below on hints how to setup SSL. To display images or channel logos, you can use: -e <...> --epgimages=/path/to/epgimages use EPG images created by plugins like tvm2vdr --chanlogos=/path/to/channellogos use channel logos (PNG only, case sensitive) Web streaming: To play live tv / recordings directly in the browser, data must be converted. ffmpeg is used for that. The ffmpeg commands including command line options used for different purpouses are in the file ffmpeg.conf in the VDR config directory (on debian like systems, this is /etc/vdr/plugins/live). Default values come with live, you can change these in ffmpeg.conf if needed The rest of the parameters can be adjusted in VDR's OSD or in the web interface. The password is stored as a MD5 hash. "Last Channel" is the last channel in the channels list, that live displays. This is especially useful if you have VDR's automatic channel update active. For example, you can add a group separator ":@1000 Found automatically" to channels.conf and set this parameter to "1000". Thus, everything VDR finds during scanning (which can after a few months be well more than 3000 channels) won't be displayed. How to make LIVE listen for SSL connections: ============================================ To make LIVE listen for incoming SSL connections you`ll have to use a Tntnet version > 1.6.0.6. By default it will listen on port 8443. * Example: https://localhost:8443 In order to start the SslListener LIVE requires a SSL certificate. If no SSL certificate is specified via command-line option, LIVE will try to use the default certificate location '$VDRDIR/plugins/live/live.pem'. If neither the default nor the custom certificate (given by the command-line option) could be found, LIVE will only start the default HTTP Listener (default: 8008) If you want do disable the SslListener for any reason, specify SSL port number 0 with the command-line option. Note: Since the GNU TLS SslListener was broken in Tntnet versions prior to SVN revision 1035 you will have to recompile Tntnet with "./configure --with-ssl=openssl" to make it work. Alternatively install version 1.6.2 or higher of Tntnet on your system. SSL Command-line options: ========================= -s PORT, --sslport=PORT use PORT to listen for incoming SSL connections (default: 8443) use PORT 0 to disable incoming SSL connections -c CERT, --cert=CERT path to a custom SSL certificate file (default: $CONFIGDIR/live.pem) -k KEY, --cert=CERT path to a custom SSL certificate key file (default: $CONFIGDIR/live-key.pem) Creating a self-signed SSL server certificate: ============================================== To create a self-signed certificate file you`ll have to run this litte command. $> cd /put/your/path/here/vdr/plugins/live $> openssl req -new -x509 -keyout live-key.pem -out live.pem -days 365 -nodes While generating the certificate you`ll be asked to answer a couple of questions. When it prompts to enter the "Common Name" you`ll have to specify the full qualified DNS server name of the machine LIVE is running on (e.g. vdr.example.com). If your VDR doesn't have a full qualified DNS name, you should use the IP Live is listening on. Note: This is just a quick-and-dirty way to create a SSL self-signed certificate. Recent browsers (like Firefox 3) will complain about it because the certificate wasn't signed by a known Certificate Authority (CA). So how does LIVE work? ====================== Basically, Live itself is a Tntnet Web server integrated into the plugin structure VDR needs. This Web server, running in VDR's environment, is provided with all public data structures VDR provides for plugins and thus has very fast access to information like the EPG, timers or recordings. Live's "pages" are written in "ecpp", a language integrating C++ and HTML in one file, very much like e.g. PHP or ASP weave functionality and "static" content information together. Contribute! =========== If you would like to contribute, please read doc/dev-contribute.txt and doc/TODO.txt. Internationalization (i18n): ============================ LIVE uses the same i18n support like VDR does since version 1.5.7. This version of LIVE can not support i18n compatible with VDR versions older than 1.5.7. All localization files are found in the po subdirectory of the LIVE plugin source. Security considerations: ======================== Please use live in a controlled environment only, like your home network or a save VPN of your home network. You cannot expect sufficient security to expose live to the public internet. Of course, better security is always appreciated, so please send patches increasing security. One possible security issue (there might be others ...): Live uses the Tntnet MapUrl mechanism to map different request URLs to Tntnet components. One component 'content.ecpp' delivers files found in the file system. When given the wrong 'path' it could retrieve any file from the server where live runs on. Therefore content.ecpp has been enhanced to check the paths before returning files. A second measure against misuse is to limit the mappings from MapUrl to only valid files. In the current version this approach has been taken. But due to the 'difficulty' to fully understand regular expressions, this might get spoiled again by 'unchecked' code contribution. Errors ====== If VDR crashes on start with these journal messages: loading plugin: /usr/local/lib/vdr/libvdr-live.so.x.x. terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid Most likely, the locale is not installed correctly. On Debian based systems, use: dpkg-reconfigure locales and restart VDR.
About
We continue here, what started at https://projects.vdr-developer.org/git/vdr-plugin-live.git
Resources
License
Stars
Watchers
Forks
Packages 0
No packages published