Re: Pylons success story (IncidentNews)
Very cool! How did you implement the breadcrumbs? K On Jun 15, 3:48 pm, Mike Orr [EMAIL PROTECTED] wrote: My first Pylons site is in production now athttp://incidentnews.gov/. It's running the following: Pylons 0.9.6 dev r2009 Apache with ProxyPass Google Maps interface (done by my colleague) SQLAlchemy with MySQL Mako templates Christoph Haas's alternative paginator Beautiful Soup (to parse the glossary source file) Unipath (my own Path object) CSV access log (subclass of paste.translogger.TransLogger) paster daemonizer (will switch to supervisord but can't get it to launch the app) Linux Gentoo (switching to Ubuntu Server Edition soon) The data comes from a larger private site that's used for data entry. That site is Quixote but may be rewritten to Pylons later this year if this site succeeds. -- Mike Orr [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: Pylons success story (IncidentNews)
On Fri, Jun 15, 2007 at 03:48:07PM -0700, Mike Orr wrote: My first Pylons site is in production now at http://incidentnews.gov/ . It's running the following: Pylons 0.9.6 dev r2009 [...] Christoph Haas's alternative paginator Glad to hear that the paginator is production-ready. Thanks for the credit. :) Linux Gentoo (switching to Ubuntu Server Edition soon) Out of curiosity. Do you run on the stable Ubuntu release, do you use the unstable branch or do you put everything into a workingenv? Very nice site. pylons++! Cheers Christoph --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: Pylons success story (IncidentNews)
On Jun 15, 2007, at 6:48 PM, Mike Orr wrote: My first Pylons site is in production now at http:// incidentnews.gov/ . Cool; our[1] first Pylons app, BIANCA, goes into production on Monday at NASA HQ -- alas, it contains v. sensitive information, so it's not publicly available, but: Apache 2.2.3 w/ mod_python Pylons 0.9.5 -- with Routes from SVN (long story) Sesame RDF database Home-grown db abstraction lib Myghty templates -- moving to Mako for 2.0 release MochiKit, Scriptaculous, etc for datagrid tables AuthKit -- with homegrown account storage in sqlite using SQLAlchemy Solaris 10 Data comes from 4 sources in NASA HQ network operations, config change management, etc. For the 2.0 release, we'll be consuming information live from DNS, intrusion detection systems, HP OpenView, and various SNMP bits. Cheers, Kendall Clark [1] http://clarkparsia.com/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: Pylons success story (IncidentNews)
On 6/16/07, wongobongo [EMAIL PROTECTED] wrote:
How did you implement the breadcrumbs?
It's a pattern I've used for years. c.crumbs is a list of (url,
label) pairs for each link except the first (Home), which is always
shown. Most controllers can leave it at the default, []. Those that
are third-level put the second-level link in the list; those that are
fourth put the second and third in the list, etc. A special value
None suppresses the breadcrumbs completely.
Normally the last link would be the parent page, but the client
insisted on an additional non-clickable link for the current page, so
I implemented that with c.page_crumb.
=== lib/base.py
def __begin__(self):
c.crumbs = []
=== lib/helpers.py
def link(label, *url_for_args, **url_for_kw):
url = url_for(*url_for_args, **url_for_kw)
return link_to(label, url)
=== templates/site_mako.html
% if c.crumbs is not None:
${h.link(Home, home)}
% for url, label in c.crumbs:
gt;gt; ${h.link_to(label, url)}
% endfor url, label
% if c.page_crumb:
gt;gt; ${c.page_crumb}
% endif c.crumbs
It uses CSS classes for the coloring, but I'd have to look at the
source to remember which tags I used. :)
=== Most controller actions are top-level pages
# Leave c.crumbs at default.
=== An Entry page is third-level
c.crumbs = [(h.url_for(incident, orr_id=orr_id), Incident)]
=== A hypothetical fourth-level page
c.crumbs = [(second_url, Second Label), (third_url, Third Label)]
--
Mike Orr [EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~--~~~~--~~--~--~---
Re: Pylons success story (IncidentNews)
On 6/16/07, Christoph Haas [EMAIL PROTECTED] wrote: Out of curiosity. Do you run on the stable Ubuntu release, do you use the unstable branch or do you put everything into a workingenv? Currently it's an older Gentoo with Python 2.4. There's a workingenv for this site. My colleagues have convinced me that a separate workingenv for every site is a good idea, in case one site later needs a library upgrade that breaks (or might break) another site. The existing Quixote sites don't have workingenvs, however. I plan to switch to Ubuntu 7.04 (current), or possibly 6.06 (long-term support). But I have a spare server so it's no problem to upgrade one while the other is in production, so I'm leaning toward the former to get newer versions of things. My workstation is Kubuntu 7.04 with Python 2.5. I easy_install all Python packages required for a site into a workingenv. Sometimes I have trouble compiling packages that depend on C libraries (Python-MySQL, python-ldap), and for those I just use the OS package. But it's impossible to stick to OS packages completely if you use a lot of just-released or still-in-development Python libraries. -- Mike Orr [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
