What is next?

[SenexCrenshaw]

I am debating what the next steps here should be. I was considering:

1. A UI rewrite with something like Vue.JS
2. The backend probably could use some work and porting to C# is interesting as well.
3. Name change??

I would separate the two systems (frontend/backend). I think these two will allow other features to be added more easily. Things like channel failover #47 and #38

I am fine with the way things are since it works but I am always considering new ideas that might help y'all out.

[SenexCrenshaw]

I decided to create a new repo. It will use c# in the backend for the server/api piece and VUE JS3 for the front end. I will keep updating this repo as bugs come in.

With the new application:
Virtual hdhomeruns with individual channels.
Multiple channels can be grouped together for additional viewing connections/failover
EPG data can be selected per channel.

This should give lots of flexibility and a new UI will be welcomed.

[aniel300]

yes please a revamp might not be a bad idea

[SenexCrenshaw]

things are moving along nicely. I have a decent backend written in .net core c# and the UI in react (TS). The plan is to allow uploading whatever amount of M3U/EPG files. From there you can allocate any channels from the EPG files to any amount of HD Home Runs. It will try to match channel names in M3U files for failover and what not. It should be very flexible. No idea when I can get an alpha out to play with but I am pecking away!

[aniel300]

am relative new to xteve and iptv in general, but how would the channel failover work ? (it sounds like a nice thing to have since this way is just one channel showing but it will switch/failover if it goes down (all in the background)?

[kjetilhp]

a little late to the party, is the switch to c# and react a personal preference or based on technical issues with go? too bad about the choice of react over vue though ;) anyway, will you share the new repo before the alpha? WIll the failover work with all these ppv channels that changes names and appears dynamically on a daily basis?

[xtinct101]

All this sounds amazing, can't wait to try it out.

[SenexCrenshaw]

Plugging away here when I have free time. I am working out how to handle multiple EPGs/Channels and the UI. I have taken this time to learn React so this is taking longer than I thought. I would very much like a beta out this year and am trying my best to make that happen.

[SenexCrenshaw]

am relative new to xteve and iptv in general, but how would the channel failover work ? (it sounds like a nice thing to have since this way is just one channel showing but it will switch/failover if it goes down (all in the background)?

It would need to be proxied/buffered through the server so when a backend stream fails it will use the other stream. I plan on adding in statistics for this as well so we know how the channels behave.

[SenexCrenshaw]

a little late to the party, is the switch to c# and react a personal preference or based on technical issues with go? too bad about the choice of react over vue though ;) anyway, will you share the new repo before the alpha? WIll the failover work with all these ppv channels that changes names and appears dynamically on a daily basis?

With out starting a serious debate... C# is a personal preference since its so easy and portable now-a-days. VS Code/Studio are solid IDEs.

I am a huge VUE fan as well. I decided to go React since a lot of people out there know React and it was another framework for me to learn. I have been happy with react/redux so far. You could re-write the UI in anything you would like. The server is c# asp.net core and the frontend can be anything.

Once I get the HDHRs worked out, the buffer mechanism and cleanup I will share.

"WIll the failover work with all these ppv channels that changes names and appears dynamically on a daily basis?" . You can create channels that will use those streams. Like you said though they are random... Maybe a feature where we can do regex matching for streams? Dunno. I would have to look into that. The bigger questions is the EPG for these.....

[kjetilhp]

You could re-write the UI in anything you would like. The server is c# asp.net core and the frontend can be anything.

Great! Looking forward to your first release

[deku-m]

Is there also a docker version coming :)?

Good luck on the rewrite of the app. Looking forward to it.

[SenexCrenshaw]

Another piece that I was avoiding was any kind of dB for the backend. I am using flat jsons files for storage which added a lot of time in developing. After all of that I still might just go with sqlite.

I plan to only publish docker images for releases.

I use openapi v3 as well so creating clients for the api is very easy.

I'll get back to it and send an update in a week or so.

[aniel300]

ok am waiting on this