spaceinvaderone/shinobi_pro_unraid repository overview

⁠Shinobi Pro Unraid

This container is a clone of the official image by Migoller at https://hub.docker.com/r/migoller/shinobidocker⁠.
This build being in mind to use on an Unraid server. If not using Unraid please install from the above link. Thank you Migoller, mrproper, pschmitt & moeiscool for your work on the Docker images.

⁠Getting Started

Install for Unraid from community applications

Default is tag :latest

For use with nvidia build of Unraid for gpu encoding use tag :nvidia

⁠Prerequisites

Unraid OS

⁠License

There is no license required for the pro version if used in the home or a school. A license is required if used commercially.

Commercial Uses

• Selling usage of the software
• Using the software in locations that engage in the buying and selling of goods and services

Conditions for Free (Unpaid) use.

• Use in a non commercial area
• Used for non commercial purposes
• When used for research or educational purposes
• Testing Purposes
• Usage by Educational institutions
• Use for Emergency Services and facilties associated like Search and Rescue Services or
• Ambulance Services
• Use in Health Care facility like a hospital or walk-in clinic

⁠Usage

Install from community applications on Unraid and fill out docker template.

⁠Template Parameters

⁠Ports

• 8080 - 8080

⁠Environment Variables

• ADMIN_USER - admin
• ADMIN_PASSWORD - password

⁠Volumes

• /mnt/user/cctv/ - /opt/shinobi/videos
• /mnt/user/appdata/shinobipro - /config
• /mnt/user/appdata/shinobipro/database - /var/lib/mysql
• /mnt/user/appdata/shinobipro/customautoload - /opt/shinobi/libs/customAutoLoad

⁠Shinobi admin access

To access Shinobi super admin GUI head over to http://xxx.xxx.xxx.xxx:8080/super⁠

• Username: as defined by ADMIN_USER environmental variable
• Password: as defined by ADMIN_PASSWORD envrionmental variable

⁠Access Shinobi remotely on SSL using an Nginx reverse proxy

Use with the Unraid docker container letsencrypt reverse proxy https://hub.docker.com/r/linuxserver/letsencrypt/⁠ Create a proxy config file called shinobipro.subdomain.conf containing the below and place in /mnt/user/appdata/letsencrypt/nginx/proxy-configs

server {
listen 443 ssl;
listen [::]:443 ssl;

server_name shinobi.*;

include /config/nginx/ssl.conf;

client_max_body_size 0;

location / {
    include /config/nginx/proxy.conf;
    proxy_pass http://ip of the shinobi container:8080;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;       
	       

}

}