Bert would indeed be happy. Cheers, Bert
> On Jan 2, 2016, at 15:22, Michael Merickel <mich...@merickel.org> 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 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. > > > -- > 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. -- 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.
smime.p7s
Description: S/MIME cryptographic signature