4 ms·

Project looks awesome, but I was a little confused. Is this a centralized user management with payments proxy to many application backends? https://userdashboa

Project looks awesome, but I was a little confused. Is this a centralized user management with payments proxy to many application backends? https://userdashboard.github.io/home https://userdashboard.github.io/home The home page did a really good job explaining with images, but wanted to confirm.

deleted 7y ago
[deleted]
benologist 7y ago
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.
benologist 7y ago
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. module.exports = { before: async (req) => { switch (req.host) { case 'domain1.com': req.dashboardServer = 'domain1.com' req.applicationServer = 'http://localhost:7000' req.applicationServerToken = 'shared secret' break } } } 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. [1] https://userdashboard.github.io/request-handlers https://userdashboard.github.io/request-handlers [2] https://userdashboard.github.io/package-json https://userdashboard.github.io/package-json

deleted 7y ago

[deleted]

benologist 7y ago

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.

benologist 7y ago

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. module.exports = { before: async (req) => { switch (req.host) { case 'domain1.com': req.dashboardServer = 'domain1.com' req.applicationServer = 'http://localhost:7000' req.applicationServerToken = 'shared secret' break } } } 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. [1] https://userdashboard.github.io/request-handlers https://userdashboard.github.io/request-handlers [2] https://userdashboard.github.io/package-json https://userdashboard.github.io/package-json