itjedi42
commented
1 week ago As far as dynamic parameters, I hadn't thought about them. You are welcome to make additions/tweaks. Just PR it back. I am all for improving it! My whole goal with this was to make all the bits to secure people's Emby installs easier and less scary. There's a lot of stuff I want to add to it. Especially for increasing the level of "set it and forget it".
I plan to (when life gives me the free time) add functionality to give it a proper WinForms GUI. Make it so all they have to do is double click it. It can invoke request to elevate when needed. Give the UI check boxes to make it easier for the less tech savvy peeps.
Which is also useful to give options for peeps just wanting the reverse proxy bits, or if they want to do the whole thing. Options for doing things like adding a scheduled task to restart server service at a particular time/day; checking for and or installing updates automatically; option to install the email-relay software and config it, would allow for email notifications; option to add additional headers like CSP, etc.
Hi, apologies for not responding sooner - I retired from Microsoft in July and have spent most of the time since travelling.
I'd like to add the option to take an existing Emby install which is not exposed to the internet and verify/install the PreReqs, setup IIS reverse proxy and Certify the Web.
My primary reason for this message is to ask if you deliberately chose to not use dynamic parameters? If so, I get that they can be confusing for novices; we used them in many of our build scripts on the Windows team, mostly without problems except when new team members tried to use them, but they are particularly useful at enforcing rules on parameter combinations, hence my reaching out to ask your preference?
Kind regards Gary