On Sun, 23 Jan 2022 at 07:47, Dennis Lee Bieber <wlfr...@ix.netcom.com> wrote: > If you are doing a web application, how are you going to host it? Who > is responsible for managing the web server? Domain name? Firewalls? > Certificates if you need HTTPS rather than plain insecure HTTP. > > I have a Raspberry-Pi with Nginx serving static pages over insecure > HTTP as I've never applied for a certificate -- using a dynamic DNS > service. It is not suited for high-demand as it is behind my ISP router, > and my uplink rate is only a tenth of my downlink rate (which isn't the > fastest thing out there to begin with [Ugh -- Hope it's the weather -- my > downlink is down to 10Mbps, when nominal is closer to 14Mbps]). Someday I > may try creating a Flask application for it, just for learning. >
Thanks to LetsEncrypt, certificates shouldn't be too hard for any public-facing server. The Pi can renew and install its own certificates in a 100% automated process, as long as you can continue receiving port 80 traffic as well as the port 443 that the live server would use. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
