vince <[email protected]> writes:

> On Wednesday, November 20, 2019 at 9:27:02 PM UTC-8, Radek Dohnal wrote:
>
>> What is the safe way how to use public webpage with my meteo data (on 
>> public site) together with weex sending MQTT data on my local home network ?
>> I would like to use MQTT from my weewx (running on my home network). But I 
>> dont wont to open any port from my home network to the internet.
>> Now Im using FTP to transfer data (HTML_ROOT folder from my local RaspPI 
>> where weewx runnig) to public site where i rent a space for my webpages. 
>> But without MQTT.
>
> It depends on whether you want realtime MQTT-based data (ie, enabling the 
> realtime-ish side of Belchertown).

Indeed, I did not get this point in the question.  Adding local mqtt
does not affect the remote skin at all.

> If you want realtime MQTT data it gets more complicated. As Greg said, 
> you'd have to run a MQTT broker on your public webserver.  'Definitely' set 
> that up to be password-protected on the Internet.   Also agree with Greg 
> that you can have your LAN MQTT broker forward to your Internet one pretty 
> easily.

I don't follow "password-protected" entirely.  As I see it (but haven't
done it):

  you have html someplace for the skin, and it may or may not have a
  password.  Typically these do not have access control.

  The javascript from the skin has to talk to an mqtt broker that has
  the data.  So one has choices (assuming one is writing code):

    1) let the mqtt data be accessible without a password

    2) use a static username/password and put it in the skin.  This is
    sort of like an API key in web parlance.

    3) some scheme of new username/passwords in each page view from the
    skin

I suspect most people running skins that get live mqtt data are doing
option 1, that almost all readers think option 3 is nuts, and that zero
people are doing it.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/rmisgmhkx96.fsf%40s1.lexort.com.

Reply via email to