2024-08-09, 04:32 AM
Thanks, it was the server link, I got it now. The project looks great, thanks for the support. We'll be waiting for new updates.
2024-08-09, 04:32 AM
Thanks, it was the server link, I got it now. The project looks great, thanks for the support. We'll be waiting for new updates.
2024-09-10, 03:21 PM
I'm having trouble getting the Docker container installed on unRAID.
My compose file is below, but it's not pulling the image. I'm sure I'm missing something simple. Thanks for any help. services: jellix: container_name: jellix image: doihaveto/jellix build: ./jellix restart: unless-stopped environment: - API_URL=http://10.0.0.134:8097/ ports: - 3000:3005
2024-09-12, 05:22 AM
(2024-09-10, 03:21 PM)volcs0 Wrote: I'm having trouble getting the Docker container installed on unRAID. There's no image to pull. I'll try to get around to doing that in the next week or so. In the meantime delete the "image:" line, and it will build it locally.
2024-09-25, 05:34 PM
New version released!
https://github.com/doihaveto/jellix/ - A docker image is now available, which makes it a lot easier to install. It's at ghcr.io/doihaveto/jellix . Example docker-compose file is in the project page.- Added movie trailers that are automatically played after 7 seconds. Can be disabled for the current session, or disabled entirely in the settings menu. - Each category will now display all of the available movies, not limited to a certain number per category. - Docker container is now running nginx instead of a python webserver. - Other minor changes.
2024-09-25, 07:15 PM
Thanks for this looks good. But I've just tried this for the first time and while the container runs and is healthy I'm getting this:
exec /entrypoint.sh exec format error My stack file running in Portainer on a Raspberry pi5: services: jellix: image: ghcr.io/doihaveto/jellix container_name: jellix restart: unless-stopped environment: - API_URL=http://192.168.1.43:8096/ ports: - 3000:80 Any ideas? I did a quick google of the error and it may be something to do with how the image was created. Also what address should I use based on my compose file: 192.168.1.43:3000 or where the Jellix container is tunning: 192.168.1.56:3000
Jellyfin1 - 10.10.3 (Docker) Synology NAS (transcoding off)
Jellyfin2 - 10.10.3 Minix ZX100-0db MiniPC, Intel N100 (transcoding on) Storage - x3 Synology NAS (22TB) Reverse Proxy - Caddy v2 running on a Pi3b+
2024-09-26, 05:11 AM
(2024-09-25, 07:15 PM)pxr5 Wrote: Thanks for this looks good. But I've just tried this for the first time and while the container runs and is healthy I'm getting this: It's running ok but you're still getting an error? That's weird. Can you tell me where are you seeing this error, and send it in full? Also do you see any errors in docker logs for this container?
2024-09-26, 01:15 PM
(This post was last modified: 2024-09-26, 01:38 PM by pxr5. Edited 1 time in total.)
I think I may have misunderstood how this works and that Jellix needs to be run on the same server as Jellyfin. I've just spun up a container on my Synology NAS (where Jellyfin is installed) and it works fine with the same compose file. I have another instance of Jellyfin running on a MiniPC and pointed the same container at that IP address and it doesn't work. So all is good my end.
I'm now wondering how I could access Jellfix remotely as I use a reverse proxy normally. Maybe just another entry in the Caddy file for 192.168.1.43:3000 - I'll do some testing when I get chance. Only movies though, is that right?
Jellyfin1 - 10.10.3 (Docker) Synology NAS (transcoding off)
Jellyfin2 - 10.10.3 Minix ZX100-0db MiniPC, Intel N100 (transcoding on) Storage - x3 Synology NAS (22TB) Reverse Proxy - Caddy v2 running on a Pi3b+
2024-10-14, 02:24 PM
(2024-09-26, 01:15 PM)pxr5 Wrote: I think I may have misunderstood how this works and that Jellix needs to be run on the same server as Jellyfin. I've just spun up a container on my Synology NAS (where Jellyfin is installed) and it works fine with the same compose file. I have another instance of Jellyfin running on a MiniPC and pointed the same container at that IP address and it doesn't work. So all is good my end. It should work regardless of where you run it, but perhaps the browser's CORS policy is preventing it from accessing jellyfin if it's not on the same server. I ran it on different machines on my local network and didn't have issues, but perhaps that's because it was on the local network. You are correct that it's only movies. I'm not sure if there's much use for the same setup for shows.
2024-10-18, 03:50 PM
Great job. I Will test.
|
|
|