:D http://django-audit-log.readthedocs.org/en/latest/usage.html
On Sat, Jul 20, 2013 at 1:16 PM, Parin Porecha <[email protected]>wrote: > django-logtailer looks a great app, but the last commit was 2 years ago. > Also, it's focused on admins. > Maybe the term 'logs' is confusing. So, I'll change it to 'audit-data' ( > stackoverflow suggestion ). > I need audit data not system logs. > > Thanks Valder > > > On Sat, Jul 20, 2013 at 9:02 PM, Valder Gallo <[email protected]>wrote: > >> Do you know django-logtailer ? >> https://github.com/fireantology/django-logtailer >> >> If you don't need search or modify the data. >> >> +1 for file storage >> >> :D >> >> >> On Sat, Jul 20, 2013 at 11:52 AM, Parin Porecha >> <[email protected]>wrote: >> >>> Hi, >>> >>> I have a to-do list app ( using Django 1.5 and MySQL ) in which a task >>> can be shared with another user. Thus, a user can have personal tasks and >>> shared tasks. Shared tasks will be a fraction ( i guess around 30% of total >>> tasks of a user ) >>> >>> For shared tasks, I want to keep a log so that users connected to the >>> task can know who has done which changes. >>> For this, I'm thinking of keeping a log file for every shared task. >>> Whenever any user makes a change, it'll be appended to that file. >>> >>> My question is - *Should I do it via file storage, or should I save it >>> in database ?* >>> >>> Please note these points - >>> - Log will not be accessed frequently ( A file's log may be read 5-10 >>> times max in an hour. ) >>> - In an hour, there may be total >500 writes ( but for different files. >>> So for a file there may be 10-50 max writes in an hour. So, concurrency is >>> not a major issue. ) >>> - I won't need to search or modify the data anyway after reading it. >>> >>> Thanks in advance ! >>> >>> -- >>> Regards, >>> Parin Porecha >>> >>> say Kifflom! <http://www.epsilonprogram.com/kifflom.htm> and look >>> forward to 17.09.13 ! >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/django-users. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> >> -- >> Valder Gallo >> +55 11 9949 2911 >> +55 11 2532 2911 >> Skype: valdergallo >> @valdergallo >> www.valdergallo.com.br >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/django-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Regards, > Parin Porecha > > say Kifflom! <http://www.epsilonprogram.com/kifflom.htm> and look forward > to 17.09.13 ! > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Valder Gallo +55 11 9949 2911 +55 11 2532 2911 Skype: valdergallo @valdergallo www.valdergallo.com.br -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
