Did you upgrade? If so, you most probably did it with root privileges... So
the permission should probably come from there, been change at the upgrade
time...
On Wed, Apr 13, 2016 at 9:06 AM, Leonel Câmara
wrote:
> Was appadmin being accessed? It uses admin for authentication by default.
>
> --
Was appadmin being accessed? It uses admin for authentication by default.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message becaus
So when these errors were occurring i saw about 20 error tickets per minute
being generated in the admin app. there was no traffic toward the admin
app at the time, any idea why that would happen?
On Wednesday, April 13, 2016 at 3:27:21 AM UTC-4, Niphlod wrote:
>
> there's none. admin is an app
there's none. admin is an application by itself.
On Tuesday, April 12, 2016 at 9:54:08 PM UTC+2, Jason Solack wrote:
>
> It's running in linux with apache/WSGI, i'm not exactly sure what you are
> asking, how are we launching web2py?
>
> Just to be clear, we're looking into how the permissions wh
It's running in linux with apache, i'm not exactly sure what you are
asking, how are we launching web2py?
On Tuesday, April 12, 2016 at 3:33:51 PM UTC-4, Niphlod wrote:
>
> every process that is running the web2py app should have permissions to
> read and write into the web2py folder.
> if a se
every process that is running the web2py app should have permissions to
read and write into the web2py folder.
if a sessions folder isn't found when the first request hits the app,
web2py creates it, but it does so under the current security environment...
Whoever is changing the permissions is
6 matches
Mail list logo
