Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #25322

Closed (moved)
Open
Opened Feb 21, 2018 by Hiro@hiro🏄

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

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.

  2. Could we just offer a redirect through htaccess?

  3. 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.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#25322