Migrating Web Apps - any interest?

[tvmaster2]

So great to to see you and others continuing to make Sage better still. Thanks!

[jusjoken]

In my testing I noticed the SJQ Web UI plugin was not compatible as it had a max SageTV version of V7 and was pointing to a location that does not exist. I have updated that plugin to use Github and allow use in V9 of SageTV.

Otherwise no other changes were made.

Initial review looks like the plugin also works under the new versions of the web UI and Jetty 9.

K

[wayner]

Awesome. SJQ was very powerful but I don't think all that many people used it. It was great for doing post-recording processing, like transcoding files, putting them into archive folders, snipping out commercials, etc.

[jusjoken]

A quick Christmas 2021 update....making good progress as follows...

• Jetty Starter - updated to Jetty 9.4.44 - Added HTTPS optional config - more detailed work to complete but works to allow me to test and update the other related apps
• SageTV Web Applications - lists and links to all web apps running on SageTV Jetty 9 server
• SageTV Web Interface - SkiingWiz has completed the update (as he is the current maintainer)
• SageTV Mobile Web Interface - updated to support Jetty9
• Media Streaming Services - used by Mobile Web Interface - updated to Jetty9 but still need to determine how this works and how to test
• SageTV Sagex API Extensions (sagex-api) - updated to Jetty9
• SageTV Sagex Remote API Services (sagex-services) - updated to Jetty9
• SageTV Swagger interface for Sagex remote api testing - updated to Jetty9 and newer swagger ui - tested with HTTPS and HTTP
• Batch Metadata Tools - Web Interface - updated to Jetty9 plus TMBD TV provider (more testing needed of TV provider)
• SageAlerts - source found (11 year old source) and updated to work with Jetty9
• SJQ - tested and works with Jetty9 - no changes needed so far
• SJQ Web UI - minor changes to allow to install with SageTV 9
• SRE - SkiingWiz updated to work with Jetty9 (minor changes)

All of the above plus likely some others that may be related will need to be released at the same time as Jetty 6 and 9 cannot run at the same time.

Continuing to work on this daily. Hopefully ready soon for some testers.... preferably on non-Production systems.

A special thanks to those supporting me on Patreon.

K

[MattHelm]

A quick Christmas 2021 update....

Thank you very much for all your hard work! Merry Christmas!

[trk2]

Much appreciated!

[Zogg]

Thanks for the updates, Ken!

[jusjoken]

So far my initial unraid testing using the stuckless docker java 11 template is working well (SageTV 9.2.5). Jetty 9 and the updated Web UI seem to all work well.

K

[jusjoken]

My testing with the Java 16 docker container is so far a FAIL. Although Jetty 9 runs fine, the Web UI main screen fails. Many of the Web UI functions work so it may be something simple to resolve but will need more investigation to know how big/small the issue is.

I will dig deeper to see if this is worth resolving at this time as it is also an issue with Jetty 6 so not sure I will delay the move to Jetty 9 for this.

K

[egeller]

Originally Posted by jusjoken

My testing with the Java 16 docker container is so far a FAIL. Although Jetty 9 runs fine, the Web UI main screen fails.

K

The issue may be that Javascript is a no-go in Java 16. I loaded the Java 16 version and ran it for a while. I reverted to Java 11 with more success. My Java 16 adventure uncovered something (I forget the details) in the Sage-to-Plex interface that quit working because a Javascript thing would not run.

My son is a front-end developer (my career was with databases and servers) and he said that Oracle et al. is killing Javascript.

[wayner]

Happy New Year to everyone, and if you haven't already, make sure that you have signed up to support jusjoken on Patreon, to thank him for keeping this alive!

[stuckless]

Originally Posted by egeller

The issue may be that Javascript is a no-go in Java 16. I loaded the Java 16 version and ran it for a while. I reverted to Java 11 with more success. My Java 16 adventure uncovered something (I forget the details) in the Sage-to-Plex interface that quit working because a Javascript thing would not run.

My son is a front-end developer (my career was with databases and servers) and he said that Oracle et al. is killing Javascript.

Just wanted to clarify "Oracle is killing Javascript". Oracle, starting with Java 9+ has been removing features of the core engine and putting them into modules or removing them totally (as in JavaScript support) and putting them into external libraries. You can still use JavaScript with Java 16, but the setup will need a new jar file and maybe some tweaks to the sagex scripting engine on how to load the engine. All in all, I don't think this would be hard thing to solve at the docker container level. (https://github.com/szegedi/nashorn/w...-Java-versions)

Side note and unrelated... I'm personally not happy with how Java has been evolving, but that's mainly because I've been with Java from 1.0 so I liked it the way it was. Oracle's changes are actually pretty good and maybe in the long run it will work out. But personally, I've all but abandoned Java and I've pretty much moved on to NodeJS (javascript).

[jusjoken]

See new thread for the release of the Jetty Webserver v3 release (with Jetty 9)

[tvmaster2]

Originally Posted by stuckless

Just wanted to clarify "Oracle is killing Javascript". Oracle, starting with Java 9+ has been removing features of the core engine and putting them into modules or removing them totally (as in JavaScript support) and putting them into external libraries. You can still use JavaScript with Java 16, but the setup will need a new jar file and maybe some tweaks to the sagex scripting engine on how to load the engine. All in all, I don't think this would be hard thing to solve at the docker container level. (https://github.com/szegedi/nashorn/w...-Java-versions)

Side note and unrelated... I'm personally not happy with how Java has been evolving, but that's mainly because I've been with Java from 1.0 so I liked it the way it was. Oracle's changes are actually pretty good and maybe in the long run it will work out. But personally, I've all but abandoned Java and I've pretty much moved on to NodeJS (javascript).

For those not as technically minded, how would this effect Windows 10 Sage server installations for example, going forward? Is this a death knell of sorts?

[jusjoken]

Originally Posted by tvmaster2

For those not as technically minded, how would this effect Windows 10 Sage server installations for example, going forward? Is this a death knell of sorts?

Should be a non event. SageTV server does not use Javascript at all...its only plugins like some of the webapps that are affected and only on Java 16+.

So right now we still have full web app support on Java 8 and 11, and we may be able to 'patch' the Java 16 issue if its worth the effort.

Hope that helps

K