Closed TPeterson94070 closed 9 months ago
Sure. We can always dig it out of source control if we need it.
Do you want to make the snip? If not, please point me to the place.
I can do this one.
This is the commit where this was added 31cc4be. It's probably ok to just remove the server startup and leave the file in the code base.
Okay, thanks, after you've done that I will pull down a refresh from the Repository and generate a new CWHelper so that I can unleash the latest and greatest on our beta test guys.
That should do it. I left the TinyWebServerSecure in source control, but noted it wasn't active.
Great! Thanks, I'll gin up a new beta test package for the gang.
Change has been merged to master branch.
Since it turned out that there's no royal road to setting up an https server on the private LAN, I've moved on to looking at stashing the csv files for CW_EPG_Remote in the user's Google Drive folder instead of fetching them from the app data folder. That means that the second server that you set up, intended to become SSL protected, isn't needed.
Can we just drop it?