Hosting - Local Hostin

[tbrooke]

I had planned to host B1 myself then discovered that it was free on line so why do it myself - What concerns me is that with the Online Admin App my website is stuck with the B1 apps domain as far as I can tell - With Self Hosting I get my own domain but the Freeshow sync links to B1.Admin and I don't see a setting to change it. I guess I could change it in Freeshow but it looks like I would have to build it myself I didn't see a setting to change it - Also I am unsure how the API and MCP would work with the online version without some authentication.

What is the Best way to solve this?

[geekyNads]

The main trade-off seems to be between using the hosted B1 Admin App for convenience and self-hosting for full control over the domain and authentication.

For self-hosting, it would be useful if FreeShow exposed the B1 Admin/API endpoint as a configurable setting rather than having the URL hard-coded into the application. That would allow users to point FreeShow at something like https://admin.example.com without having to build a custom version of FreeShow.

For the API/MCP side, I would also expect authentication to be handled by the self-hosted B1 instance (for example, API keys, OAuth, or another supported authentication mechanism), rather than relying on the hosted B1 Admin service.

So ideally the configuration would look something like:

• B1 Admin URL: configurable
• API URL: configurable
• Authentication: configurable/handled by the B1 instance
• FreeShow sync: uses the configured B1 endpoint

If these URLs are currently hard-coded, adding a configuration option for the B1 endpoint would probably be the cleanest solution and would avoid requiring users to maintain a custom FreeShow build.