mirror of
https://github.com/Squidly271/AppFeed.git
synced 2024-09-21 11:40:25 +00:00
54 lines
3.6 KiB
XML
54 lines
3.6 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<Container version="2">
|
|
<Name>neolink</Name>
|
|
<Repository>thirtythreeforty/neolink</Repository>
|
|
<Registry>https://hub.docker.com/r/thirtythreeforty/neolink/</Registry>
|
|
<Network>bridge</Network>
|
|
<Shell>sh</Shell>
|
|
<Privileged>false</Privileged>
|
|
<Support>https://github.com/thirtythreeforty/neolink</Support>
|
|
<Overview>Neolink is a small program that acts as a proxy between Reolink IP cameras and normal RTSP clients. Certain cameras, such as the Reolink B800, do not implement ONVIF or RTSP, but instead use a proprietary "Baichuan" protocol only compatible with their apps and NVRs (any camera that uses "port 9000" will likely be using this protocol).
|
|
|
|
NOTE: See the GitHub Repo for examples for setting up your appdata/neolink/config.toml file for each camera. https://github.com/thirtythreeforty/neolink
|
|
|
|
Neolink allows you to use NVR software such as Shinobi or Blue Iris to receive video from these cameras instead. The Reolink NVR is not required, and the cameras are unmodified. Your NVR software connects to Neolink, which forwards the video stream from the camera.
|
|
|
|
The Neolink project is not affiliated with Reolink in any way; everything it does has been reverse engineered.</Overview>
|
|
<WebUI></WebUI>
|
|
<TemplateURL>https://raw.githubusercontent.com/digiblur/unraid-docker-templates/master/neolink.xml</TemplateURL>
|
|
<Icon>https://raw.githubusercontent.com/digiblur/unraid-docker-templates/master/images/letter_n_blue.png</Icon>
|
|
<ExtraParams>--restart=on-failure</ExtraParams>
|
|
<PostArgs></PostArgs>
|
|
<CPUset></CPUset>
|
|
<Networking>
|
|
<Mode>bridge</Mode>
|
|
<Publish>
|
|
<Port>
|
|
<HostPort>8554</HostPort>
|
|
<ContainerPort>8554</ContainerPort>
|
|
<Protocol>tcp</Protocol>
|
|
</Port>
|
|
</Publish>
|
|
</Networking>
|
|
<Data>
|
|
<Volume>
|
|
<HostDir>/mnt/user/appdata/neolink/config.toml</HostDir>
|
|
<ContainerDir>/etc/neolink.toml</ContainerDir>
|
|
<Mode>rw</Mode>
|
|
</Volume>
|
|
</Data>
|
|
<Environment></Environment>
|
|
<Config Name="neolink_config" Target="/etc/neolink.toml" Default="/mnt/user/appdata/neolink" Mode="rw" Description="See the Neolink Github for camera setup examples required in this file." Type="Path" Display="always" Required="true" Mask="false">/mnt/user/appdata/neolink/config.toml</Config>
|
|
<Config Name="neolink" Target="8554" Default="8554" Mode="tcp" Description="Container Port: 8554" Type="Port" Display="always" Required="true" Mask="false">8554</Config>
|
|
<Date>1598322822</Date>
|
|
<Category>HomeAutomation: Tools:Utilities</Category>
|
|
<Description>Neolink is a small program that acts as a proxy between Reolink IP cameras and normal RTSP clients. Certain cameras, such as the Reolink B800, do not implement ONVIF or RTSP, but instead use a proprietary "Baichuan" protocol only compatible with their apps and NVRs (any camera that uses "port 9000" will likely be using this protocol).
|
|
|
|
NOTE: See the GitHub Repo for examples for setting up your appdata/neolink/config.toml file for each camera. https://github.com/thirtythreeforty/neolink
|
|
|
|
Neolink allows you to use NVR software such as Shinobi or Blue Iris to receive video from these cameras instead. The Reolink NVR is not required, and the cameras are unmodified. Your NVR software connects to Neolink, which forwards the video stream from the camera.
|
|
|
|
The Neolink project is not affiliated with Reolink in any way; everything it does has been reverse engineered.</Description>
|
|
<templatePath>/tmp/GitHub/AppFeed/templates/digiblursRepository/neolink.xml</templatePath>
|
|
</Container>
|