Better containerization support

[NW11NG]

🚀 Description

Problem to solve

Current the docker compose implementation is not efficient for users running an existing stack, it seems you need to edit the nginx to avoid port binding issues for other services etc.
It would be nice to see better support for environment variables within the compose as well as adding VPN support (gluetun) which isn't possible with the current deployment options

Proposal

Publish to docker hub and allow users to choose how they would like to deploy with environment variables or custom networks like gluetun as well as setting paths for persistant storage. Ports should also be published as well as the nginx credentials to allow customisation

Further details

By all means if I am missing something please li k me the documentation but I have spent days trying to get this to work inside a vpn and despite opening correct ports it seems the frontend and backend cannot communicate due to the urls inside of the dockerbuild files

✅ Acceptance Criteria

• [ ]

[antebrl]

Thank you for the issue.
Please confirm if I understood you correctly:

• You want an environment variable to configure the outward-facing port of Nginx. Currently, this port must be set manually in the docker-compose.yml file. For example, to use a custom port 1234 on the host machine, you would configure it like this:

iptv_restream_nginx:
   image: nginx:alpine
   ports:
     - "1234:80"

Publish to docker hub

I have published the images on ghcr. See this docker-compose.yml

I have spent days trying to get this to work inside a vpn and despite opening correct ports it seems the frontend and backend cannot communicate

I haven't tested deploying the application alongside a VPN and don't have much experience with VPN-based setups. The Docker containers are all part of a custom network and share this namespace. If you separate them into different VPN networks, it could cause communication issues.

Could you provide more details about your deployment setup? That might help us troubleshoot the problem more effectively.

[markcs]

To add to this, I currently have Caddy running and don't really want to deploy another proxy handler.

I think I have it 'almost' working by commenting out the nginx section and modifying the docker file a bit, however restreaming is not working. I see 404 not found, so I think my caddy definitions are incorrect..

Can you let me know what is happening in this section of the nginx conf file? I see the ts files being written into the backend under the /stream folder. Should this be proxied to iptv_restream_backend or frontend and which port to use?

Thanks!

        location /streams/ {
            root /;

            add_header 'Access-Control-Allow-Origin' '*';
            add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS';
            add_header 'Access-Control-Allow-Headers' 'Range';
            add_header 'Access-Control-Expose-Headers' 'Content-Length, Content-Range';

            add_header Cache-Control no-cache;
            add_header Pragma no-cache;
        }

EDIT: Ignore the above, I have it working. But it would be good to split out the NGINX config and just provide a docker example configuration

[antebrl]

Thanks for reaching out.

But it would be good to split out the NGINX config and just provide a docker example configuration

What exactly do you mean with a docker example configuration?