Ubuntu 64 Install

[SHS]

Any post a reg install doc for SageTV Server Install 64x with latest ver with out all using the GitHub from stuckless ?.

[stuckless]

Originally Posted by SHS

Any post a reg install doc for SageTV Server Install 64x with latest ver with out all using the GitHub from stuckless ?.

Not exactly sure what you are after... to just "install" sagetv, you can download the BinTray deb package and then install it, and you are done.

Setting up IR blasting and comskip, etc, these are all somewhat tedious, and not really a part of the install, but rather the post installation configuration (if you need/want them).

You can also run the Docker image directly on ubuntu and it would come with the added benefit of having comskip configured. Configuring IR blasting would still require some effect.

[SHS]

Never mind I guest I miss the v2 (Basic Linux V9 Build and Walkthrough - V2) as ver 1 from SageWizdom was jump all over place
So from look of it look like I have fellow step3, 5 thur 8 and just update commands to ref the latest ver of sagetv deb
I just for test WinTV-quadHD

[matt91]

You can also run the Docker image directly on ubuntu and it would come with the added benefit of having comskip configured. Configuring IR blasting would still require some effect.

I realize this isn't really a sage question, but what's the (estimated) performance hit for this? Running docker + sage must consume more resources than just running sage alone. Is it generally a small hit?

[stuckless]

Originally Posted by matt91

I realize this isn't really a sage question, but what's the (estimated) performance hit for this? Running docker + sage must consume more resources than just running sage alone. Is it generally a small hit?

In short, you likely can't tell the difference... but here's a much better explained response

http://stackoverflow.com/questions/2...cker-container

[ThePaladinTech]

Originally Posted by stuckless

You can also run the Docker image directly on ubuntu and it would come with the added benefit of having comskip configured.

Just saw this... This may be the solution for my brother as getting unraid isn't an option.

Could you help me with some of the commands? from here: https://forums.sagetv.com/forums/showthread.php?t=63165


docker run -d --name sagetv-server \ <- so that names it so it's not some random named container right?
-v /home/seans/unRAID/mnt/user/sagemedia:/var/media \
-v /home/seans/unRAID/mnt/user/mediaext:/var/mediaext \
-v /home/seans/unRAID/mnt/user/apps/sagetv3:/opt/sagetv \
-v /home/seans/unRAID:/unraid \
--net host \
--env PUID=1000 \
--env PGID=1000 \
--env VIDEO_GUID=19 \
--env OPT_GENTUNER=Y \
--env OPT_COMMANDIR=Y \
--env OPT_COMSKIP=Y \
--env JAVA_MEM_MB=768 \
--env VERSION=latest \
--env OPT_SETPERMS=Y \
--privileged \ <- This gives it more access to the system? for remote access as far as I can tell?
-t -i stuckless/sagetv-server-java8

I'm most puzzled by the -v command I bolded - what would the equivelent be for ubuntu? btw the ubuntu user is 'sagetv9'

Thanks all

Edit: presently looking through the 11 page post i referenced, maybe it's in there

[Fuzzy]

the -v option is used to map an actual host folder to a folder within the container. What that bolded one does, is map actual folder /home/seans/unRAID to /unraid inside the container, so sagetv could find any file under the /home/seans/unRAID folder beneath it's own /unraid folder... Technically, the only volume mapping (-v option) that would be required for sagetv would be mapping the server folder (/opt/sagetv) and a share used to access recording and import folder locations (/var/media).

Internally, I believe sage defaults to the following paths:
/opt/sagetv -> SageTV main folder
/var/media/tv -> SageTV Recordings folder
/var/media/videos -> Video Import folder
/var/media/pictures -> Picture Import folder
/var/media/music -> Music Import folder

[stuckless]

You can ingnore -v unraid option since I use that to better mimic what an unraid filesystem looks like when I doing testing.

--priviledged is used so that it can expose the necessary ports with mapping them (it is required)

And yeah, that first bolded part is so that you give it a good name which makes it easier if you need to run docker logs etc.