Lessons I learned while creating my SaaS with Rails
samurails.com
Lessons I learned while creating my SaaS with Rails
1–10 of 23 posts
Re: Lessons I learned while creating my SaaS with Rails
#2Extra (maybe obvious) tip for #7: Get yourself a free Slack/Hipchat account and start curling those errors and exceptions to it. Super easy, way less hassle than email, and free push notifications to your phone if you've got the app installed.
Re: Lessons I learned while creating my SaaS with Rails
#3Extra (maybe obvious) tip for #7: Get yourself a free Slack/Hipchat account and start curling those errors and exceptions to it. Super easy, way less hassle than email, and free push notifications to your phone if you've got the app installed.
Great tip, I will set it up!
Re: Lessons I learned while creating my SaaS with Rails
#4Thanks for the insight into Elastic Beanstalk; I'm looking into it now.
Regarding Coffeescript and classes, I think that's a really poor reason to use it. IMO Coffeescript has had its day and if you want class sugar, just use ES6. You're already using a compilation step in your process so why not use it to work with something standard?
Re: Lessons I learned while creating my SaaS with Rails
#5Thanks for the insight into Elastic Beanstalk; I'm looking into it now. Regarding Coffeescript and classes, I think that's a really poor reason to use it. IMO Coffeescript has had its day and if you want class sugar, just use ES6. You're already using a compilation step in your process so why not use it to work with something standard?
You're probably right indeed! I was just looking into refactoring some code, found that and thought it was pretty cool. Plus Rails comes with CoffeeScript by default.
ES6 is pretty sweet (pun intended) and will probably make CS kinda useless in the future. I'll look into it however I think that currently CoffeeScript is a bit of a standard in the Rails world.
Re: Lessons I learned while creating my SaaS with Rails
#6Thanks for the insight into Elastic Beanstalk; I'm looking into it now. Regarding Coffeescript and classes, I think that's a really poor reason to use it. IMO Coffeescript has had its day and if you want class sugar, just use ES6. You're already using a compilation step in your process so why not use it to work with something standard?
You're probably right indeed! I was just looking into refactoring some code, found that and thought it was pretty cool. Plus Rails comes with CoffeeScript by default. ES6 is pretty sweet (pun intended) and will probably make CS kinda useless in the future. I'll look into it however I think that currently CoffeeScript is a bit of a standard in the Rails world.
That is a fair point, if I'm using Rails I actually just use plain old JS as I don't personally like CS.
I just found a comment by a Rails contributor [1] which says ES6 will be supported out of the box in Rails 5, which would be ideal. I can't find anything newer to back that up though. I think it might be via ES6 support baked into sprockets.
[1] http://kryptonlabs.com/blog/2015/10/25/whats-new-in-rails-5/...
Re: Lessons I learned while creating my SaaS with Rails
#7Great blog post! Can't you use Angular or React with RoR when rendering in the backend? I am pretty sure you can.
Re: Lessons I learned while creating my SaaS with Rails
#8You're going to cry the day when you try to clone your Elastic Beanstalk environment to do a rolling upgrade, and the termination of the first wipes away your RDS db with it.
It's undocumented, but you'd be better off creating the db separately, not within the beanstalk wizard, to avoid this
Re: Lessons I learned while creating my SaaS with Rails
#9Great blog post! Can't you use Angular or React with RoR when rendering in the backend? I am pretty sure you can.
Yes, you can just use Rails as an API and create a frontend SPA. But in my opinion, it's faster to write in the 'old way' for a MVP instead of creating 2 different applications (one frontend, one backend). For the future, I'm actually thinking about rewriting the frontend using SPA technologies.
Re: Lessons I learned while creating my SaaS with Rails
#10You're going to cry the day when you try to clone your Elastic Beanstalk environment to do a rolling upgrade, and the termination of the first wipes away your RDS db with it. It's undocumented, but you'd be better off creating the db separately, not within the beanstalk wizard, to avoid this
Wouah, thanks for the heads up. I had no idea about this, I'm gonna look into it and re-create the RDS db myself.