Update on issue of aw-watcher-web reporting unknown hostname

[DivineMK]

I come from #67 and see that the issue is closed already as OP main issue was resolved, so I want to track this specific issue again.

The issue is with buckets from aw-watcher-web having "unknown" as hostname.

[losogudok]

Workaround I found:

1. Build extension according to README
2. Change hostname "unknown" to your computer hostname and PORT to 5600 (dev version uses 5666)
3. Load extension to Chrome (dont forget to enable dev mode)
4. Enjoy!

[soqb]

that doesn't work on firefox. the default release channel doesn't let you use unsigned addons.

[Cyber5imon]

Here are the basic steps to sign your own custom Firefox add-on:

1. Get the credentials from AMO.
2. Download and Install NodeJs.
3. Install web-ext using this command: npm install --global web-ext
4. Go to your add-on directory.
5. Run this command: web-ext sign --api-key="JWT issuer" --api-secret="JWT secret"
6. A folder named "web-ext-artifacts" is created containing your signed XPI file ready to be installed!

[DivineMK]

Thank you for sharing the workaround. I will keep the issue open until this can be integrated into the extension as an option.

[simonmysun]

I wonder if it would be better to add a optional input on https://github.com/ActivityWatch/aw-watcher-web/blob/e2cc98c3ac02cba86f8ee2d7141f71d47ebcacc0/static/popup.html