On 17 December 2013 16:09, Olemis Lang <[email protected]> wrote: > On Mon, Dec 16, 2013 at 10:10 AM, Saint Germain <[email protected]> wrote: > >> On 16 December 2013 15:58, Olemis Lang <[email protected]> wrote: >> > On Mon, Dec 16, 2013 at 9:51 AM, Saint Germain <[email protected]> >> wrote: >> > >> >> On 16 December 2013 15:30, Olemis Lang <[email protected]> wrote: >> >> >> I just want to show bloodhound output pages on project menus on my >> web >> >> app. >> >> >> >> >> > Beyond comments above there's code developed by Google Summer of Code >> >> > student Antonia Horincar which is about embedding BH content in >> external >> >> > web sites. I do not know whether it's been committed into /trunk >> though . >> >> > >> >> >> >> Ok that doesn't help you too much with RoR integration, but if it may >> >> help others: >> >> If the point is just to integrate Bloodhound in a website without >> >> interacting with it (except for user authentication), I have >> >> successfully integrate Trac and Bloodhound with a Django website using >> >> WSGI. >> >> The only tricky part is to have a different templating system for >> >> Django app and Trac/Bloodhound. >> >> >> > >> > Have you considered this plugin (... or alike ...) ? >> > >> > http://trac-hacks.org/wiki/TracWsgiPlugin >> > >> >> No I am calling Trac/Bloodhound almost directly through WSGI. >> To be honest I didn't try to understand too much how this WSGI was >> working, it just worked so I was happy. ;-) >> > > There is yet another way to get this done *IF* your app's request > dispatching is powered by Routes framework . In Bloodhound Labs plugin [1]_ > we have implemented a web bootstrap handler that dispatches requests to > products/global envs based on routes definitions. Therefore you could add > your web app's routes in there e.g. using sub-mappers . >
Hello Olemis, I implemented the website with Django standard architecture. Bloodhound is merely considered as a Django app in this architecture. So I use standard Django URL dispatcher and not the Routes framework: https://docs.djangoproject.com/en/dev/topics/http/urls/ The advantage is that it integrates quite smoothly. The disadvantage is maybe performance (don't know, I haven't paid much attention to performance until now). Thanks for the info though !
