Use Case 2: No frontend. Only Backend

[joncodo]

From @seanspeaks

One other new "Use Case" to call out/carve out into either this repo or the core or the docs: To actually integrate Frigg into your application well, I've settled on a default approach of having all Management API requests expect x-Frigg-appUserId and x-Frigg-appOrgId headers, which invokes the loadUserManager middleware, which finds or creates the provided users by corresponding ID. "App" in this case is "your app".

[joncodo]

From @seanspeaks

I like the idea of optional frontend install. The hope/goal is that you need some sort of frontend to understand how the app works and how you might incorporate into your existing application, but that it would likely be a throwaway part of the code. The other important part (not mentioned here yet) is that we have frontend needs for integrations where you're allowed to call in an iFrame or html/js/css code (bring-your-own-framework, just point to a valid URL) (Front, Zendesk, HubSpot's "Advanced IFRAME actions", Salesforce, etc.). Those aren't needed for any "getting started", but it's a nice option to have UI's dedicated to integrations be managed in the same place that the backend/business logic is managed.

[joncodo]

So the install will ask you if you want to install the front end. This is low priority since users can just delete the frontend folder when they want to.