Re: [fossil-users] milestone: libfossil CGI demo
On Sat, Feb 15, 2014 at 11:17 PM, Stephan Beal sgb...@googlemail.comwrote: The majority of the implementation is demonstrated in this script: http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/finfo?name=th1ish/cgi-init.th1ish Here's a more interesting example: http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/index.cgi/timeline?limit=101 which is implemented by this small script: http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/finfo?name=th1ish/pages/timeline.th1ish Happy Fossiling! -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] milestone: libfossil CGI demo
Is there an interface yet to the wiki? I have been wanting to change/add a few things. I want to add a full text search for wiki bodies. I guess I could look into adding that into normal fossil. Jonathan Otsuka On Feb 16, 2014, at 9:38 AM, Stephan Beal sgb...@googlemail.com wrote: On Sat, Feb 15, 2014 at 11:17 PM, Stephan Beal sgb...@googlemail.com wrote: The majority of the implementation is demonstrated in this script: http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/finfo?name=th1ish/cgi-init.th1ish Here's a more interesting example: http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/index.cgi/timeline?limit=101 which is implemented by this small script: http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/finfo?name=th1ish/pages/timeline.th1ish Happy Fossiling! -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] milestone: libfossil CGI demo
On Sun, Feb 16, 2014 at 8:34 PM, Jonathan Otsuka djg...@gmail.com wrote: Is there an interface yet to the wiki? I have been wanting to change/add a few things. There's a library interface for loading/storing wiki content: http://fossil.wanderinghorse.net/repos/libfossil/doxygen/fossil-content_8h.html#a47f91b6c7f68877b578a4cb20ed07fbd but not yet a script-side interface. libfossil also does not do fossil's wiki parsing - that will eventually be ported into a higher-level layer. I want to add a full text search for wiki bodies. The API gives you enough tools to fetch the contents of each version for your indexing purposes. i don't see an API for fetching historic versions of a page, but recently wrote an SQL query to fetch that history[1], so that feature's just a matter of time. I guess I could look into adding that into normal fossil. Doing a real-time search across all versions would (IMO) not be feasible, in terms of performance. Fetching historical versions of content is extremely memory hungry - it can easily cost a total of 100MB in de/re-allocations to fully resolve a small file's contents through the generations (peak memory is normally much lower). However, collecting and indexing the (immutable) data is not generically a problem. Indexing the wiki pages when they're saved would also be a good idea, and libfossil provides a callback hook which clients can use to be notified of artifacts being saved (which includes wiki pages). That could also be used to take it to the next logical step and index file content when it arrives. [1] = http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/finfo?name=sql/q-wiki-lineage.sql -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Painful team interaction with fossil, how to improve?
Le Thu, 13 Feb 2014 20:44:43 +0400, Justin Forest h...@umonkey.net a écrit : I wrote a Python script that helps myself deal with this. It looks at all tickets and emails all participants with all comments and changes since their last reaction. It also emails users specified in the responsible ticket field (which you can add in /tktsetup_tab), thus I can assign tickets to users and they get emailed without having to comment first. It also sends all changes to an email address specified in the FOSSIL_CC environment variable, for archiving purpose. I tried using the ticket hooks branch, but found it easier to just query the repository every 5 minutes with a cron job (also, this saves me from maintaining another web app that would handle the hook requests). I run the script on the same machine that Fossil databases are, so there are no performance or load issues. In case this sounds helpful, you can inspect the script here: http://code.umonkey.net/fossil-extras/file/tip/fossil-ticket-notify.py Or download it: http://code.umonkey.net/fossil-extras/raw-file/tip/fossil-ticket-notify.py That's awesome! Just what I needed. I actually only use the JSON API to get last tickets edits and send the change to a mailing list, but sending to ticket participants is what I was looking for, thanks! -- BohwaZ signature.asc Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
