Opened 10 months ago

Closed 8 months ago

#25322 closed defect (invalid)

Finding a way to serve search.tpo for the different portals

Reported by: hiro Owned by: tpa
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi,

I have a machine that will be serving search results for the coming web portals.
This is a Solr installation + a pyramid app to display the search results in html.

This machine lives on 195.201.2.191.

Since the portals are static html pages, I am trying to think of a way so that at the local url '/search' we can serve the search result of the search service.

So for example support.torproject.org/search would display the search results for the support portal from 195.201.2.191.

Now there are a few issues that we should consider.

  1. Onion service

The search service will be behind its own onion service.

  1. Could we just offer a redirect through htaccess?
  1. should we have a search.tpo service and that's it?

Points 2. and 3. could be complicated in terms of user experience. I'd say that if a user search something they do not necessarly expect to be taken to a different window or different page.

Any other ideas are welcomed.

Child Tickets

Change History (2)

comment:1 Changed 10 months ago by arma

Sounds like something to get the ux team in on discussing.

I'd be tempted to move this to the website component too, since it's not really a sysadmin thing at this point -- it's still a "how do we want our website service to behave" thing.

One option to explore is whether a proxypass approach can work -- the frontend webserver would pass requests to the search backend if they are for certain urls.

comment:2 Changed 8 months ago by weasel

Resolution: invalid
Status: newclosed

<hiro> you can close all of them thanks weasel

Please reopen when something actionable for tpa shows up

Note: See TracTickets for help on using tickets.