Show HN: SaaS application boilerplate
21–30 of 78 posts
Re: Show HN: SaaS application boilerplate
#22Re: Show HN: SaaS application boilerplate
#23> If you experience such errors: > In the database remove the record from alembic_version table > Remove any files from your computer under app/migrations. I'm not sure advising users to delete all their migrations is the right thing to do (which is what this appears to be doing).
As for the problem overall, I didn't find a good solution for it. Maybe you can help?
Re: Show HN: SaaS application boilerplate
#24I remember when there was a Rails one... It worked great, until it didn't. It was, however, a great learning tool on how you could role your own Rails SaaS.
Re: Show HN: SaaS application boilerplate
#25Earlier quoted context omitted.
Big fan of BulletTrain - it's a big accelerant for building a SAAS (literally worth a couple of months of development time).
I saw them, read their blog (for inspirational purposes of course :) and even wrote them. But I believe it's really overpriced. I'm working on the paid modules/components but I will keep the price moderate.
Re: Show HN: SaaS application boilerplate
#26Earlier quoted context omitted.
I saw them, read their blog (for inspirational purposes of course :) and even wrote them. But I believe it's really overpriced. I'm working on the paid modules/components but I will keep the price moderate.
FWIW - I found it valuable as it provided both the sort of modules/components as you're describing but also a set of productivity accelerating things like the SuperScaffolding etc to really apply those into an application along with a well thought out system to extend all of that when I hit the limits.
Check some of them on our website https://www.saasforge.dev in the "Coming soon" section.
Re: Show HN: SaaS application boilerplate
#27Re: Show HN: SaaS application boilerplate
#28Re: Show HN: SaaS application boilerplate
#29For a SaaS framework you usually need at least: integration with a billing provider (almost always Stripe nowadays), web hook handling for a bunch of services (or a generic way of handling webhooks easily), some kind of social auth integration framework or ready built integrations for a bunch of services, bulk email support, a modular dashboard (seems you have the start of this?), a landing page generator with pricing tiers that integrate with the backend somehow, a team management option for users.
Have a look at Laravel Spark, or some of the other premium SaaS frameworks available right now for what people a now expecting of these frameworks.
Also, I'm a little dubious about your license (seems to be fixed now?). You need to be crystal clear about whether or not this is open source, or if you are trying to sell a product. "SaaS as a Service" (or SaaSaaS as I like to call it) seems to have blown up recently, but I'm usually wary of things like this. When making a SaaS, I like to keep margins and fuss as low as possible, and including a piece of software that might cause me legal trouble down the track is a big no-no.
Re: Show HN: SaaS application boilerplate
#30I appreciate the efforts being done in this space, but I don't think this is launch ready yet. It doesn't include some of the things that make a SaaS a SaaS, and not a typical user sign up web app with admin panel. For a SaaS framework you usually need at least: integration with a billing provider (almost always Stripe nowadays), web hook handling for a bunch of services (or a generic way of handling webhooks easily)…
I totally agree about the functionality. Stripe integration will be the next feature I will add. And even so, I still believe this boilerplate can save you at least a week of work. I already used it for my other projects and I can confirm it.
Dashboard UI is already done and I'm going to add more modules/components to make it easier to use. Do you have any suggestions what it would be?
Laravel Spark is one of the resources for inspiration :))) I just didn't implement everything I would like to - yet.
I fixed the license, the boilerplate can be used for any purposes (except ones against the law) - this version. Because I'm working on the commercial extension of it - and it will be a completely separate story. But even with using of commercial modules (or version) you will be totally free to use it and it will be completely white-labeled.
Another situation when you are trying to modify and resell a product but it has nothing to do with making a SaaS, right?