Re: supplementX.xmltv.org

Hi Gary,
Fetching from GitHub directly is probably a Nono as XMLTV has a lot of users they might see that as abuse.

What I would suggest is to do a GitHub Action that uploads everything to S3 or something similar on each change. 
https://github.com/marketplace/actions/s3-sync <https://github.com/marketplace/actions/s3-sync>

That way we can also keep the supplement subdomains rather than toying around with Github pages.

Not sure either why XMLTV doesn’t use Github Actions instead of Jenkins as well.

> 5 nov. 2020 kl. 18:37 skrev Gary Buhrmaster <[email protected]>:
> 
> On Thu, Nov 5, 2020 at 5:07 PM Carsten Aulbert <[email protected]> wrote:
> 
>> Nick, Robert, others, any way you may help me with some instructions?
> 
> Making a mountain out of the molehill (and not
> really addressing the question at hand), while
> a bigger change, I am wondering if in the
> longer term the project should not move the
> supplemental data retrieval source to github
> itself (which is highly available) by changing
> the perl Supplemental module to retrieve
> from some part of github (I have not thought
> it through to know if that should be a new
> dedicated supplemental data repo, a release
> file, github pages, a new subdirectory in the
> repo, or just intelligent directed url access to
> the data in the repo by the Supplement module).
> 
> 
> _______________________________________________
> xmltv-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xmltv-devel

_______________________________________________
xmltv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xmltv-devel