+1 Think this is the right way to go. I'm working on the module now,
should have something to show within next couple days..
On Jul 24, 12:04 pm, Iceberg wrote:
> That way the developer need to implement a dedicate action, perhaps
> protected by authentication, to access log on WEB. It is reason
That way the developer need to implement a dedicate action, perhaps
protected by authentication, to access log on WEB. It is reasonable
for public site, but an overkill for small enterprise intranet app.
But there is no need to argue on this, man. We can have both. If Yarin
gonna implement a modul
I think the place for this stuff is "private". From a security point
of view log files should not by default be exposed to the public.
On Jul 24, 10:49 am, Iceberg wrote:
> Sorry I disagree. No need to take "static" literally. In web2py,
> "static" just means the content inside such directory wi
Sorry I disagree. No need to take "static" literally. In web2py,
"static" just means the content inside such directory will be served
directly by web2py core, unlike other "dynamic" content served by
app's controller. So it is nothing wrong to serve log file inside
"static", no to mention the bypro
about #3. I would prefer if this were written as a
gluon.contrib.logging module that users can import if needed.
On Jul 23, 2:02 pm, Iceberg wrote:
> Well done Yarin! Some comments.
>
> 1. Change those time_expire= into time_expire=None please. The clumsy
> trick was my early "i
Glad you like- I'd love to see this as part of the core. Let me know if
there's anything else I can do.
>I am not so keen to include the sqlite part because it is too specific
Is this because it requires the extra module? I kept it separate because
it's a Python, not web2py, specific class, but
Very good work. We should think about a way to include this in web2py
core.
I am not so keen to include the sqlite part because it is too specific
but:
I see the log.py file could go in contrib with minimal changes (it it
were implemented as a function that takes the request and cache obj
+1
notice that you can use expire_time=None to prevent cache from
expiring instead of
On Jul 23, 8:24 am, Yarin wrote:
> Added a slice: Application
> Logginghttp://web2pyslices.com/main/slices/take_slice/91
>
> It covers logging to both a file and SQLite. The code is well
> documented
Added a slice: Application Logging
http://web2pyslices.com/main/slices/take_slice/91
It covers logging to both a file and SQLite. The code is well
documented- use this instead of the previous code. Would love to get
your comments.
@Iceberg, btw apparently the SQLite cross-thread issues weren't s
Working on one now...
On Jul 22, 8:20 am, Massimo Di Pierro wrote:
> This is useful. I suggest making a web2py slice about this.
>
> Massimo
>
> On Jul 21, 2010, at 9:37 PM, Iceberg wrote:
>
>
>
> > Just a quick thought. Since web2py itself already handles SQLite db
> > well under multi-thread
This is useful. I suggest making a web2py slice about this.
Massimo
On Jul 21, 2010, at 9:37 PM, Iceberg wrote:
Just a quick thought. Since web2py itself already handles SQLite db
well under multi-thread situation, so a quick tweak to your
sqlitehandler.py may be putting the web2py db insta
By using web2py's default sqlite db, I was able to solve the
threading
issues(Thanks Iceberg)- however, for whatever reason the only record
being inserted
into the db is the initial one from log.py when logging gets
initiated. Any subsequent attempts to log from controllers don't
show
up in the db
By using web2py's default sqlite db, I was able to solve the threading
issues- however, for whatever reason the only record being inserted
into the db is the initial one from log.py when logging gets
initiated. Any subsequent attempts to log from controllers don't show
up in the db- no error, just
Disregard that last post I found it: web2py/applications/{app}/
databases/storage.sqlite
I used that and looks like it solved the threading issues! Thanks
Iceberg... testing now to see if I can get the whole thing working...
On Jul 21, 11:41 pm, Yarin wrote:
> @Iceberg, that seems like a really
@Iceberg, that seems like a really good idea but I'm not sure how I'm
supposed to do that- what is the 'web2py db instance'? An instance of
what? Or is it a path to a db file that already exists in the web2py
heirarchy? Could you possibly provide an example?
Thanks--
On Jul 21, 10:37 pm, Iceberg
Just a quick thought. Since web2py itself already handles SQLite db well under
multi-thread situation, so a quick tweak to your sqlitehandler.py may be
putting the web2py db instance, rather than a filename, to initialize your
SQLiteHandler() class.
Best regards,
Ice
16 matches
Mail list logo
