All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Rails with SQLite: Deployment Challenges and Production Considerations

By

ingve

8mo ago· 14 min readenInsight

Summary

This article discusses the author's experience building a Rails application using SQLite instead of traditional database services, highlighting the differences, challenges, and potential pitfalls when using SQLite in production environments. The author shares insights from deploying a side project with Rails 8's new features like Solid Cable, Solid Cache, and Solid Queue, along with Litestack, and warns about unexpected ways these simplified setups can lead to outages despite the author's 20 years of Rails deployment experience.

Key quotes

· 3 pulled
Between Litestack and the Rails 8 trifecta of Solid Cable, Solid Cache, and Solid Queue, it's easier than ever to spin up a Rails app that doesn't need a database service, or a redis service, or a file storage service
It's great to simplify things, but even after 20 years of deploying Rails apps I was still caught out by some of the ways things are different
Based on what happened when I built a new side project in Rails on SQLite, we'll cover what's different, what's new, and several ways that
Snippet from the RSS feed
This post was originally given as a talk for Friendly.rb. The slides are also available. Between Litestack and the Rails 8 trifecta of Solid Cable, Solid Cache, and Solid Queue, it’s easier than ever to spin up a Rails app that doesn’t need a database ser

You might also wanna read