Explore to move perf-html.io to profiler.firefox.com

As discussed before, I wanted to get the idea of changing domains for the profiler frontend to profiler.firefox.com into the next phase.

With the move, we should also consistently name all peripherals, like the addon. I’d propose to move from the current “Gecko Profiler” to “Firefox Profiler” (but don’t really have strong opinions on it).

The main benefits of the migrations would be:

1. Firefox domain brand to underline the trustworthiness of the tool & data handling
2. Unified “Profiler” product that includes the recording and analysis capabilities

Tradeoffs:

• Migration of domain, existing links and existing users (mostly redirects and updating the addon?)

Questions

• Does this have stricter legal or privacy requirements?
• How does netlify handle subdomains for deploy previews?

Thoughts?

Decisions

Useful to do.

1. No stricter requirements because of firefox.com domain
2. netlify should work fine
3. Needs final decision on sub-domain name

[julienw]

@past right, I’ll outline the remaining tasks in a comment tomorrow and file bugs.

[julienw]

https://bugzilla.mozilla.org/show_bug.cgi?id=1506863 filed for the new subdomain entry. I added the entry in netlify too, and will continue the configuration once the mozilla bug is fixed.