Re:Show HN: Dashboard – self-hosted accounts, orgs and subsc...
by benologist on Wednesday August 21, 2019 @12:13PM
(#20758670)
This is implemented now, you can add a "before" request handler [1] and inspect the HOST header to check the domain and switch to an alternative configuration for that request. Dashboard compiles a global.packageJSON [2] holding your template, title, menu links etc and you can override that per-request by setting an alternative req.packageJSON for more individualized site settings too. Each of your application servers can serve a '/public/template-additional.css' and '/public/content-additional.css' to override the appearance as well.
This will work with per-site user accounts because the data was already partitioned by the dashboard server address. I think for sharing accounts across multiple websites you could just omit changing the req.dashboardServer.
Re:Show HN: Dashboard – self-hosted accounts, orgs and subsc...
by benologist on Tuesday August 20, 2019 @11:29PM
(#20754354)
You host a uniquely-configured copy of Dashboard for each web application. It only requires some small changes I can investigate tomorrow that would let you use one copy for multiple applications.
Re:Show HN: Dashboard – self-hosted accounts, orgs and subsc...
by CGamesPlay on Wednesday August 21, 2019 @12:45AM
(#20754627)
This is pretty interesting. Is there any prior art for things like this? User management that integrates with a specific target application, I mean, rather than say a generic SSO solution.
Another analogy is Facebook some years ago when Farmville and Zynga were incredibly popular. Facebook had this platform for apps where you wrote "FBML" which was a secured subset of HTML they would translate and then put into a frame on their website where people would use your app or game. If you were writing an app in that era you would fetch user information from their API etc. HTML has changed enough to skip an intermediate FBML language today.
Drupal and WordPress are also quite similar the main difference is your content, your application, resides on a second server instead of combined which is how Dashboard is stack-agnostic.
[1] https://github.com/darekkay/dashboard
https://userdashboard.github.io/home
The home page did a really good job explaining with images, but wanted to confirm.
[1] https://userdashboard.github.io/request-handlers
[2] https://userdashboard.github.io/package-json
https://xsolla.com
Another analogy is Facebook some years ago when Farmville and Zynga were incredibly popular. Facebook had this platform for apps where you wrote "FBML" which was a secured subset of HTML they would translate and then put into a frame on their website where people would use your app or game. If you were writing an app in that era you would fetch user information from their API etc. HTML has changed enough to skip an intermediate FBML language today.
Drupal and WordPress are also quite similar the main difference is your content, your application, resides on a second server instead of combined which is how Dashboard is stack-agnostic.