Basically the ones listed https://httpd.apache.org/docs/current/mod/mod_ssl.html here which, after realising it's because I'm not using Apache locally, kind of leads me into another question. How do I access variables like these locally if I'm not running my app through Apache any more?
On Tuesday, May 26, 2020 at 10:53:28 PM UTC+1, Graham Dumpleton wrote: > > What SSL variable are you talking about? > > On 27 May 2020, at 3:59 am, Mitt Frag <[email protected] <javascript:>> > wrote: > > Hi Graham. Really sorry about the late reply here. I am missing a variable > related to SSL. I ran the app locally using 'python server.py' and the > output says it is running as a https server however the SSL variable that > is normally there isn't there in local development. I'm not sure if it's > related to the http requests I'm making from the frontend? I make the same > calls in production with the same protocol and I can see that SSL variable > though. > > On Friday, May 15, 2020 at 12:14:10 AM UTC+1, Graham Dumpleton wrote: >> >> If you are using Flask, you can run the Flask development server. This is >> a WSGI server still, and the per request WSGI environ should still be >> present. >> >> What in the WSGI environ are you expecting to see if you are already >> doing that and something isn't present? >> >> On 15 May 2020, at 6:54 am, Mitt Frag <[email protected]> wrote: >> >> I currently have a setup where my React client interacts with a Flask >> backend which is daemonized with WSGI through Apache. The problem I have >> now is that to develop this way I have to rebuild the client which can take >> 1-2 minutes each time, Apache then picks up the build files. The reason I >> am forced to do this is because I cannot run my main server.py file just >> via the command line via >> python server.py >> >> because this file now relies on request.environ() which I assume is >> exclusive to WSGI. Ideally, I would be able to run my React application in >> development mode (takes no time at all to start-up) and would be able to >> run my server.py file using WSGI locally as opposed to via daemonizing it >> via the Apache config. Is there a way I can run WSGI locally like this? >> From my initial research it seems that I might want to download >> modwsgi-standalone and then make use of modwsgi-express? >> >> >> You only need 'mod_wsgi-standalone' if for some reason you can use the >> system Apache (runtime+dev packages installed). If the system Apache exists >> (with those dev header files and apxs), then you can 'pip install mod_wsgi' >> to get mod_wsgi-express. In other words, the 'mod_wsgi-standalone' package >> also installs an Apache instance, which you don't need if you have system >> Apache installed anyway. >> >> Graham >> >> > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/modwsgi/c6bdbc08-7aad-41fb-952d-e342dea658b8%40googlegroups.com > > <https://groups.google.com/d/msgid/modwsgi/c6bdbc08-7aad-41fb-952d-e342dea658b8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi/e78de8ff-94f6-401d-a81b-2b74c459de56%40googlegroups.com.
