You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Olemis Lang <ol...@gmail.com> on 2013/03/21 16:51:53 UTC
Allura search context (VM down?) WAS: [BLOODHOUND] Query Builder
(Search / Custom Query)
Hi!
:)
We were discussing a bit about search contexts for Apache™ Bloodhound and ...
On 3/21/13, Olemis Lang <ol...@gmail.com> wrote:
> On 3/20/13, Joe Dreimann <jo...@wandisco.com> wrote:
>> On 20 Mar 2013, at 20:53, Olemis Lang <ol...@gmail.com> wrote:
>>> On 3/20/13, Joachim Dreimann <jo...@wandisco.com> wrote:
>>> [...]
>>>> On 14 March 2013 19:47, Andrej Golcov <an...@digiverse.si> wrote:
>>> [...]
>>>>> We can set default product filter based on active product and use
>>>>> global search if user navigates directly to global search url - I
>>>>> think, Olemis suggested something like this.
>>>>
>>>> I believe search should always be global unless the user chooses
>>>> otherwise.
>>>
>>> what does this mean exactly ? Let's focus on the following situation .
>>> User reads let's say a wiki page in product P and searches for word W
>>> by using search input box in the header . In your opinion is there any
>>> value for getting results from other projects , even potentially not
>>> provide any result for the active project ?
>>
>> Yes.
> [...]
>
> My point is somehow similar to this :
>
> http://sourceforge.net/p/allura/tickets/?source=navbar
>
> In there you'll find focused product-specific Search Tickets box and
> broad Search box in body header . So user will choose search scope
> explicitly . The only difference being that our proposal for focused
> search (by default) should span over multiple resources (not just
> tickets) . That means that I basically agree with you on user intents
> within product boundaries . OTOH I disagree on not to limit the
> (default) scope of search to active product . Systematically leading
> the user out of product boundaries is not a good practice afaict
>
> PS: I actually don't know whether the search box at the top is really
> part of Allura of a SF.net specific add-on .
>
I was trying to confirm my hypothesis but ...
{{{
#!sh
$ wget -O /dev/null http://allura-vm.apache.org/
--2013-03-21 10:43:02-- http://allura-vm.apache.org/
Resolving allura-vm.apache.org... 140.211.11.147
Connecting to allura-vm.apache.org|140.211.11.147|:80... failed:
Connection timed out.
Retrying.
[...]
}}}
Is the demo VM down ?
--
Regards,
Olemis.
Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: Allura search context (VM down?) WAS: [BLOODHOUND] Query Builder
(Search / Custom Query)
Posted by Stefano Invernizzi <st...@gmail.com>.
I'm sorry for my late answer. When I set up the forge, I had to explicitely
allow connections on port 80, in order to make it reachable. After doing
so, I didn't have any problem. I don't know if this is useful.
Anyway, I can see the demo VM is now reachable from everywhere, so I guess
the problem has been solved, except we still have to start using SSL.
Stefano
2013/3/22 Tim Van Steenburgh <tv...@gmail.com>
> I'll take care of getting this set up.
>
> Tim
>
> On Friday, March 22, 2013 at 12:47 PM, Dave Brondsema wrote:
>
> > We have to set up SSL https://issues.apache.org/jira/browse/INFRA-6039
> >
> > On 3/21/13 2:25 PM, Dave Brondsema wrote:
> > > On 3/21/13 8:51 AM, Olemis Lang wrote:
> > > > Hi!
> > > > :)
> > > >
> > > > We were discussing a bit about search contexts for Apache™
> Bloodhound and ...
> > > >
> > > > [snip]
> > > >
> > > > I was trying to confirm my hypothesis but ...
> > > >
> > > > {{{
> > > > #!sh
> > > >
> > > > $ wget -O /dev/null http://allura-vm.apache.org/
> > > > --2013-03-21 10:43:02-- http://allura-vm.apache.org/
> > > > Resolving allura-vm.apache.org (http://allura-vm.apache.org)...
> 140.211.11.147
> > > > Connecting to allura-vm.apache.org (http://allura-vm.apache.org)|140.211.11.147|:80...
> failed:
> > > > Connection timed out.
> > > > Retrying.
> > > >
> > > > [...]
> > > > }}}
> > > >
> > > > Is the demo VM down ?
> > >
> > > Yes, it is. Tim recently got sudo access to try to fix it (I guess
> maybe a
> > > process had died) but now it's only reachable from localhost:80 and
> not externally.
> > >
> > > Stefano, when you set it up did you have any issues like that? Any
> ideas?
> >
> >
> >
> > --
> > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> > <><
> >
> >
>
>
>
Re: Allura search context (VM down?) WAS: [BLOODHOUND] Query
Builder (Search / Custom Query)
Posted by Tim Van Steenburgh <tv...@gmail.com>.
I'll take care of getting this set up.
Tim
On Friday, March 22, 2013 at 12:47 PM, Dave Brondsema wrote:
> We have to set up SSL https://issues.apache.org/jira/browse/INFRA-6039
>
> On 3/21/13 2:25 PM, Dave Brondsema wrote:
> > On 3/21/13 8:51 AM, Olemis Lang wrote:
> > > Hi!
> > > :)
> > >
> > > We were discussing a bit about search contexts for Apache™ Bloodhound and ...
> > >
> > > [snip]
> > >
> > > I was trying to confirm my hypothesis but ...
> > >
> > > {{{
> > > #!sh
> > >
> > > $ wget -O /dev/null http://allura-vm.apache.org/
> > > --2013-03-21 10:43:02-- http://allura-vm.apache.org/
> > > Resolving allura-vm.apache.org (http://allura-vm.apache.org)... 140.211.11.147
> > > Connecting to allura-vm.apache.org (http://allura-vm.apache.org)|140.211.11.147|:80... failed:
> > > Connection timed out.
> > > Retrying.
> > >
> > > [...]
> > > }}}
> > >
> > > Is the demo VM down ?
> >
> > Yes, it is. Tim recently got sudo access to try to fix it (I guess maybe a
> > process had died) but now it's only reachable from localhost:80 and not externally.
> >
> > Stefano, when you set it up did you have any issues like that? Any ideas?
>
>
>
> --
> Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
>
Re: Allura search context (VM down?) WAS: [BLOODHOUND] Query Builder
(Search / Custom Query)
Posted by Dave Brondsema <da...@brondsema.net>.
We have to set up SSL https://issues.apache.org/jira/browse/INFRA-6039
On 3/21/13 2:25 PM, Dave Brondsema wrote:
> On 3/21/13 8:51 AM, Olemis Lang wrote:
>> Hi!
>> :)
>>
>> We were discussing a bit about search contexts for Apache™ Bloodhound and ...
>>
>> [snip]
>>
>> I was trying to confirm my hypothesis but ...
>>
>> {{{
>> #!sh
>>
>> $ wget -O /dev/null http://allura-vm.apache.org/
>> --2013-03-21 10:43:02-- http://allura-vm.apache.org/
>> Resolving allura-vm.apache.org... 140.211.11.147
>> Connecting to allura-vm.apache.org|140.211.11.147|:80... failed:
>> Connection timed out.
>> Retrying.
>>
>> [...]
>> }}}
>>
>> Is the demo VM down ?
>>
>
> Yes, it is. Tim recently got sudo access to try to fix it (I guess maybe a
> process had died) but now it's only reachable from localhost:80 and not externally.
>
> Stefano, when you set it up did you have any issues like that? Any ideas?
>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: Allura search context (VM down?) WAS: [BLOODHOUND] Query Builder
(Search / Custom Query)
Posted by Dave Brondsema <da...@brondsema.net>.
On 3/21/13 8:51 AM, Olemis Lang wrote:
> Hi!
> :)
>
> We were discussing a bit about search contexts for Apache™ Bloodhound and ...
>
> [snip]
>
> I was trying to confirm my hypothesis but ...
>
> {{{
> #!sh
>
> $ wget -O /dev/null http://allura-vm.apache.org/
> --2013-03-21 10:43:02-- http://allura-vm.apache.org/
> Resolving allura-vm.apache.org... 140.211.11.147
> Connecting to allura-vm.apache.org|140.211.11.147|:80... failed:
> Connection timed out.
> Retrying.
>
> [...]
> }}}
>
> Is the demo VM down ?
>
Yes, it is. Tim recently got sudo access to try to fix it (I guess maybe a
process had died) but now it's only reachable from localhost:80 and not externally.
Stefano, when you set it up did you have any issues like that? Any ideas?
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><