3 ms·

Great idea, but I agree with codingdave. Too opinionated and only makes things more difficult. The more important things to a SaaS is the actual product and no

Great idea, but I agree with codingdave. Too opinionated and only makes things more difficult. The more important things to a SaaS is the actual product and not the authentication / backend / DB. 99.99999% of all early stage SaaS have absolutely no need for even 2FA, let alone multitudes of authentication. It's just a lot of clutter and cruft for an MVP, which is what should be built. I think a better framework would be focusing on the essentials, a very simple username + pwd, drop-in DB with a generic schema (Put it in JSON and export it from a file, rather than wrapping in an ODM / ORM object). Finally you could wrap it up with a nice landing page template. I would pay money for someone to give me a light, nice-looking landing page that is easily templated and it focuses on being light. --- One issue with this kind of project is that it is difficult to adopt and build on to. It might be a great starting place, but it presents a fork of either total rebuild or stumbling through unfamiliar, cluttered code.

anandchowdhary 7y ago
Thanks, madamelic. Like I said to codingdave, Staart was built as a tool for me, and I published it to see if others might want to use it too. I agree with you that 2FA, auth rules for teams, etc., may be overkill, but the projects I'm working on (primarily focused as enterprise software alternates) all needed them, which is how Staart was born. I am more and more pushed in the direction of a "check the features you want to keep and build your Staart package". Perhaps that last part can be solved with thorough documentation about how to build on top of it. I am currently doing this by only working on project-specific files ("core product") and letting Staart handle auth/etc., but the second these need to be updated to be project-specific too, it will result in merge errors when updating Staart and so on. You're right, it's a problem I need to look into.

anandchowdhary 7y ago

Thanks, madamelic. Like I said to codingdave, Staart was built as a tool for me, and I published it to see if others might want to use it too. I agree with you that 2FA, auth rules for teams, etc., may be overkill, but the projects I'm working on (primarily focused as enterprise software alternates) all needed them, which is how Staart was born. I am more and more pushed in the direction of a "check the features you want to keep and build your Staart package". Perhaps that last part can be solved with thorough documentation about how to build on top of it. I am currently doing this by only working on project-specific files ("core product") and letting Staart handle auth/etc., but the second these need to be updated to be project-specific too, it will result in merge errors when updating Staart and so on. You're right, it's a problem I need to look into.