Paul Webster wrote: > That is what I do for my own set-up. > I went down that route early on because I didn't want to have to redo > the ngrok initialisation each time I (rarely) restarted the server and I > didn't want to buy an ngrok service because I was not really sure that I > would need it. > So ... I run it over nginx with a letsencrypt cert (I even helped > resolve an issue with one of the renewal scripts - > https://gist.github.com/Greelan/28a46a33140b65c9a045573ca460f044#gistcomment-3140115 > ) > > However, when Phil came up with the automatic updater mechanism that > meant that the ngrok free service could be used without having to > re-enter authentication information which makes that route much easier. > I came up with some small changes to the Python script and Phil made > some more in the script and back-end and it became even better. > > > Take a look at the "Don't forward" thread from mherger > https://forums.slimdevices.com/showthread.php?107165-IMPORTANT-Stop-forwarding-your-LMS-ports-to-the-internet
I'd muse that setting up ngrok without the pCP limitations is a breeze compared to getting certs and DNS names and opening router ports. Plus, an ngrok installation is portable. Take @mecouc who wants to send off a pre-installed pi to his parents. No need to open ports on his parents' router as ngrok will happily tunnel its way outwards from any network. That would not 'just work' with an apache/nginx approach. ------------------------------------------------------------------------ philchillbill's Profile: http://forums.slimdevices.com/member.php?userid=68920 View this thread: http://forums.slimdevices.com/showthread.php?t=111016 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
