Bullet Train – Rails-based SaaS framework
bullettrain.co
Bullet Train – Rails-based SaaS framework
1–10 of 148 posts
Re: Bullet Train – Rails-based SaaS framework
#2Kind of funny that "starting you off with all the features that are the same in every product" is a good description of the original motivation for Rails itself. Which is not criticism, the goalposts have moved quite a bit the past few decades.
Re: Bullet Train – Rails-based SaaS framework
#3Kind of funny that "starting you off with all the features that are the same in every product" is a good description of the original motivation for Rails itself. Which is not criticism, the goalposts have moved quite a bit the past few decades.
I see your point but I think this is at a level of abstraction that Rails never set out to solve.
Rails is arguably “technology batteries included”, whereas this is more like “product batteries included”. There are many Rails sites that wouldn’t use these features, however there aren’t many Rails sites that wouldn’t use ActiveRecord or HTML rendering.
Re: Bullet Train – Rails-based SaaS framework
#4Kind of funny that "starting you off with all the features that are the same in every product" is a good description of the original motivation for Rails itself. Which is not criticism, the goalposts have moved quite a bit the past few decades.
I don't think so. This boils down to a set of already installed, pre-configured gems in a starter project. That's always how Rails has worked. When I was consulting, I had exactly this for myself before Bullet Train ever existed - a pre-configured rails repo that I just forked when I started something new.
The thing w/ Bullet Train is that so much work is done for you, that if you don't like an opinion or two that they hold, you really should start from scratch, as tearing things out will just take longer. Its the downside of having so much integration and configuration already done.
Re: Bullet Train – Rails-based SaaS framework
#5This doesn't really have the types of features I would personally want as someone who has done a lot of rails development in the past.
The types of things I tend to need to set up in any modern app is SSO integration, React integrated on the frontend, etc... These are annoying things I have to integrate every time I build something and are more or less industry standard at this point.
Re: Bullet Train – Rails-based SaaS framework
#6It'd be nice if there was a way to try the demo without signing in.
That said, this looks like a good product.
Are there other similar/competing things for Rails, and are there other competing SaaS-in-a-box things for other frameworks?
Re: Bullet Train – Rails-based SaaS framework
#7It'd be nice if there was a way to try the demo without signing in. That said, this looks like a good product. Are there other similar/competing things for Rails, and are there other competing SaaS-in-a-box things for other frameworks?
Re: Bullet Train – Rails-based SaaS framework
#8It'd be nice if there was a way to try the demo without signing in. That said, this looks like a good product. Are there other similar/competing things for Rails, and are there other competing SaaS-in-a-box things for other frameworks?
https://github.com/smirnov-am/awesome-saas-boilerplates collects such frameworks, it lists 4 for Rails.
Re: Bullet Train – Rails-based SaaS framework
#9I evaluated Bullet Train last year when building an MVP for a client. Ended up using Jump Start Rails instead. Main reasons:
1. The hybrid approach to iOS and Android apps with JSR were better than what BT had to offer
2. There was a lot less to learn about the mental model of how JSR was built via Bullet Train. It was basically pay, pull down, configure, and get going with JSR. BT has things like SuperScaffolding, an abstraction layer on CanCanCan, etc. I didn't want to have to ramp up on those to decide whether they were better than the alternatives.
YMMV of course. JSR is a paid app and IIRC BT was at the time too... but looks like maybe not anymore?
Re: Bullet Train – Rails-based SaaS framework
#10This doesn't really have the types of features I would personally want as someone who has done a lot of rails development in the past. The types of things I tend to need to set up in any modern app is SSO integration, React integrated on the frontend, etc... These are annoying things I have to integrate every time I build something and are more or less industry standard at this point.
> This doesn't really have the types of features I would personally want as someone who has done a lot of rails development in the past.
This is relative.
> React integrated on the frontend
This is something that I don't want at all. Regarding the SSO, without reading the code, I'm sure you are able to accomplish it using devise (included in their framework)