Rails for everything
literallythevoid.com
Rails for everything
1–10 of 250 posts
Re: Rails for everything
#2The essential convention over configuration ideas still prevail when you want to pile on functionality quickly and without boilerplate.
Re: Rails for everything
#3If you want to only use sqlite, I suggest looking into litestack: https://github.com/oldmoe/litestack
I've not used it myself, but I am going to rewrite one of my projects that I only use locally from postgres to litestack. The benchmarks are incredible!
https://github.com/oldmoe/litestack/blob/master/BENCHMARKS.m...
Re: Rails for everything
#4I've been building some apps with stacks lately that are supposed to be more modern and performant. Namely an app with Spring Boot and another with Micronaut. Both had a React frontend. It really made me appreciate Rails' omakase approach. Just having a form that shows validation errors from the backend and having something as simple as Rails' flash messages isn't solved by the frameworks themselves and requires you to build it yourself or find a third-party solution that might or might not do the basic thing you need or might or might not be well-supported. Rails truly solves the problems 90% of web apps share. It might not be in a way that's perfect for your specific project but it will likely work and you can swap it out one you've validated you app or feature.
Re: Rails for everything
#5If you want to only use sqlite, I suggest looking into litestack: https://github.com/oldmoe/litestack I've not used it myself, but I am going to rewrite one of my projects that I only use locally from postgres to litestack. The benchmarks are incredible! https://github.com/oldmoe/litestack/blob/master/BENCHMARKS.m...
Is this really necessary given the advances with SQLite in Rails 8? What edge does this have over what’s included these days?
Re: Rails for everything
#6Inbuilt authentication is a very welcome addition. I've been using Django instead of Rails for the last 4-5 years (for business reasons) and that was one of the features Django provided which, upon reflection, seems like table stakes for a modern web app. The other glaring omission being an inbuilt admin interface -- which may have been added after I moved on.
Re: Rails for everything
#7Since Rails 8 I’ve even found myself using Rails + Sitepress over a static site generator. Kamal makes it really easy to run multiple lightweight sites on a cheap VPS writing even less configuration than Nginx, so it saves time up front.
Plus, nearly every static site ends up with someone saying, “oh I wish I could ____, but it’s a static site.” Instead of needing to pick a client-side-only solution, use a third party service, or integrate with a cloud Functions as a Service provider, Rails and a production-ready database are right there ready to help.
Re: Rails for everything
#8If you want to only use sqlite, I suggest looking into litestack: https://github.com/oldmoe/litestack I've not used it myself, but I am going to rewrite one of my projects that I only use locally from postgres to litestack. The benchmarks are incredible! https://github.com/oldmoe/litestack/blob/master/BENCHMARKS.m...
Is this really necessary given the advances with SQLite in Rails 8? What edge does this have over what’s included these days?
Litestack provides numerous benefits, but the largest is live replication to S3-compatible storage, which SQLite will not do by default.
Re: Rails for everything
#9Inbuilt authentication is a very welcome addition. I've been using Django instead of Rails for the last 4-5 years (for business reasons) and that was one of the features Django provided which, upon reflection, seems like table stakes for a modern web app. The other glaring omission being an inbuilt admin interface -- which may have been added after I moved on.
> The other glaring omission being an inbuilt admin interface -- which may have been added after I moved on.
with scaffolding and other rails generators with custom templates is that really a big asset? might not look amazing out of the box but you can find css templates easy enough too. maybe they should make an admin generator but rails is king of crud and if you need it ootb you can use one of the many gems.
Re: Rails for everything
#10After using SQLite in production for a little while, I don't think "SQLite is all you need." Migrations are a pain, so any long-lived app will eventually experience pain. As an example, SQLite doesn't have a way to add a NOT NULL constraint to an existing column; you have to rebuild the entire table using a temp table.