OliveTin for Channels: An Interface for Misc Channels DVR Scripts & Tricks

OK. I've sorted out the Raspi OS issue but I'm struggling now with how exactly to set up my dvr-server volume. I'm running docker/portainer on a separate machine to the Channels DVR server but I can't work out exactly what I need in terms of the portainer volume.

I have read this and the linked thread about file volumes but I'm still unsure. I presume I need to set up a samba share volume for it? If so how exactly as the CIFS option seems to need username and password. IIRC from when I set up access to it from my Linux PC, the samba share to my DVR uses user root but no password.

My DVR server is at 192.168.1.8 and it's samba share is \DVR-SERVER\MEDIA\DVR\

You need to be a valid user to access a Samba share. For example, if your Samba share is on a Windows PC and that PC only has one user setup, then that user's name and password would be what you'd use.

It your Samba share is on a Linux box, then valid Samba users are setup on that box. I'm not sure if root with no password is even possible, without even considering whether it's a good idea (it's not). Here again, if it's a one user box, then that user's credentials are the likely answer.

Generally, looking at the share using Windows or anything with a desktop GUI should give you a good idea of the machine name and share name. For example:

Here are all my shares on //media-server6. Folders /dvr and /ChannelsDVR are where my CDVR recordings and log data are found.

So, I would have Portainer-Volumes created for each using either the hostname or IP and share names of dvr and ChannelsDVR. Whatever you choose to call those Volumes is the name you'd use in the OliveTin stack.

You'd need to uncomment the very bottom section of the compose relating to volumes, and then define each similar to this example:

volumes: # use this section if you've setup a docker volume named channels-dvr, with CIFS or NFS, to bind to /mnt/dvr inside the container. Set ${DVR_SHARE} to channels-dvr (DVR_SHARE=channels-dvr) in that example.
  channels-dvr:
    external: true
  channels-dvr-logs:
    external: true

Assuming you chose channels-dvr and channels-dvr-logs as your volume names.

1 Like

I'm using the OEM Raspi 4 image for my DVR Server.

In investigating all this I have just discovered that the Channels image comes with Docker built in. So it seems the best way would be to run Olive Tin directly on there as the file access would be direct.

But, I really, really don't want to screw up my Channels server when I don't really know what I'm doing other than blindly following instructions!

Is anyone running Olive Tin on the OEM Channels Raspi 4 image version?

Would the instructions above all still work fine?

If Docker is included, one would assume you can install containers, and both Portainer (required) and OliveTin are just that after all.

The only other requirement I can think of, that would be worth investigating, is what part of the filesystem is available to bind read/write directories to. I'd test it for you myself, but I'm away from my home lab, for about another month.

If you're not opposed to spending a few dollars, one might consider buying another RPi4 as a test platform -- for just this kind of testing/validation.

1 Like

I've built a new bnhf/olivetin:latest (aka bnhf/olivetin:2024.04.11), with some notable interface changes:

There's now a side menu, instead of the "Actions" and "Logs" buttons:

When you initiate an Action, there's a pop-up rather than the previous larger overlay, which is much nicer when more Action buttons are present:

After clicking "Start", another pop-up is displayed with the results of stdout (now called Standard Output), immediately visible. No need to go to the logs to view it:

There is still a Logs option on the side menu:

And in Logs, there's now a search option:

Overall, some nice changes I think, and there are numerous additional options (based on upstream OliveTin) that can be taken advantage of in the future.

It's possible some may need to "clear images and files" in their browser after updating. Also, in situations where you're expecting an icon to change color, a manual browser refresh is currently required (working on that one). Enjoy!

1 Like

Great idea. I don't even need to spend anything as I have a spare Raspi4 that I got to try out as an Android TV client but it wasn't any good. I'll fire it up as a second Channels DVR and try out Olive Tin on that.

What browser are you using ?
I get gibberish ...

Chrome -- but your screenshot looks OK to me. Where's the gibberish?

EDIT: The icons on the left are from Organizr -- if that's what you're talking about...

Look at the Actions side menu. nothing there.

Those icons on my screenshot are from Organizr, which is available as a Project One-Click install. You may see some items on the OliveTin side menu in the future. :slight_smile:

EDIT: You're actually looking at two side menus next to each other, one is Organizr, the other is OliveTin. Kind of like the way most of us have multiple top menus.

Yeah I see ... hamburger Icon on the left opens that empty side menu.

For now, if you want to go to see all the logs, use the Logs option at the bottom of the side menu. And then, the Actions option gets you back from Logs.

...since you have the GUI book open - any chance you would consider something like docker's "Advanced mode," which would allow for cut/pasting environment variables in? This would make multiple tries at some of the variable-heavy items much less painful.

Not in quite that way. But I could make the values you enter the new defaults? With the exception of passwords of course.

I'll test to be sure, but I think Roboform could capture all of one's field data when entered, and auto fill in the future.

I do this now when testing for username and password, but I think it could store all fields. Upside with this is you'd never end up with bad data as the default.

Roboform is the answer! Just tested on Windows and Mac. The free version should be fine.

On the Mac, when you enter your form data, use the "Option" button when you click "Start" and you'll be prompted to save your form data:

Then next time through on that same Action item:

It'll offer to autofill the fields. One word of caution, use the fill forms option available from the stacked dots, otherwise the form gets submitted immediately. Much better to have it fill, look things over one last time, and then click "Start".

1 Like

@Edwin_Perez says: "Hey how 'bout a little something on that new side menu?" :slight_smile:

@bnhf says: "Coming right up!":

New version of bnhf/olivetin:latest (2024.04.12) pushed today with Project One-Click moved to its own dashboard. More details here:

1 Like

I know you like roboform, but the above would be simpler for most.

Is the first post updated with the latest docker-compose and environment variables?

It was good, but I just sync'd it with a couple of small changes I made in the bottom volumes section for anyone using network shares, so it's even better now. :slight_smile:

Thanks, thought I did something wrong. Turns out the new changes don't work with Firefox (v124.0.2).

Brave and Edge are working.