We briefly discussed this before, but I didn't find a ticket for it, so I made this one.
Let's consider turning Atlas into a page on Tor Metrics. It could live under "Home >> Services >> Atlas".
From a technical perspective I think we could add Atlas as Git submodule and copy its index.html into a JSP, so that we can include the Tor Metrics banner and footer. And we'd copy over all required JS files.
It would certainly help to get rid of Atlas' navbar and footer and make sure that it works well with Metrics' style file.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
karsten: I'm going to need to have some idea of how to set up a dev environment for this. Will things just work if I tell Eclipse to do Tomcat things with metrics-web?
irl: It's complicated! :) I'd say don't worry about the technical integration part. Better import Metrics' CSS file into Atlas and make sure the page looks okay there (though without banner and footer). I'll happily do the rest.
I've now merged the metrics theme with Atlas and rebranded it as Relay Search. For now we can display a message at the top of the page to explain to users about the rebranding. This will be merged and continue to be served by the static mirrors for now, waiting for embedded Jetty in metrics-web before merging into the metrics-web codebase.
Javascript libraries have been updated for compatibility with the versions used by metrics-web, including jQuery and bootstrap.
The only issue that has been found with compatibility is the "return to top" button used on the website which uses a URL fragment, conflicting with the URL routing for the javascript application.
Many resources are now loaded from metrics.torproject.org instead of being local to the Atlas codebase, which is something we should be aware of but is not a large problem as that's where we'll want them to be loaded from in the future anyway.
Currently services.html has:
<li><a href="https://atlas.torproject.org/" target="_blank">Atlas</a> displays data about single relays and bridges in the Tor network.</li>
Let's change this to:
<li><a href="https://atlas.torproject.org/">Relay Search</a> displays data about single relays and bridges in the Tor Network.</li>
(The omission of the _blank target is deliberate, as Relay Search now matches the Metrics branding this should be seamless for users.)
Trac: Description: We briefly discussed this before, but I didn't find a ticket for it, so I made this one.
Let's consider turning Atlas into a page on Tor Metrics. It could live under "Home >> Operation >> Atlas".
From a technical perspective I think we could add Atlas as Git submodule and copy its index.html into a JSP, so that we can include the Tor Metrics banner and footer. And we'd copy over all required JS files.
It would certainly help to get rid of Atlas' navbar and footer and make sure that it works well with Metrics' style file.
to
We briefly discussed this before, but I didn't find a ticket for it, so I made this one.
Let's consider turning Atlas into a page on Tor Metrics. It could live under "Home >> Services >> Atlas".
From a technical perspective I think we could add Atlas as Git submodule and copy its index.html into a JSP, so that we can include the Tor Metrics banner and footer. And we'd copy over all required JS files.
It would certainly help to get rid of Atlas' navbar and footer and make sure that it works well with Metrics' style file. Status: assigned to accepted
The index.html will become a JSP, and the JavaScript application will be loaded as it currently is, just with the codebase merged into the metrics-web codebase.
Later there is a possibility that portions will be rewritten in Java, but this will depend on a Java Onionoo client (metrics-bot kind of has one, but it's not anywhere near complete).
We should dynamically generate the fallback_dir.js script from tor's source code in order to have it automatically kept up to date. Alternatively, this could be added to Onionoo.
If metrics-lib does not already have a parser for this file format, it would probably also be a good idea to add one.
The SVG tooltips used in the graphs are broken with bootstrap 3.3.7 but work with 3.3.5. The fix appears to be to replace the getPosition function from 3.3.5 in 3.3.7 and we should ensure we do this. For now, Relay Search is hosting its own bootstrap js.
I have updated comment:15 to have the set of remaining tasks to do the actual inclusion work, and created child tickets for each of the individual tasks.
update the link from the metrics.tpo services page
I already did this as part of merging #25255 (moved) and #25258 (moved), because I thought it was an oversight. Looks like it wasn't. Anyway, it's already done now.