Logging problem solved! Finally!
Turns out it was just that web2py is using the file error.log for the wsgi
output, while apache (httpd) is using error_log. In case this helps anyone
else, on the homebrew version of httpd the log files are located in
/opt/homebrew/var/log/httpd
So my local ap
Okay, my one remaining problem is logging output. I'm using the default
logging settings for web2py, and it usually is output in the apache error
log. But nothing appears in the error log for my mac installation of apache
(homebrew version of httpd). The apache server notices are showing up ther
Thanks Massimiliano. I've used local Apache for years so that I can test
things like ssl and some routing that are done at the server level. But
I've always done it on Linux, and I'm learning that mac is quite different.
I've got mod_wsgi set up and working, but I think the issue may just be
t
Sorry I didn't notice that you use apache.
Can I ask you why?
In my dev machine I use the web2py internal server for simplicity.
Anyway have you setup uwsgi to use the right python?
Il giorno ven 23 dic 2022 alle ore 09:22 Massimiliano
ha scritto:
> How do you start web2py?
>
> Il giorno ven 23
How do you start web2py?
Il giorno ven 23 dic 2022 alle ore 03:39 Ian W. Scott
ha scritto:
> So it looks like it's a problem importing python modules. I'm using a
> virtualenv (pyenv) and web2py isn't finding the modules I installed for
> this version. There may be other issues too (since the lo
So it looks like it's a problem importing python modules. I'm using a
virtualenv (pyenv) and web2py isn't finding the modules I installed for
this version. There may be other issues too (since the logging isn't
working!) but this is something I can fix...
On Thursday, December 22, 2022 at 8:43
6 matches
Mail list logo
