← Directory

XTeVe G2G OWI

XTeVe G2G OWI is a combined Docker image that bundles XTeVe, guide2go, and owi2plex into one persistent container for Internet Protocol television (IPTV) and…

  • Downloaders
  • Tools & Utilities
XTeVe G2G OWI is a combined Docker image that bundles XTeVe, guide2go, and owi2plex into one persistent container for Internet Protocol television (IPTV) and electronic program guide (EPG) workflows. It proxies tuner streams to Plex, Emby, and similar TV apps, pulls Schedules Direct guides, and reads guides from Enigma receivers through Open WebIF. The image includes cron jobs and a web interface, making it useful for homelab users who want one container to manage channels, schedules, and EPG updates.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

13/100 Low

Maintained
0last commit 941 days ago
Popular
165 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 12 days ago

GitHub stars
5
Open issues
0
Last commit
2024-03-16
Latest release
latest
Activity
stale

Checked 5 days ago - source: GitHub (alturismo/xteve_g2g_owi)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 15 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Default port 34400 is for your TV apps xTeVe listens on port 34400 by default, so open that port for the TV app, tuner, or device that will connect. If 34400 is already used by something else, start xTeVe on another port using its -port option so other apps know where to find it. source
  • Keep the ~/.xteve settings folder safe By default, xTeVe keeps its settings in the ~/.xteve/ folder, or in a different folder you set with -config. Back up or protect this folder, because it holds your channel configuration and can make the app start broken if it is missing. source
  • Guide URLs may need login details If you turn on xTeVe login, some guide addresses like /xmltv/xteve.xml can require a username and password. Without the right credentials, your media app may not load the TV program list even though xTeVe is running. source
  • Check persistent config after first start After the first start, review the mounted config folders for XTeVe, guide2go, and owi2plex. The container runs in host mode and preserves setup, so delete the config contents if you want to start from scratch. source

Fetched 6 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where is the xTeve web interface after starting the container?

Open the xTeve web UI at the machine IP on port 34400 with the /web/ path. The documentation says the container runs in host mode.

How is xTeve configuration persisted across container restarts?

The setup is persistent in the config folder after the first start. A sample mount maps /root/.xteve to a host appdata folder and /config to a host path.

When do changes to cron and xTeve start options take effect?

They are updated when the Docker container is restarted.

How do I install this app on Unraid?

Find xteve_g2g_owi in Community Apps, review the template, and click Install. Unraid handles the Docker app setup from the published template.

Answers sourced from ca.unraid.net, github.com, hub.docker.com

Community

Collected 14 days ago - public community threads