3 ms·
The great thing about a static app architecture is that for things like administrative functions you can usually easily build an entirely separate interface and
by mbleigh 13y ago
The great thing about a static app architecture is that for things like administrative functions you can usually easily build an entirely separate interface and application utilizing the same back-end resources.
Security through obscurity is never sufficient, and static architecture makes you think through those concerns more thoroughly before deploy. See http://www.staticapps.org/articles/authentication-and-authorization http://www.staticapps.org/articles/authentication-and-author... for more on that subject.
As to development vs production, minifying etc. that's something we're trying to solve with multi-environment hosting at Divshot.
- BinaryIdiot 13y agoIt's not typically cost effective or realistic to build an entirely separate interface for administrative functionality (in fact, for user experience purposes, it's typically better to be able to administrator changes in place). As I mentioned it's doable but requires additional upfront work that I have never had time to do on any project I get to work on. Obviously security through obscurity isn't sufficient as I said it wasn't security :) but I don't see any reason why a static architecture should make you think about those issues any more or less; you should already be doing so.