Making the default web client configurable

[lava]

The CLI supports setting the HAPPY_SERVER_URL to a custom API server, but the web app url for is hardcoded to app.happy.engineering.

Would it make sense to add a HAPPY_APP_URL as well, to support self-hosted deployments?

[bra1nDump]

All of the communication goes through the server at this moment.

If you self host the web app I assume it will just use the host where it is served from. So it should work out of the box mostly?

[lava]

I'm self-hosting both server and web app, and sure, the web app is configured to use the self-hosted server by default so once the cli client is connected to the correct backend server i can go to my web app and everything works out of the box.

But the initial web authn request by the CLI always goes to app.happy.engineering/terminal/connect

I think it would be nice if this could be configured to use the self-hosted instance instead.

[nelsonblaha]

This issue can probably be closed with a documentation update. The README.md should mention HAPPY_WEBAPP_URL alongside HAPPY_SERVER_URL in the environment variables section so other self-hosters can find it easily.
My setup for reference:

• Happy Server (backend) at https://happy.blaha.io
• Happy Web (frontend) at https://claude.blaha.io
• Multiple machines (nelnet + paul) with Happy CLI daemons connecting to the shared backend
• All fully self-hosted, no cloud services
  Works perfectly once you know about HAPPY_WEBAPP_URL!