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
  • #25393

Closed (moved)
Open
Opened Mar 01, 2018 by iwakeh iwakeh@iwakeh

Integration of RelaySearch

RelaySearch (former Atlas) recently was integrated into Metrics code bases more tightly. It is working fine, but should be adapted more to facilitate better maintenance in future.

One question that needs to be decided:

Should RelaySearch be developed as a part of metrics.tp.o that can also be served stand-alone, which is the current situation or just as a part of metrics.tp.o? The latter would reduce the amount of files and maintenance for RelaySearch once the integration is completed, as it currently duplicates many parts of metrics-web (fonts, css partially, etc), which will cost more maintenance in future.

This ticket should serve for the discussion of the above question and for deriving the next necessary steps. (There is also a related ticket for metrics-web, see #25392 (moved))

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#25393