mastodon.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
Generic Mastodon server for anyone to use.

Server stats:

8.3K
active users

#rails

16 posts15 participants0 posts today

I just upgraded a #Rails app from 7.0 to 8.0 only to realise after agonising for two days that in version 7.1, "eager loading" ActiveStorage records was "fixed" so now it takes 1200 ms to load a page in production instead of 120 ms.

Every year or two (especially with a major version bump), I re-read #Rails intro docs, guides, and onboarding materials

I re-watch intro videos and screencasts

To see what's new, yes
But also to see what ossified ways I have that have been obviated or improved

Too see with fresh eyes

I’m upgrading a #Rails app from 7.1 to 8.02. The App uses tailwindcss-rails even though I don’t use any #TailwindCss in the app. I had problems taking Tailwind to 4.x so I pinned it to ~> 3.3.1 per the README. I’d love to get over the hump and get it all the way to 4.x. but there was an @forms plugin that seemed to be missing.

Anyone know of specific steps to upgrade a Rails App? (The instructions seem more geared to a generic App and I can’t seem to make the translation). Boosts appreciated.

🌗 建立模組化 Rails 應用程式:透過 Active Storage Dashboard 深入剖析 Rails Engine
➤ 使用 Rails Engine 打造高效能、易於使用的檔案管理工具
panasiti.me/blog/modular-rails
作者分享了十年來使用 Rails 開發應用程式的經驗,並探討了使用者對於檔案儲存空間使用情況、未連結檔案以及檔案類型等常見問題。為瞭解決這些問題,作者開發了 Active Storage Dashboard,一個可掛載的 Rails Engine,提供現代化的使用者介面來監控和管理 Active Storage 資料。文章深入探討了 Rails Engine 的概念、架構以及 Active Storage Dashboard 的實作細節,包括路由、URL 生成、配置彈性以及驗證策略,並鼓勵開發者更頻繁地使用 Engine
#Rails #Active Storage #Engine #開發

www.panasiti.meBuilding Modular Rails Applications: A Deep Dive into Rails Engines Through Active Storage Dashboard | Giovanni Panasiti - Personal Website and BlogI’ve been building Rails applications for the last 10 years on a daily base and almost all of them use active storage now. Users are uploading files and then...
Replied in thread

@oinak I supposed that plus making sure the inheritors were in domain specific modules would probably be enough to avoid naming conflicts.

And if it really is that simple, I'm surprised it's not covered in a higher percentage of the #Rails #DDD content out there.