[pylons-devel] Re: github pages for pylons project sites
Obviously the owner of pylonshq.com never pointed the site to the right address. If someone is able to reach him please tell him to point to the marketing.pylonsproject.org IP. On Monday, January 4, 2016 at 1:10:36 PM UTC-5, Jonathan Vanasco wrote: > > I just wanted to add that PylonsHQ redirects to PylonsProject (and is the > name of the github project), and that link should be maintained. > -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at https://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
Re: [pylons-devel] github pages for pylons project sites
Sure, the initial setup is pretty simple, Linode VPS running Ubuntu 14.04 with latest Nginx-stable. A pylons user, with public user keys for site publishing, responsible to publish via pushing master branch to prod deployment, and probably dev branch for dev deployment. The setup will be done this weekend, so expect to have it in place early next week. I've created a Pylons account on Linode so we can have multiple to access the console and DNS, it's not tied to me. As soon as I'm done I'll share with all responsible people the informations, and then we'll just have to write down some procedure and workflow about this. On Saturday, January 2, 2016 at 4:54:28 PM UTC-5, Michael Merickel wrote: > > Okay, I was unaware of any on-going changes on the sites which is a little > silly for someone with my level of involvement in the project. > > Blaise, could you please explain the setup you are currently working on - > including a timeline, what websites it will affect, how team members will > be able to use it and what will happen when you are hit by a bus? > > I'm happy to withdraw my github pages proposal if we have something that > works well but I was unaware anything was actually happening! This is > something I'd like to help with, especially with regards to the actual > hosting configuration. > > - Michael > > > On Sat, Jan 2, 2016 at 3:33 PM, Blaise Laflamme <bla...@laflamme.org > > wrote: > >> Contributor should be able to compile and see their own changes before >> they submit PRs, and we should do the same when reviewing. The dev branch I >> was proposing earlier was to help us merging PR and make sure we don't >> publish unfinished work on master. >> >> On Saturday, January 2, 2016 at 4:28:29 PM UTC-5, Steve Piercy wrote: >>> >>> On 1/2/16 at 3:11 PM, mmer...@gmail.com (Michael Merickel) pronounced: >>> >>> >Hey everyone, I'm starting the discussion (which I hope is very quick) >>> >about what to do with our public websites. >>> > >>> >Right now we have: >>> > >>> >- docs.pylonsproject.org (docs, hosted on rtd) >>> >- docs.pylonsproject.org/projects (hosted on rtd) >>> >- www.pylonsproject.org (ppo, hosted somewhere controlled by >>> blaise/ben) >>> >- trypyramid.com (tpc, hosted somewhere I have no idea) >>> >- webob.org (hosted somewhere I have no idea) >>> >- docs.webob.org (hosted on rtd) >>> > >>> >I think Blaise is the only person with access to DNS configurations but >>> I'm >>> >not really sure. >>> > >>> >I'd like to propose moving several sites over to github pages for >>> easier >>> >management and update the DNS records with CNAME records to the github >>> >pages sites. All of the sites are static and it would allow master to >>> be >>> >always live, as well as control deployment permissions via the standard >>> >github.com/Pylons membership levels. >>> > >>> >The sites I'd like to see updated are: >>> > >>> >- www.pylonsproject.org >>> >- trypyramid.com >>> >- webob.org >>> > >>> >Can anyone give me a reason to not go this route? >>> >>> +1, but with a concern for the non-doc/HTML-only/marketing >>> sites. How do we preview proposed changes with as much ease as >>> deploying to a production environment? >>> >>> Taking trypyramid.com as an example, I could set up a CNAME of >>> trypyramid.stevepiercy.com, and point it at a particular branch >>> of stevepiercy/tpc before submitting a PR to Pylons/tpc. But >>> this would raise a bar for new individual contributions. >>> >>> Perhaps we declare a branch 'dev' or 'staging' for reviewing >>> proposed changes, and set up a CNAME for each marketing website? >>> >>> --steve >>> >>> >>> Steve Piercy, Soquel, CA >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "pylons-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to pylons-devel...@googlegroups.com . >> To post to this group, send email to pylons...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/pylons-devel. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at https://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
Re: [pylons-devel] github pages for pylons project sites
You're right, we definitely need this. On Saturday, January 2, 2016 at 4:54:18 PM UTC-5, Steve Piercy wrote: > > OK, so we need to set that expectation in a contributing.md > document for the repo. We cannot assume that contributors know > our process when it's not documented for a given repo. > > GitHub uses contributing.md: > > https://help.github.com/articles/setting-guidelines-for-repository-contributors/ > > > Example from another Pylons Project: > https://github.com/Pylons/pyramid/blob/master/contributing.md > > I've logged an issue for trypyramid.com: > https://github.com/Pylons/tpc/issues/35 > > --steve > > > On 1/2/16 at 1:33 PM, bla...@laflamme.org (Blaise Laflamme) > pronounced: > > >Contributor should be able to compile and see their own changes > >before they submit PRs, and we should do the same when > >reviewing. The dev branch I was proposing earlier was to help > >us merging PR and make sure we don't publish unfinished work on master. > > > > > Steve Piercy, Soquel, CA > > -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at https://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
[pylons-devel] Re: github pages for pylons project sites
Those three sites are on a Rackspace VPS badly organized and using their Cloud DNS. I'm in the process of migrating them over a Linode (we got sponsorship) VPS + DNS configured to publish via a githook for people who'll have access to do it: for now me, steve and goodwill. Those sites are static for now but would probably need compiling on publishing soon and probably add more stuff behind sooner than later. For sure we can go the Github page route but while in the process of migrating them I think it's preferable to have more options at hand with the VPS than making sure we have no other possibilities than static sites. On Saturday, January 2, 2016 at 4:12:04 PM UTC-5, Michael Merickel wrote: > > Hey everyone, I'm starting the discussion (which I hope is very quick) > about what to do with our public websites. > > Right now we have: > > - docs.pylonsproject.org (docs, hosted on rtd) > - docs.pylonsproject.org/projects (hosted on rtd) > - www.pylonsproject.org (ppo, hosted somewhere controlled by blaise/ben) > - trypyramid.com (tpc, hosted somewhere I have no idea) > - webob.org (hosted somewhere I have no idea) > - docs.webob.org (hosted on rtd) > > I think Blaise is the only person with access to DNS configurations but > I'm not really sure. > > I'd like to propose moving several sites over to github pages for easier > management and update the DNS records with CNAME records to the github > pages sites. All of the sites are static and it would allow master to be > always live, as well as control deployment permissions via the standard > github.com/Pylons membership levels. > > The sites I'd like to see updated are: > > - www.pylonsproject.org > - trypyramid.com > - webob.org > > Can anyone give me a reason to not go this route? > > - Michael > -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at https://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
Re: [pylons-devel] github pages for pylons project sites
-trypyramid.com -webob.org we'll have to redo a base for pylonsproject.org since it's a crappy pyramid app atm, but we could have something quick for the better. On Saturday, January 2, 2016 at 5:22:45 PM UTC-5, Michael Merickel wrote: > > Which websites are you planning to affect in the short term? Is it the 3 I > originally listed? I expect Bert will be happy if webob.org is on the > list. > > On Sat, Jan 2, 2016 at 4:03 PM, Blaise Laflamme <bla...@laflamme.org > > wrote: > >> Sure, >> >> the initial setup is pretty simple, Linode VPS running Ubuntu 14.04 with >> latest Nginx-stable. A pylons user, with public user keys for site >> publishing, responsible to publish via pushing master branch to prod >> deployment, and probably dev branch for dev deployment. >> >> The setup will be done this weekend, so expect to have it in place early >> next week. >> >> I've created a Pylons account on Linode so we can have multiple to access >> the console and DNS, it's not tied to me. >> >> As soon as I'm done I'll share with all responsible people the >> informations, and then we'll just have to write down some procedure and >> workflow about this. >> >> >> On Saturday, January 2, 2016 at 4:54:28 PM UTC-5, Michael Merickel wrote: >>> >>> Okay, I was unaware of any on-going changes on the sites which is a >>> little silly for someone with my level of involvement in the project. >>> >>> Blaise, could you please explain the setup you are currently working on >>> - including a timeline, what websites it will affect, how team members will >>> be able to use it and what will happen when you are hit by a bus? >>> >>> I'm happy to withdraw my github pages proposal if we have something that >>> works well but I was unaware anything was actually happening! This is >>> something I'd like to help with, especially with regards to the actual >>> hosting configuration. >>> >>> - Michael >>> >>> >>> On Sat, Jan 2, 2016 at 3:33 PM, Blaise Laflamme <bla...@laflamme.org> >>> wrote: >>> >>>> Contributor should be able to compile and see their own changes before >>>> they submit PRs, and we should do the same when reviewing. The dev branch >>>> I >>>> was proposing earlier was to help us merging PR and make sure we don't >>>> publish unfinished work on master. >>>> >>>> On Saturday, January 2, 2016 at 4:28:29 PM UTC-5, Steve Piercy wrote: >>>>> >>>>> On 1/2/16 at 3:11 PM, mmer...@gmail.com (Michael Merickel) >>>>> pronounced: >>>>> >>>>> >Hey everyone, I'm starting the discussion (which I hope is very >>>>> quick) >>>>> >about what to do with our public websites. >>>>> > >>>>> >Right now we have: >>>>> > >>>>> >- docs.pylonsproject.org (docs, hosted on rtd) >>>>> >- docs.pylonsproject.org/projects (hosted on rtd) >>>>> >- www.pylonsproject.org (ppo, hosted somewhere controlled by >>>>> blaise/ben) >>>>> >- trypyramid.com (tpc, hosted somewhere I have no idea) >>>>> >- webob.org (hosted somewhere I have no idea) >>>>> >- docs.webob.org (hosted on rtd) >>>>> > >>>>> >I think Blaise is the only person with access to DNS configurations >>>>> but I'm >>>>> >not really sure. >>>>> > >>>>> >I'd like to propose moving several sites over to github pages for >>>>> easier >>>>> >management and update the DNS records with CNAME records to the >>>>> github >>>>> >pages sites. All of the sites are static and it would allow master to >>>>> be >>>>> >always live, as well as control deployment permissions via the >>>>> standard >>>>> >github.com/Pylons membership levels. >>>>> > >>>>> >The sites I'd like to see updated are: >>>>> > >>>>> >- www.pylonsproject.org >>>>> >- trypyramid.com >>>>> >- webob.org >>>>> > >>>>> >Can anyone give me a reason to not go this route? >>>>> >>>>> +1, but with a concern for the non-doc/HTML-only/marketing >>>>> sites. How do we preview proposed changes with as m
Re: question about design decision on pyramid's core
you're about t reverse-engineer mcdonc's brain... be careful ;) On Wednesday, 27 March 2013 14:10:42 UTC-4, Jonathan Vanasco wrote: thanks. makes sense. i'm just trying to reverse engineer some templating flowthroughs. most other things were logically grouped together. -- You received this message because you are subscribed to the Google Groups pylons-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: how are the pyramid docs managed ?
No the new theme is not online, I've been just playing with different ideas before starting the public project. The current theme is here: https://github.com/Pylons/pylons_sphinx_theme Do you attend pycon this year? On Saturday, 9 February 2013 13:56:42 UTC-5, Jonathan Vanasco wrote: On Feb 8, 3:46 pm, Blaise Laflamme bla...@laflamme.org wrote: Hi jonathan, feel free to modify the sphinx theme and send a pull request. Actually older versions like 1.1, 1.2, etc, are not out-of-date but up-to-date with those versions. There are the latest and the development one that reflects the current stable and development versions of Pyramid. A mention to point to other versions would be good, I'm also working on a new theme that would include this information, and others tricks, but it's not ready ;) I hope to use the pycon sprints to work on this. is the new theme online anywhere ? i'm largely concerned with SEO tricks and just some visual cues going oh hey, this is/might be out-of-date. For example, if I search for pyramid.request on a major engine, I get a mix of -latest and 1.x docs. What I'm thinking might work is this... - since the theme is an external repository, have it reference back to the pyramid/master ( hopefully that wont have a recursion issue? otherwise to another repo ) to check what the current master/latest and legacy versions are - docs would contain , at the header, a note like this: you are viewing the most current Pyramid docs, for the 1.4 branch. if using an earlier branch, please click here. you are viewing the legacy Pyramid docs, for the 1.0 branch. if you are using a new branch, please click here. ( basically a better version of this page : http://httpd.apache.org/docs/1.3/ ) - every page would also contain a link to the /latest branch, to push up the internal pagerank for the domain - all the versioned docs push a link rel=canonical href=/latest/ using that, we should effectively eliminate all of the 1.x items from google/yahoo/bing search , and everything will point to /latest ... with the per-version docs easily accessible -- You received this message because you are subscribed to the Google Groups pylons-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: how are the pyramid docs managed ?
Hi jonathan, feel free to modify the sphinx theme and send a pull request. Actually older versions like 1.1, 1.2, etc, are not out-of-date but up-to-date with those versions. There are the latest and the development one that reflects the current stable and development versions of Pyramid. A mention to point to other versions would be good, I'm also working on a new theme that would include this information, and others tricks, but it's not ready ;) I hope to use the pycon sprints to work on this. On Friday, 8 February 2013 12:09:27 UTC-5, Jonathan Vanasco wrote: what controls how the pyramid docs get built and stored onto doc.pylonsproject ? looking at the github source ( https://github.com/Pylons/pyramid/tree/master/docs ) it looks to me like only the current docs are in master, and the older ones are built off misc releases the reason why i ask, is that i wanted to try and patch the templates to add some SEO tricks and also an alert box that appears on specific version branches, and lets people know that the docs are ( or may be ) out of date -- and pointing to the latest release. i've referenced out-of-date docs a few times from search engines myself, and i've seen many others with the same issues. would love to stop it. -- You received this message because you are subscribed to the Google Groups pylons-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Why is there a separate pyramid_chameleon repository?
You mean removing the repo? I don't think... Github repos are not only reflecting the current working state but also work in progress. Stable documentation reflects the current working state, I consider people visiting github repos as more advanced user looking at more than just stable stuff. If we decide to drop those projects from happening then yes we can remove them, not before. On Sunday, 20 January 2013 10:52:48 UTC-5, Tshepang Lekhonkhobe wrote: On Sunday, January 20, 2013 3:34:05 PM UTC+2, Chris McDonough wrote: On Sun, 2013-01-20 at 00:32 -0800, Tshepang Lekhonkhobe wrote: When I saw https://github.com/Pylons/pyramid_chameleon, I thought it's a dependency of Pyramid, only to find that it's been integrated into Pyramid itself. Why is it there? It was created at a sprint with the idea that we were going to eventually move Chameleon support out of the core but we never pulled the trigger. Unclear whether we ever will. To avoid this sort of confusion, and to represent reality, do you mind simply removing it? -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/RdCblgn92jsJ. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: Sites using Pyramid Pyramid Advocacy
I think for now we need an easy way to share assets, lets say something like a Dropbox folder? On Wednesday, 24 October 2012 18:34:52 UTC-4, Iain Duncan wrote: Thanks guys. I'm thinking what is necessary in the long run is for there to be some kind of app/page up that makes it super easy for someone to submit their site. Should this go to a pylons address, or do you guys want me to just stick something up that encourages people to email me the description and logo for now? thanks Iain On Wed, Oct 24, 2012 at 7:07 AM, Thomas G. Willis tom.w...@gmail.comjavascript: wrote: Cool. Just sent it to you. On Monday, October 22, 2012 7:58:04 PM UTC-4, Iain Duncan wrote: Right, well I'll start collecting them then. Can you send it to idu...@xornot.com javascript:? Chris, what's the easiest way for me to edit a page on the Pylons site to have a preamble and include my email address for people to send their links to? thanks Iain On Sat, Oct 20, 2012 at 5:27 AM, Thomas G. Willis tom.w...@gmail.comjavascript: wrote: I work for Batterii(http://batterii.com) we have a managed innovation solution written in pyramid and ember.js on top of google appengine. We actually have happy customers using it. I had sent someone our logo about a year ago for inclusion on the pylons site but it's still not up there. Ember.js on the other hand included the logo fairly quickly. On Friday, October 19, 2012 9:30:24 PM UTC-4, Blaise Laflamme wrote: I think this should be added to the new pylons project / pyramid sites refactoring. Noted. If you have anything collected please share. On Friday, 19 October 2012 17:33:15 UTC-4, Iain Duncan wrote: Hi everyone, I started a thread about this ages ago, and expressed interest in making something happen, and then life happened and I had not time. Now I'm in a position where this has become a higher priority again. It seems to me that one thing really lacking in the Pyramid docs is some advocacy and examples of high profile sites using Pyramid. I realize this is a bit non-sensical in that we're not talking about a CMS, but I'm sure I'm far from the only one who has had a client ask about that. Plone and SQLAlchemy have done a great job of it. So questions: - sites using Pyramid? is there a list anywhere? - If I want to help make one, what would be the recommended way of going about this? -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/** msg/pylons-devel/-/**sUw3kubem4EJhttps://groups.google.com/d/msg/pylons-devel/-/sUw3kubem4EJ . To post to this group, send email to pylons...@googlegroups.comjavascript: . To unsubscribe from this group, send email to pylons-devel...@** googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/** group/pylons-devel?hl=enhttp://groups.google.com/group/pylons-devel?hl=en . -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/inaxx9ZRzIYJ. To post to this group, send email to pylons...@googlegroups.comjavascript: . To unsubscribe from this group, send email to pylons-devel...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en. -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/4aGoTQT9nTIJ. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: Sites using Pyramid Pyramid Advocacy
In fact the site is at https://github.com/Pylons/pylonshq pylonsrtd is the sphinx doc frontend for our full set of docs. Best would probably be to collect them somewhere with logos in png+transparency at a good size, like 600px wide. I'll be sprinting o the new website at pylonsca on nov 12-13. On Monday, 22 October 2012 20:13:56 UTC-4, Chris McDonough wrote: On 10/22/2012 07:58 PM, Iain Duncan wrote: Right, well I'll start collecting them then. Can you send it to idu...@xornot.com javascript: mailto:idu...@xornot.com javascript:? Chris, what's the easiest way for me to edit a page on the Pylons site to have a preamble and include my email address for people to send their links to? The source of the site is on github. I think this is it: https://github.com/Pylons/pylonsrtd - C thanks Iain On Sat, Oct 20, 2012 at 5:27 AM, Thomas G. Willis tom.w...@gmail.comjavascript: mailto:tom.w...@gmail.com javascript: wrote: I work for Batterii(http://batterii.com) we have a managed innovation solution written in pyramid and ember.js on top of google appengine. We actually have happy customers using it. I had sent someone our logo about a year ago for inclusion on the pylons site but it's still not up there. Ember.js on the other hand included the logo fairly quickly. On Friday, October 19, 2012 9:30:24 PM UTC-4, Blaise Laflamme wrote: I think this should be added to the new pylons project / pyramid sites refactoring. Noted. If you have anything collected please share. On Friday, 19 October 2012 17:33:15 UTC-4, Iain Duncan wrote: Hi everyone, I started a thread about this ages ago, and expressed interest in making something happen, and then life happened and I had not time. Now I'm in a position where this has become a higher priority again. It seems to me that one thing really lacking in the Pyramid docs is some advocacy and examples of high profile sites using Pyramid. I realize this is a bit non-sensical in that we're not talking about a CMS, but I'm sure I'm far from the only one who has had a client ask about that. Plone and SQLAlchemy have done a great job of it. So questions: - sites using Pyramid? is there a list anywhere? - If I want to help make one, what would be the recommended way of going about this? -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/sUw3kubem4EJ. To post to this group, send email to pylons...@googlegroups.comjavascript: mailto:pylons...@googlegroups.com javascript:. To unsubscribe from this group, send email to pylons-devel...@googlegroups.com javascript: mailto:pylons-devel%2bunsubscr...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en. -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/XLVbkgMK3v4J. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: pylonsproject.org: 502 Bad Gateway
Should be online now On Thursday, 5 July 2012 16:45:38 UTC-4, Robin Gloster wrote: Hi, http://www.pylonsproject.org/ is raising a 502 Bad Gateway atm. Robin -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/3Nj3MUrVCP0J. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: suggestion for scaffolds
Good point... I'm currently rewriting the scaffold theme and hope to have it done before 1.3 release -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/LKMYM6R4kpMJ. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: web2pyramid
Hi Massimo, sorry for being late I was traveling yesterday and was off the net. I'm the one responsible of that small project and the design was bought on themeforest.net at a pretty cheap price, you should look at the license to know it's restrictions. However doing a similar design is not a big job ;) Here's the link http://themeforest.net/item/booster-product-focused-html5-landing-page/179207 -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/EuT4nAno7vwJ. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: Pyramid for Humans tutorial at Plone Conf...any reviewers?
Hi paul, I'm also interested in reading your material. -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/nTdKfhKKHdIJ. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: Logging configuration
using a run.wsgi fle like this one at the trot of your project will do want you want with modwsgi, http://docs.pylonsproject.org/projects/pyramid_exclog/dev/#deployment-under-mod-wsgi -- You received this message because you are subscribed to the Google Groups pylons-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-devel/-/2f536wsO9OsJ. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: Access to matchdict on locale_negotiator
You can use a custom predicate in your routes to set
request.locale_name, try something like:
def langs(info, request):
lang = info['match'].get('lang')
if lang:
request.locale_name = lang
return True
return False
and add route:
config.add_route('place', '/{lang}/place', custom_predicates=(langs,))
Hope this helps,
Blaise
On Aug 9, 3:33 pm, Juan Pizarro jpiza...@doingit.cl wrote:
Hello,
My name is Juan Pizarro, from Chile.
I'm working to migrate a app form pylons to pyramid, i use mako and
the locale is based on URL, example /{lang}/place/{id}.
The problem is, I can't access to the request.matchdict on
locale_negotiator, there aren't exist,
The solution was to setup the locale_name in a suscriber on
pyramid.events.BeforeRender, like
request.locale_name = request.matchdict['lang'] if 'lang' in
request.matchdict else None
I don't know if this is a good option, but works.
I don't know if is a bug or pyramid was designed for setup matchdict
after locale_negotiator.
Bye
--
You received this message because you are subscribed to the Google Groups
pylons-devel group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
ConFoo 2012: Call for Presenters (CFP)
Dear Pyloneers, The 3rd edition of ConFoo, an international conference on Web technologies, will be held in Montreal from February 29th to March 2nd 2012. http://confoo.ca/en ConFoo addresses several aspects of the Web and covers many languages (PHP, Python, Ruby, .Net, Java). ConFoo is a conference for developers, managers and any stakeholder in the Web technology industry. You rock the world with your mad Pyramid skills? Develop some awesome plugin or contribute on core kickass functionalities? You tame most Web development problems with a whip made of Python leather? You have what's needed to encourage Montréal's Web developers to rise from their royal tomb and enter a new millenium of glory! Reveal to Montrealers the very power of Python by submitting your talk proposal before September 2nd. Act fast and get to dance to the beat of the host city of PyCon 2014 before everyone else. For more information : http://confoo.ca/en/news/confoo-2012-call-for-papers-is-now-open ConFoo is a collaborative pursuit of local user groups in their quest to see the Web reach new heights. -- You received this message because you are subscribed to the Google Groups pylons-devel group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: Sub-optimal top paragraph on pylonsproject.org
Hi and thanks for your suggestions. We're currently remodelling, redesigning and reorganizing the current website so any input is welcome. There is already a basis for a new design, however we're actually more in the information architecture phase. If you want to contribute I propose joining us on pylonshq wiki - https://github.com/Pylons/pylonshq/wiki/New-pylonshq.com, I'll shortly create a new project for the new website and will move stuff there. Blaise On Jul 20, 4:55 am, Chris McDonough chr...@plope.com wrote: On Wed, 2011-07-20 at 01:52 -0700, Eric Ongerth wrote: Quote from the currenthttp://pylonsproject.org: The Pylons Project was founded by the people behind the Pylons web framework to develop web application framework technology in Python. Rather than focusing on a single web framework, the Pylons Project will develop a collection of related technologies. The first package is the Pyramid web framework. It's factual, but a little clunky and indirect. May I propose a rewrite, maybe something like the following? The Pylons Project develops web application framework technology in Python. Our primary offering is known as Pyramid. Our previous framework was called Pylons. Pyramid is a unification of the Pylons framework with repoze.bfg, providing a superset of the capabilities of both. (or replace that final sentence in any way that seems fitting.) I'm thrilled to take any docs contribution; the best way is via pull request. - C There's just something about the current phrasing of the paragraph, especially given its prominent location on the page, that seems to say we're scrambling to explain this Pylons vs. Pylons vs. Pyramid distinction to you, dear visitor, even though you didn't ask. The point of rewriting -- whether it be my suggestion or someone else's better offering -- would be to provide the simple factual information as smoothly as possible, without a rather than clause, and without a couple of other things that just seem a bit indirect and unnecessary about the current phrasing. No offense intended to he who wrote the paragraph, it's not bad, and I think it made perfect sense in the first quarter of 2011, addressing visitors who most likely were aware of Pylons and arrived to see what the hubbub was about with news of Pyramid making the rounds. But we've quickly moved into a more long term steady state where the average visitor is none too concerned with the history or the aforementioned distinction; by and large I suspect the average visitor simply wants to get straight into the current offering and not worry about those details. I do suppose there is a significant minority of visitors who are newfound maintainers or migrators of Pylons-based projects, who actually are seeking that information; but I don't see a need to cater to them at the top of the page by default. Along those lines I almost went as far as to suggest that we quit even bothering to explain the Pylons vs. Pylons vs. Pyramid distinction on the front page at all. But I suppose it's still necessary, given that Pyramid has top billing and yet the URL and the 'Project itself are still (and will remain) Pylons branded. So I guess that does leave some need for at least a minor explanation. There is also value in noting the strength and extent of current well-known apps/sites/ projects built on the Pylons framework. Thus the grey bar which forms the second main element of the page, below the top orange-gradient Pyramid section, has reason to exist with at least some sort of prominence. Still, I almost think it could be a good idea to remodel it into (mostly/nearly) a full-on Pyramid home page, with a less prominent section at the bottom, or in a sidebar, saying looking for the Pylons framework? and providing links thereto. Maybe right now is not quite that point in time yet, but it's food for thought. I don't mean to take on the sound of a project member or contributor here, as all I've been able to provide is a few typo corrections in docs. Forgive my use of the we voice above. But I do hope these thoughts are worth the community's and the developers' consideration. Thanks. - ejo -- You received this message because you are subscribed to the Google Groups pylons-devel group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: Some thoughts about Pyramid
I'm up too On Mar 3, 8:09 pm, Carlos de la Guardia carlos.delaguar...@gmail.com wrote: Guys, I'll be at PyCon and would like to sprint on this. Maybe a tutorial with code. Anyone? Carlos de la Guardia On Thu, Mar 3, 2011 at 6:08 PM, Chris McDonough chr...@plope.com wrote: On Thu, 2011-03-03 at 17:57 -0600, Joe Dallago wrote: So the thing we can carry away from this discussion is that we should improve Pyramid's new user experience, with tutorials and perhaps some defaults for basic functionality. We hold these truths to be self evident... - C On Thu, Mar 3, 2011 at 4:27 PM, Mike Orr sluggos...@gmail.com wrote: On Thu, Mar 3, 2011 at 10:22 AM, danjac...@gmail.com danjac...@gmail.com wrote: I'm not sure the OP is trolling, it comes across as frustration. It's absolutely a legitimate point, and it's what I've been concerned about for the past several months. It's why I'm writing the Pyramid Migration Guide and Akhet (the successor to pyramid_sqla) -- both to be released hopefully by PyCon. Stephan comes from a new user's perspective with a Django background. As such, there will be more users like this, and if we can give them specific documentation and examples addressing their concerns, it will help the works-out-of-the-box issue. If we want to attract new users, we must do this. That doesn't mean the Pyramid core developers have to do all the work. It's a great opportunity for add-on products made by others with more time on their hands. The Pyramid manual is essentially a reference guide, so it documents all the alternatives in detail. That's necessary, but it's not the same as a tutorial. And people have such different backgrounds that several focused tutorials would be better than one. I'm writing a migration guide for Pylons users. Stephan's post makes me think a migration guide for Django users would be helpful. I don't know enough about Django to write this myself. Obviously we can't write guides for every single framework, but Pylons covers a variety of WSGI developers who know something about Pylons, and Django covers another large set that's unique enough to require its own guide. Zope/BFG people seem to find the Pyramid manual sufficient, so that's covered. The answers to Stephan's concerns fall into roughly three categories: - Intentional design decisions; i.e., goals for Pyramid. - Tradeoffs we had to make given those decisions. - The historical legacy of BFG, and the desire not to break backward compatibility. Pyramid's design is heavily shaped by things that Pylons/TurboGears didn't have and their developers wanted. BFG did have these so we took them, and along came everything else BFG had. Things that Pylons specifically wanted were: events, a complete reference manual, eliminating the magic globals [1], better unit testing (which views-returning-a-dict provides), interfaces, a larger developer-base, and maybe other things I'm forgetting. Traversal, ZODB, and built-in auth that's simpler than repoze.who/what were minor desires that essentially came for free. [1] Pyramid threadlocals are similar to Pylons magic globals, but the rest of the framework has been designed not to require them (the threadlocals). The BFG developers make a compelling case that traversal and interfaces are useful, especially for certain kinds of applications. That having these available is a good thing, even for those who don't use them, because it provides a migration path to use them later if they become important someday. Traversal is particularly suited to CMS sites where editor-users can attach a page to any URL, arbitrarily nested. Routes doesn't do this; Routes depends on path variables being in fixed URL positions. Interfaces I only understand superficially, but I have a gut feeling they will be more widely used as more people get comfortable with them. Previously interfaces were available only in Zope and BFG. Zope is a very specialized environment, BFG somewhat less so, but Pyramid makes interfaces accessible to the masses (i.e., general Python-web developers). Pyramid and WebHelpers have borrowed some features from Django, but certain aspects of Django are decidedly non-features in Pyramid/Pylons/TurboGears, and have been for five years. The Pylons Project believes in using third-party packages whenever feasable, and in spinning off packages that can be used outside the frameworks. Of course there are disadvantages to this as well as advantages. If a third-party library becomes unmaintained or has version skew (i.e., its latest version has incompatible changes), it adversely affects the framework until we reconcile the two or switch to another library. Likewise, sometimes the framework needs to switch to a better library, and users have to adjust their applications.
Re: Some thoughts about Pyramid
Well... same for me, I got a lot of clients work to complete and I've done my best trying to put everything in place to have something cohesive. I also got help from multiple people for different tasks and I'm grateful for every contribution. That said we definitely need to communicate the right message, provide the right level of documentation for the targeted audience, have a better way to expose tools and contributions, etc... I think we should add the website as a sprint project too, could be combined with the tutorial? Blaise On Mar 4, 2:50 pm, Mike Orr sluggos...@gmail.com wrote: Pylons never did marketing well for two reasons. One, the core developers aren't talented marketers. Two, we were busy finishing Pylons 1, and then we immediately finished Pyramid 1 back-to-back. That didn't leave much extra time for marketing or for focusing on the website. Now that Pyramid 1 is finished, we can take a step back and look at some areas we've neglected; e.g., marketing and tutorials. I say we, although in reality Ben is busy with his clients' sites, I'm plowing through three Pyramid add-ons, and for all I know Chris is working on his own clients' sites, and who knows what others are doing. Still, it's worth discussing how the Pylons Project as a whole can improve on marketing, documentation, and handholding (new users through the process of building their first site). I have a friend who is a marketer and supports the Pylons Project, but he's kind of gotten burned out on Python as a whole for various reasons so he can't quite be a full marketing advisor. Is there anyone else with marketing-type experience who would like to stand up? -- Mike Orr sluggos...@gmail.com -- You received this message because you are subscribed to the Google Groups pylons-devel group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: Some thoughts about Pyramid
By that I meant, following a previous post I made, to possibly create new comer guides, opinionated guides, etc... to fill the missing gap. I don't think the current docs need to track down those requests, they are not perfect but they are great. Another point is complaint about pyramid needing more rails, and at the same time having less dependencies with a smaller core ;) We're in the middle :) On Mar 4, 4:38 pm, Reed L O'Brien reedobr...@gmail.com wrote: Who is the targeted audience? Currently it seems to be everyone with a complaint. I was very happy with repoze.bfg as it shipped and am very happy with pyramid as it currently ships. It was only a minor nuisance to add pyramid_zcml as a dependency to the projects I had using it. I subsequently stopped using it, so I don't have to manage another dependency; it is just spelling... -- You received this message because you are subscribed to the Google Groups pylons-devel group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
Re: varying template name which matches route path
Doing something similar for pylonsproject.org to render mako templates
or rst files based on on a path url:
https://github.com/Pylons/pylonshq/blob/master/pylonshq/handlers/pages.py
On Feb 24, 3:13 pm, AwaisMuzaffar awais1...@googlemail.com wrote:
Lets assume, I have the following route set up:
config.add_route('pages', '/{page}/', view='testproject:views.pages',
view_renderer='testproject:templates/page.mak')
Would it be possible to make the template name e.g page.mak a variable
that matches the name of the response path.
something like: view_renderer = .. templates/{page}.mak
So template name uses the path name.
I hope you guys understand what I am getting at.
--
You received this message because you are subscribed to the Google Groups
pylons-devel group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
