It’s not that the reports themselves are no longer useful – but the format in which they are displayed, and the limited interactivity of them. I need to do more than just get some read only data. I need to also drill in deeper and get more information from accounts, users, podcasts, etc.
I Don’t Want A /admin Route
I’ve been hesitant to add in a “/admin” route on SignalLeaf for a lot of reasons. Then a few weeks ago, it suddenly dawned on me – I don’t need to add a “/admin” route set to the main app itself. I can build a separate admin app, and have it focused 100% on the administrative tools, reports and dashboards that I need.
So that’s what I did over the last week or two. I set up a new website, with it’s own authorization configuration, dedicated entirely to my needs for administrative tools. It’s working out really well for me, too. I don’t have to worry about polluting the core SignalLeaf app w/ administrative tools. I don’t have to worry about re-deploying the core system when I change the admin tools. I don’t even have to worry about the admin tools crashing, because I’m the only one that will ever use them. If the admin tools crash, who cares. They are on a separate site, and will not affect the core of SignalLeaf at all.
Build A Separate Admin App
If you’re looking at building an administrative section of your SaaS or web application, you might want to think about creating a completely separate application. It’s been a real breath of fresh air for me and SignalLeaf.
Of course, I needed a good authorization system to handle the admin site. I want something simple to require authorization for all routes on the site, and I wasn’t quite happy with the ones that I was finding. Far too many authentication systems in NodeJS land claim authorization as well, then don’t deliver. So I built my own authorization system – mustBe – but that’s another blog post to come soon.