Re: Problems with podlings pages
On 29 February 2016 at 22:27, Sam Ruby wrote: > Feel free to add a link on the main whimsy page, re-order columns, > capitalize headings, etc. OK > I also forgot to mention that it is my intent to make the roster tool > fully read/write over time... people with the appropriate permissions > should be able to make updates from these pages. The ability to edit > the SpamAssassin score, and to add/remove committers are just an > examples of what possibilities are there. > > So there may be other read-only views out there. The phone book is an > example. I'm personally skeptical of it's functionality to do > cross-checks. Not that it duplicates functionality that has been Not? Did you mean Note? > present for a long time in the roster tool (that's fine with me, after > all, it has a different target audience). But that it tells the wrong > audience (the general public) this information, and does not provide > the means to correct it. AFAIK, the phone book was aimed at committers, not the general public, though it is public. It is now usable as a replacement for most of people.a.o. Whimsy is not as easy to use as it requires auth for most of the information that has traditionally been publicly available from people.a.o. > - Sam Ruby > > On Mon, Feb 29, 2016 at 5:13 PM, sebb wrote: >> On 29 February 2016 at 21:56, Sam Ruby wrote: >>> On Mon, Feb 29, 2016 at 4:40 PM, sebb wrote: On 29 February 2016 at 21:37, sebb wrote: > Main page lists a link for: > > https://whimsy.apache.org/incubator/podlings/by-age > > This lists 50 PPMCs > > https://whimsy.apache.org/roster lists >>> >>> How did you get to this page? >> >> I typed it in, because it's not linked from the main page. >> Perhaps it should be added above the list of its sub-pages? >> >>> It should have a trailing slash. Do we >>> need to add the following to >>> infrastructure-puppet/data/nodes/whimsy-vm2.apache.org.yaml >>> >>> RedirectMatch ^/roster$ /roster/ >> >> Probably not. >> > 51PodlingsActive podlings at the ASF => > https://whimsy.apache.org/podlings => 404 > > Not sure where the link is supposed to go Found it at https://whimsy.apache.org/roster/podlings However this repeats the information in, and indeed links to, http://incubator.apache.org/projects/#current >>> >>> Apparently not. One has 50 and one has 51. :-) >>> Not sure why there is a need for this duplication. Why not just link to the incubator site? >>> >>> I do link to the incubator site when you click on an individual podling. >>> >>> The index pages has counts, and can sort in various ways by clicking >>> on the headings. >> >> Did not realise that; it's not immediately obvious. >> I think the Status column should be between the Name and Description >> (and IMO they would be more obvious if they were capitalised). >> >>> I'm not sure what cross-checks may be useful, but an >>> example where cross-checks find authorizations associated with retired >>> podlings can be found on the groups page. >> >> Current podlings may have a non-LDAP group (for SVN auth); this should >> disappear when the podling graduates (it's replaced by an LDAP >> committee group) or retires (it should be removed). >> > or why the pages disagree on > the number of podlings >>> >>> Nope. I would have thought that the two pages were derived from the >>> same data source. >> >> They should both be derived from podlings.xml, but maybe they >> interpret it differently. >> Or maybe they are using different copies - there's the original SVN, >> then maybe a staging copy and the deployed copy. >> If a change has not been fully pushed there could be discrepancies. >> >>> - Sam Ruby
Re: Problems with podlings pages
Feel free to add a link on the main whimsy page, re-order columns, capitalize headings, etc. I also forgot to mention that it is my intent to make the roster tool fully read/write over time... people with the appropriate permissions should be able to make updates from these pages. The ability to edit the SpamAssassin score, and to add/remove committers are just an examples of what possibilities are there. So there may be other read-only views out there. The phone book is an example. I'm personally skeptical of it's functionality to do cross-checks. Not that it duplicates functionality that has been present for a long time in the roster tool (that's fine with me, after all, it has a different target audience). But that it tells the wrong audience (the general public) this information, and does not provide the means to correct it. - Sam Ruby On Mon, Feb 29, 2016 at 5:13 PM, sebb wrote: > On 29 February 2016 at 21:56, Sam Ruby wrote: >> On Mon, Feb 29, 2016 at 4:40 PM, sebb wrote: >>> On 29 February 2016 at 21:37, sebb wrote: Main page lists a link for: https://whimsy.apache.org/incubator/podlings/by-age This lists 50 PPMCs https://whimsy.apache.org/roster lists >> >> How did you get to this page? > > I typed it in, because it's not linked from the main page. > Perhaps it should be added above the list of its sub-pages? > >> It should have a trailing slash. Do we >> need to add the following to >> infrastructure-puppet/data/nodes/whimsy-vm2.apache.org.yaml >> >> RedirectMatch ^/roster$ /roster/ > > Probably not. > 51PodlingsActive podlings at the ASF => https://whimsy.apache.org/podlings => 404 Not sure where the link is supposed to go >>> >>> Found it at >>> >>> https://whimsy.apache.org/roster/podlings >>> >>> However this repeats the information in, and indeed links to, >>> http://incubator.apache.org/projects/#current >> >> Apparently not. One has 50 and one has 51. :-) >> >>> Not sure why there is a need for this duplication. >>> Why not just link to the incubator site? >> >> I do link to the incubator site when you click on an individual podling. >> >> The index pages has counts, and can sort in various ways by clicking >> on the headings. > > Did not realise that; it's not immediately obvious. > I think the Status column should be between the Name and Description > (and IMO they would be more obvious if they were capitalised). > >> I'm not sure what cross-checks may be useful, but an >> example where cross-checks find authorizations associated with retired >> podlings can be found on the groups page. > > Current podlings may have a non-LDAP group (for SVN auth); this should > disappear when the podling graduates (it's replaced by an LDAP > committee group) or retires (it should be removed). > or why the pages disagree on the number of podlings >> >> Nope. I would have thought that the two pages were derived from the >> same data source. > > They should both be derived from podlings.xml, but maybe they > interpret it differently. > Or maybe they are using different copies - there's the original SVN, > then maybe a staging copy and the deployed copy. > If a change has not been fully pushed there could be discrepancies. > >> - Sam Ruby
Re: Problems with podlings pages
On 29 February 2016 at 21:56, Sam Ruby wrote: > On Mon, Feb 29, 2016 at 4:40 PM, sebb wrote: >> On 29 February 2016 at 21:37, sebb wrote: >>> Main page lists a link for: >>> >>> https://whimsy.apache.org/incubator/podlings/by-age >>> >>> This lists 50 PPMCs >>> >>> https://whimsy.apache.org/roster lists > > How did you get to this page? I typed it in, because it's not linked from the main page. Perhaps it should be added above the list of its sub-pages? > It should have a trailing slash. Do we > need to add the following to > infrastructure-puppet/data/nodes/whimsy-vm2.apache.org.yaml > > RedirectMatch ^/roster$ /roster/ Probably not. >>> 51PodlingsActive podlings at the ASF => >>> https://whimsy.apache.org/podlings => 404 >>> >>> Not sure where the link is supposed to go >> >> Found it at >> >> https://whimsy.apache.org/roster/podlings >> >> However this repeats the information in, and indeed links to, >> http://incubator.apache.org/projects/#current > > Apparently not. One has 50 and one has 51. :-) > >> Not sure why there is a need for this duplication. >> Why not just link to the incubator site? > > I do link to the incubator site when you click on an individual podling. > > The index pages has counts, and can sort in various ways by clicking > on the headings. Did not realise that; it's not immediately obvious. I think the Status column should be between the Name and Description (and IMO they would be more obvious if they were capitalised). > I'm not sure what cross-checks may be useful, but an > example where cross-checks find authorizations associated with retired > podlings can be found on the groups page. Current podlings may have a non-LDAP group (for SVN auth); this should disappear when the podling graduates (it's replaced by an LDAP committee group) or retires (it should be removed). >>> or why the pages disagree on >>> the number of podlings > > Nope. I would have thought that the two pages were derived from the > same data source. They should both be derived from podlings.xml, but maybe they interpret it differently. Or maybe they are using different copies - there's the original SVN, then maybe a staging copy and the deployed copy. If a change has not been fully pushed there could be discrepancies. > - Sam Ruby
Re: Problems with podlings pages
On Mon, Feb 29, 2016 at 4:40 PM, sebb wrote: > On 29 February 2016 at 21:37, sebb wrote: >> Main page lists a link for: >> >> https://whimsy.apache.org/incubator/podlings/by-age >> >> This lists 50 PPMCs >> >> https://whimsy.apache.org/roster lists How did you get to this page? It should have a trailing slash. Do we need to add the following to infrastructure-puppet/data/nodes/whimsy-vm2.apache.org.yaml RedirectMatch ^/roster$ /roster/ >> 51PodlingsActive podlings at the ASF => >> https://whimsy.apache.org/podlings => 404 >> >> Not sure where the link is supposed to go > > Found it at > > https://whimsy.apache.org/roster/podlings > > However this repeats the information in, and indeed links to, > http://incubator.apache.org/projects/#current Apparently not. One has 50 and one has 51. :-) > Not sure why there is a need for this duplication. > Why not just link to the incubator site? I do link to the incubator site when you click on an individual podling. The index pages has counts, and can sort in various ways by clicking on the headings. I'm not sure what cross-checks may be useful, but an example where cross-checks find authorizations associated with retired podlings can be found on the groups page. >> or why the pages disagree on >> the number of podlings Nope. I would have thought that the two pages were derived from the same data source. - Sam Ruby
Re: https://whimsy.apache.org/incubator/podlings/by-age - reverse sort?
On Mon, Feb 29, 2016 at 4:31 PM, sebb wrote: > It might be better to list podlings by reverse order of age so the > newer ones get more exposure? The original purpose of this page was to draw attention to podlings that needed a little push. > Also the links to the podling sites could open in a new window? That's an age old controversy: https://annevankesteren.nl/2004/09/new-window Given that all browsers provide the ability to open a page in a new tab/window (via control, command, or middle - click), I tend to agree that pages should behave consistently, and leave it up to the user to decide. - Sam Ruby
Re: Problems with podlings pages
On 29 February 2016 at 21:37, sebb wrote: > Main page lists a link for: > > https://whimsy.apache.org/incubator/podlings/by-age > > This lists 50 PPMCs > > https://whimsy.apache.org/roster lists > > 51PodlingsActive podlings at the ASF => > https://whimsy.apache.org/podlings => 404 > > Not sure where the link is supposed to go Found it at https://whimsy.apache.org/roster/podlings However this repeats the information in, and indeed links to, http://incubator.apache.org/projects/#current Not sure why there is a need for this duplication. Why not just link to the incubator site? > or why the pages disagree on > the number of podlings
Problems with podlings pages
Main page lists a link for: https://whimsy.apache.org/incubator/podlings/by-age This lists 50 PPMCs https://whimsy.apache.org/roster lists 51PodlingsActive podlings at the ASF => https://whimsy.apache.org/podlings => 404 Not sure where the link is supposed to go or why the pages disagree on the number of podlings
https://whimsy.apache.org/incubator/podlings/by-age - reverse sort?
It might be better to list podlings by reverse order of age so the newer ones get more exposure? Also the links to the podling sites could open in a new window?
RECOVERY: whimsy.apache.org (whimsy.apache.org (https)) is back up!
Hello, The https service at whimsy.apache.org (whimsy.apache.org (https)) seems to be back in working order again. With regards, Ping My Box - https://www.pingmybox.com/
Re: Beta test: LDAP updates via whimsy
On Mon, Feb 29, 2016 at 1:34 PM, Rene Gielen wrote: > To follow-up my own report: as it turns out, the addition done through > whimsy was actually succesful. Checked with list_committee.pl and by > reloading https://whimsy-test.apache.org/roster/committee/struts page. > > Seems like the 500 was mis-leading. Thanks for reporting it! It was a recent regression. I've pushed a fix. After it completed the change, there was a bug in the code that collected updated results to be sent back as a response. That's now fixed. > Thanks, > René - Sam Ruby > Am 29.02.16 um 19:31 schrieb Rene Gielen: >> Hi, >> >> the Apache Struts PMC has a new member, Greg Huber (ghuber). >> >> I tried to make the update with whymsy-test. I found ghuber by availid, >> chose "Add to PMC only", and confirmed it in the following dialog. The >> result was HTTP status 500. I'm going to use minotaur now, just wanted >> to let you folks know. >> >> Cheers, >> - René >> >> >> Am 15.02.16 um 23:44 schrieb Sam Ruby: >>> The current plans are for shell access to be phased out. This affects >>> PMC chairs who are responsible for updating LDAP access, something that >>> is currently done via running Perl scripts: >>> >>> https://www.apache.org/dev/pmc.html#SVNaccess >>> https://reference.apache.org/pmc/acreq#SVNaccess >>> >>> PMC chairs (as well as those in the secretary group as well as people >>> with root access) can now make LDAP updates via a web interface: >>> >>> https://whimsy-test.apache.org/roster/committee/ >>> >>> At the moment, this is *just* a replacement for those scripts. Planned >>> additions include: >>> >>> * sending out emails to the PMC when changes are made >>> >>> * updating committee-info.txt >>> >>> Please direct bug reports, feature requests, and pull requests to: >>> >>> dev@whimsical.apache.org >>> https://issues.apache.org/jira/browse/WHIMSY/ >>> https://github.com/apache/whimsy >>> >>> - Sam Ruby >>> >> > > -- > René Gielen > http://twitter.com/rgielen
ALERT: whimsy.apache.org (whimsy.apache.org (https)) is DOWN!
Hello, The https service at whimsy.apache.org (whimsy.apache.org (https)) has been reported as down by our monitoring system: Component: response Error code: Internal Server Error or equivalent bad message received: HTTP/1.1 400 public_json nonldap-groups ["/usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler/setup (LoadError)", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'", "\tfrom /srv/whimsy/www/roster/public_json_common.rb:10:in `'", "\tfrom roster/public_nonldap_groups.rb:23:in `require_relative'", "\tfrom roster/public_nonldap_groups.rb:23:in `'"] Debug output: -- [Mon Feb 29 18:40:49 2016]: Initialising socket [Mon Feb 29 18:40:49 2016]: Looking up hostname whimsy.apache.org... [Mon Feb 29 18:40:49 2016]: Connecting to 209.188.14.150:443 [Mon Feb 29 18:40:50 2016]: Connected, sending HTTPS payload. [Mon Feb 29 18:40:50 2016]: Reading response header from server [Mon Feb 29 18:40:50 2016]: Caught exception: Internal Server Error or equivalent bad message received: HTTP/1.1 400 public_json nonldap-groups ["/usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler/setup (LoadError)", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'", "\tfrom /srv/whimsy/www/roster/public_json_common.rb:10:in `'", "\tfrom roster/public_nonldap_groups.rb:23:in `require_relative'", "\tfrom roster/public_nonldap_groups.rb:23:in `'"] -- With regards, Ping My Box - https://www.pingmybox.com/
Re: Beta test: LDAP updates via whimsy
To follow-up my own report: as it turns out, the addition done through whimsy was actually succesful. Checked with list_committee.pl and by reloading https://whimsy-test.apache.org/roster/committee/struts page. Seems like the 500 was mis-leading. Thanks, René Am 29.02.16 um 19:31 schrieb Rene Gielen: > Hi, > > the Apache Struts PMC has a new member, Greg Huber (ghuber). > > I tried to make the update with whymsy-test. I found ghuber by availid, > chose "Add to PMC only", and confirmed it in the following dialog. The > result was HTTP status 500. I'm going to use minotaur now, just wanted > to let you folks know. > > Cheers, > - René > > > Am 15.02.16 um 23:44 schrieb Sam Ruby: >> The current plans are for shell access to be phased out. This affects >> PMC chairs who are responsible for updating LDAP access, something that >> is currently done via running Perl scripts: >> >> https://www.apache.org/dev/pmc.html#SVNaccess >> https://reference.apache.org/pmc/acreq#SVNaccess >> >> PMC chairs (as well as those in the secretary group as well as people >> with root access) can now make LDAP updates via a web interface: >> >> https://whimsy-test.apache.org/roster/committee/ >> >> At the moment, this is *just* a replacement for those scripts. Planned >> additions include: >> >> * sending out emails to the PMC when changes are made >> >> * updating committee-info.txt >> >> Please direct bug reports, feature requests, and pull requests to: >> >> dev@whimsical.apache.org >> https://issues.apache.org/jira/browse/WHIMSY/ >> https://github.com/apache/whimsy >> >> - Sam Ruby >> > -- René Gielen http://twitter.com/rgielen
Re: Beta test: LDAP updates via whimsy
Hi, the Apache Struts PMC has a new member, Greg Huber (ghuber). I tried to make the update with whymsy-test. I found ghuber by availid, chose "Add to PMC only", and confirmed it in the following dialog. The result was HTTP status 500. I'm going to use minotaur now, just wanted to let you folks know. Cheers, - René Am 15.02.16 um 23:44 schrieb Sam Ruby: > The current plans are for shell access to be phased out. This affects > PMC chairs who are responsible for updating LDAP access, something that > is currently done via running Perl scripts: > > https://www.apache.org/dev/pmc.html#SVNaccess > https://reference.apache.org/pmc/acreq#SVNaccess > > PMC chairs (as well as those in the secretary group as well as people > with root access) can now make LDAP updates via a web interface: > > https://whimsy-test.apache.org/roster/committee/ > > At the moment, this is *just* a replacement for those scripts. Planned > additions include: > > * sending out emails to the PMC when changes are made > > * updating committee-info.txt > > Please direct bug reports, feature requests, and pull requests to: > > dev@whimsical.apache.org > https://issues.apache.org/jira/browse/WHIMSY/ > https://github.com/apache/whimsy > > - Sam Ruby > -- René Gielen http://twitter.com/rgielen
Vhost generator (was: PGP keys should display one per line)
On Mon, Feb 29, 2016 at 10:05 AM, sebb wrote: > On 29 February 2016 at 12:22, Sam Ruby wrote: >> On Mon, Feb 29, 2016 at 5:35 AM, sebb wrote: >>> >>> I'm using virtual hosts for different apps (projects, reports, etc) >> >> Makes sense. Let's plan to update the "Advanced configuration" >> section of DEVELOPMENT.md to be based on a vhost. I've attached the >> current puppet generated vhost definition that is on whimsy-vm2. I >> suspect with only minimal changes it would work as is on your machine >> - complete with authentication. > > Attachment was stolen en route to me ... I blame gnomes. Try this: https://whimsy.apache.org/test/vhost-generator >> Perhaps a "vhost generator" CGI script would be helpful? First it >> presents a form with a few fields that can be used to customize the >> result, and then after you click submit it presents a file you can >> download and drop into your "sites-available" directory? > > I don't have a sites-available directory; I'm using > /etc/apache2/extra/httpd-vhosts.conf > > I think a fixed template would be just as good, together with comments > as to what to edit if necessary. > That would help people understand the config. The template I'm using is live data from the actual deployment. If you have improvements in mind for the template, please contribute them to infrastructure-puppet. But I would like to go further. I believe that the edits can be automated. Once this generator produces a file that you can actually use, I'll go back and update my setup to use a vhost too. At that point, we will have something that two people are using. If others want to follow, at least they won't be trailblazing. > But it would be helpful to have a script to check that the file paths > used in the template contained the expected contents. > >>> I guess this is closer to what I need. >>> Alias /roster/ /srv/whimsy/www/roster/committer PassengerBaseURI /roster PassengerAppRoot /srv/whimsy/www/roster/committer PassengerAppEnv development Options -Multiviews >>> >>> Doesn't work. >>> >>> However this does: >>> >>> Alias /roster/ /srv/whimsy/www/roster >>> >>> PassengerBaseURI /roster >>> PassengerAppRoot /srv/whimsy/www/roster >>> PassengerAppEnv development >>> Options -Multiviews >>> >>> >>> Yay! >> >> Comparing that to what is deployed on whimsy-vm2, I missed a "/public" >> on the Alias line. >> Should that not work... have you ever run Docker or Vagrant before? I >>> >>> I have got Docker; don't think I have used Vagrant. >> >> Unless you are a Linux user, Vagrant is better in my opinion. You get >> a real VM that you can ssh into with full sudo access. With Docker, >> you get a container, which can only be hosted by Linux at the moment, >> and that means that for Mac OS/X users you will be putting it into a >> VM anyway. Since you are up and running, I'll put this on the back >> burner for now, but it is a good thing to have. > > Yes. > > If Vagrant is still OK for Linux, then potentially there is no need > for Docker as well. > probably can quickly set up one or the other. My thoughts are that once you have a working system that you can compare against, spotting the difference with your current setup would be much easier. And that could lead to updates to the documentation to help others. >>> >>> I think it would help to document what the paths represent, and for >>> file paths, what one would expect to find there. >>> >>> e.g. I assume PassengerAppRoot is a local path, and need to point to a >>> rake app, i.e. a whimsy directory containing config.ru. >>> >>> This should make it easier to check the settings are correct. >> >> The best way would be to base the settings on what is actually >> deployed. The instructions to produce those settings are in >> infrastructure-puppet, but making the generated results visible and >> helping you tailor them would be even better. Would you agree? > > Definitely. Cool. See above. - Sam Ruby
Re: PGP keys should display one per line
On 29 February 2016 at 12:22, Sam Ruby wrote: > On Mon, Feb 29, 2016 at 5:35 AM, sebb wrote: >> >> I'm using virtual hosts for different apps (projects, reports, etc) > > Makes sense. Let's plan to update the "Advanced configuration" > section of DEVELOPMENT.md to be based on a vhost. I've attached the > current puppet generated vhost definition that is on whimsy-vm2. I > suspect with only minimal changes it would work as is on your machine > - complete with authentication. Attachment was stolen en route to me ... > Perhaps a "vhost generator" CGI script would be helpful? First it > presents a form with a few fields that can be used to customize the > result, and then after you click submit it presents a file you can > download and drop into your "sites-available" directory? I don't have a sites-available directory; I'm using /etc/apache2/extra/httpd-vhosts.conf I think a fixed template would be just as good, together with comments as to what to edit if necessary. That would help people understand the config. But it would be helpful to have a script to check that the file paths used in the template contained the expected contents. >> I guess this is closer to what I need. >> >>> Alias /roster/ /srv/whimsy/www/roster/committer >>> >>> PassengerBaseURI /roster >>> PassengerAppRoot /srv/whimsy/www/roster/committer >>> PassengerAppEnv development >>> Options -Multiviews >>> >> >> Doesn't work. >> >> However this does: >> >> Alias /roster/ /srv/whimsy/www/roster >> >> PassengerBaseURI /roster >> PassengerAppRoot /srv/whimsy/www/roster >> PassengerAppEnv development >> Options -Multiviews >> >> >> Yay! > > Comparing that to what is deployed on whimsy-vm2, I missed a "/public" > on the Alias line. > >>> Should that not work... have you ever run Docker or Vagrant before? I >> >> I have got Docker; don't think I have used Vagrant. > > Unless you are a Linux user, Vagrant is better in my opinion. You get > a real VM that you can ssh into with full sudo access. With Docker, > you get a container, which can only be hosted by Linux at the moment, > and that means that for Mac OS/X users you will be putting it into a > VM anyway. Since you are up and running, I'll put this on the back > burner for now, but it is a good thing to have. Yes. If Vagrant is still OK for Linux, then potentially there is no need for Docker as well. >>> probably can quickly set up one or the other. My thoughts are that >>> once you have a working system that you can compare against, spotting >>> the difference with your current setup would be much easier. And that >>> could lead to updates to the documentation to help others. >> >> I think it would help to document what the paths represent, and for >> file paths, what one would expect to find there. >> >> e.g. I assume PassengerAppRoot is a local path, and need to point to a >> rake app, i.e. a whimsy directory containing config.ru. >> >> This should make it easier to check the settings are correct. > > The best way would be to base the settings on what is actually > deployed. The instructions to produce those settings are in > infrastructure-puppet, but making the generated results visible and > helping you tailor them would be even better. Would you agree? Definitely.
RECOVERY: whimsy.apache.org (whimsy.apache.org (https)) is back up!
Hello, The https service at whimsy.apache.org (whimsy.apache.org (https)) seems to be back in working order again. With regards, Ping My Box - https://www.pingmybox.com/
ALERT: whimsy.apache.org (whimsy.apache.org (https)) is DOWN!
Hello, The https service at whimsy.apache.org (whimsy.apache.org (https)) has been reported as down by our monitoring system: Component: response Error code: Internal Server Error or equivalent bad message received: HTTP/1.1 400 public_json nonldap-groups ["/usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler/version (LoadError)", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'", "\tfrom /usr/local/rvm/gems/ruby-2.3.0/gems/bundler-1.11.2/lib/bundler.rb:9:in `'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'", "\tfrom /usr/local/rvm/gems/ruby-2.3.0/gems/bundler-1.11.2/lib/bundler/setup.rb:4:in `'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in `require'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/! kernel_require.rb:127:in `rescue in require'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in `require'", "\tfrom /srv/whimsy/www/roster/public_json_common.rb:10:in `'", "\tfrom roster/public_nonldap_groups.rb:23:in `require_relative'", "\tfrom roster/public_nonldap_groups.rb:23:in `'"] Debug output: -- [Mon Feb 29 13:41:26 2016]: Initialising socket [Mon Feb 29 13:41:26 2016]: Looking up hostname whimsy.apache.org... [Mon Feb 29 13:41:26 2016]: Connecting to 209.188.14.150:443 [Mon Feb 29 13:41:27 2016]: Connected, sending HTTPS payload. [Mon Feb 29 13:41:27 2016]: Reading response header from server [Mon Feb 29 13:41:27 2016]: Caught exception: Internal Server Error or equivalent bad message received: HTTP/1.1 400 public_json nonldap-groups ["/usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler/version (LoadError)", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'", "\tfrom /usr/local/rvm/gems/ruby-2.3.0/gems/bundler-1.11.2/lib/bundler.rb:9:in `'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'", "\tfrom /usr/local/rvm/gems/ruby-2.3.0/gems/bundler-1.11.2/lib/bundler/setup.rb:4:in `'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in `require'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0! /lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in `rescue in require'", "\tfrom /usr/local/rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in `require'", "\tfrom /srv/whimsy/www/roster/public_json_common.rb:10:in `'", "\tfrom roster/public_nonldap_groups.rb:23:in `require_relative'", "\tfrom roster/public_nonldap_groups.rb:23:in `'"] -- With regards, Ping My Box - https://www.pingmybox.com/
Re: PGP keys should display one per line
On Mon, Feb 29, 2016 at 5:35 AM, sebb wrote: > > I'm using virtual hosts for different apps (projects, reports, etc) Makes sense. Let's plan to update the "Advanced configuration" section of DEVELOPMENT.md to be based on a vhost. I've attached the current puppet generated vhost definition that is on whimsy-vm2. I suspect with only minimal changes it would work as is on your machine - complete with authentication. Perhaps a "vhost generator" CGI script would be helpful? First it presents a form with a few fields that can be used to customize the result, and then after you click submit it presents a file you can download and drop into your "sites-available" directory? > I guess this is closer to what I need. > >> Alias /roster/ /srv/whimsy/www/roster/committer >> >> PassengerBaseURI /roster >> PassengerAppRoot /srv/whimsy/www/roster/committer >> PassengerAppEnv development >> Options -Multiviews >> > > Doesn't work. > > However this does: > > Alias /roster/ /srv/whimsy/www/roster > > PassengerBaseURI /roster > PassengerAppRoot /srv/whimsy/www/roster > PassengerAppEnv development > Options -Multiviews > > > Yay! Comparing that to what is deployed on whimsy-vm2, I missed a "/public" on the Alias line. >> Should that not work... have you ever run Docker or Vagrant before? I > > I have got Docker; don't think I have used Vagrant. Unless you are a Linux user, Vagrant is better in my opinion. You get a real VM that you can ssh into with full sudo access. With Docker, you get a container, which can only be hosted by Linux at the moment, and that means that for Mac OS/X users you will be putting it into a VM anyway. Since you are up and running, I'll put this on the back burner for now, but it is a good thing to have. >> probably can quickly set up one or the other. My thoughts are that >> once you have a working system that you can compare against, spotting >> the difference with your current setup would be much easier. And that >> could lead to updates to the documentation to help others. > > I think it would help to document what the paths represent, and for > file paths, what one would expect to find there. > > e.g. I assume PassengerAppRoot is a local path, and need to point to a > rake app, i.e. a whimsy directory containing config.ru. > > This should make it easier to check the settings are correct. The best way would be to base the settings on what is actually deployed. The instructions to produce those settings are in infrastructure-puppet, but making the generated results visible and helping you tailor them would be even better. Would you agree? - Sam Ruby
RECOVERY: whimsy.apache.org (whimsy.apache.org (https)) is back up!
Hello, The https service at whimsy.apache.org (whimsy.apache.org (https)) seems to be back in working order again. With regards, Ping My Box - https://www.pingmybox.com/
ALERT: whimsy.apache.org (whimsy.apache.org (https)) is DOWN!
Hello, The https service at whimsy.apache.org (whimsy.apache.org (https)) has been reported as down by our monitoring system: Component: response Error code: Internal Server Error or equivalent bad message received: HTTP/1.1 400 public_json ldap-people "[ldap2-us-west.apache.org:636] => # for ldapsearch -x -LLL -b ou=people,dc=apache,dc=org -s one (|(cn=*)(loginShell=*)(asf-personalURL=*)(createTimestamp=*)(modifyTimestamp=*)) cn loginShell asf-personalURL createTimestamp modifyTimestamp uid, retrying ..." Debug output: -- [Mon Feb 29 11:22:30 2016]: Initialising socket [Mon Feb 29 11:22:30 2016]: Looking up hostname whimsy.apache.org... [Mon Feb 29 11:22:30 2016]: Connecting to 209.188.14.150:443 [Mon Feb 29 11:22:30 2016]: Connected, sending HTTPS payload. [Mon Feb 29 11:22:30 2016]: Reading response header from server [Mon Feb 29 11:22:30 2016]: Caught exception: Internal Server Error or equivalent bad message received: HTTP/1.1 400 public_json ldap-people "[ldap2-us-west.apache.org:636] => # for ldapsearch -x -LLL -b ou=people,dc=apache,dc=org -s one (|(cn=*)(loginShell=*)(asf-personalURL=*)(createTimestamp=*)(modifyTimestamp=*)) cn loginShell asf-personalURL createTimestamp modifyTimestamp uid, retrying ..." -- With regards, Ping My Box - https://www.pingmybox.com/
Re: PGP keys should display one per line
On 29 February 2016 at 01:53, Sam Ruby wrote: > On Sun, Feb 28, 2016 at 8:28 PM, sebb wrote: >> On 29 February 2016 at 01:04, Sam Ruby wrote: >>> On Sun, Feb 28, 2016 at 7:41 PM, sebb wrote: I thought I *had* configured www/roster; see my posting from 21:07 (else-thread) How should I have done it? >>> >>> I went back and looked closer. You configured www/roster/committer, >>> not www/roster. Here's my config: >>> >>> >>> PassengerBaseURI /whimsy/roster >>> PassengerAppRoot /var/whimsy/www/roster >>> PassengerAppEnv development >>> Options -Multiviews >>> # CheckSpelling Off >>> >>> >>> Alias /whimsy/roster/ /var/whimsy/www/roster >> >> Still does not work. >> >> I get >> >> The requested URL /roster/committee/ was not found on this server. >> >> The requested URL /roster/committer/ was not found on this server. >> >> For http://my.whimsy/roster/ I get a directory listing of www/roster > > I'm clearly not getting that. Note that I access my copy of whimsy as > http://localhost/whimsy, so I would access the roster application as > http://localhost/whimsy/roster. > > If you are trying to 'mount' the roster application at the root of > your webserver, your setup would look something like this: > I'm using virtual hosts for different apps (projects, reports, etc) so I guess this is closer to what I need. > Alias /roster/ /srv/whimsy/www/roster/committer > > PassengerBaseURI /roster > PassengerAppRoot /srv/whimsy/www/roster/committer > PassengerAppEnv development > Options -Multiviews > Doesn't work. However this does: Alias /roster/ /srv/whimsy/www/roster PassengerBaseURI /roster PassengerAppRoot /srv/whimsy/www/roster PassengerAppEnv development Options -Multiviews Yay! > Should that not work... have you ever run Docker or Vagrant before? I I have got Docker; don't think I have used Vagrant. > probably can quickly set up one or the other. My thoughts are that > once you have a working system that you can compare against, spotting > the difference with your current setup would be much easier. And that > could lead to updates to the documentation to help others. I think it would help to document what the paths represent, and for file paths, what one would expect to find there. e.g. I assume PassengerAppRoot is a local path, and need to point to a rake app, i.e. a whimsy directory containing config.ru. This should make it easier to check the settings are correct. > - Sam Ruby
