He is a dynamic #Rails & #Ruby core team member and Sr Staff Engineer at @Shopify! When not innovating in tech, he loves whipping up culinary delights, cuddling with feline friends, and crafting quirky software.
Long shot: Any #Rails devs know of a method to add a lang attribute on any text that's missing a translation, so has had to fall back to the default locale? I suspect I might need to write my own i18n backend, but I'd love to find something already out there.
If I do end up writing my own version of the I18n::Fallback backend, I'll try to get it merged upstream into Rails core; accessibility by default is best accessibility.
How do I tell Heroku to not install install the #nodejs buildpack at all?
(and remediate this WARNING on every deploy)
WARNING:
Installing a default version (20.9.0) of Node.js.
This version is not pinned and can change over time, causing unexpected failures.
Heroku recommends placing the heroku/nodejs buildpack in front of heroku/ruby to install a specific version of node
Ready to save time with Rails Generators? Soft-launching Frictionless Generators for you great folks today. (The "proper" launch shouldn't be too far off.)
Still a few resources to finish up for the premium version, but the content is complete, and the main cheat sheets and quick reference sheets are included.
Already bought it? Make sure to download the latest updates! And if you have any kind words for testimonials, please pass them along.
I'm hopefully not the only geriatric millennial Rails dev still subscribed to that list. Perhaps you could send out a final message to say that the forum is the new official source?
@NeadReport There should be trains, no idea, the idea might be neat. But when we have railway infrastructure in use, it needs to be upkept. This has a feeling like a gadgetbahn. So many branch lines are not in use in Europe. Some lines were converted into cycle tracks. So are abandonned for the past 30 years and would need a refurbishment. Why not the real deal?
@canleaf
A very similar situation with unused rail lines here in the states.
I think it really boils down to volume of users for either mode.
There are no lines when you order an Uber ride. It comes to you. A rail cab ride into the next small town to shop or dine? I'm obviously a romantic when it comes to this idea :)
I observe devs in my company bringing back the "schema.rb" file from production into the Git repository.
I am uncertain about this practice. Modifying directly the schema.rb file has consistently been problematic for me. Perhaps it's less of an issue if you solely use schema:load, but I remain skeptical.
I would prefer a re-entering migration to rectify the schema, such as using 'create index if not exists.' This way, changes are propagated across all databases in various environments.
@byroot@benoit I live in slight fear that our schema.rb does not actually match our production schema, even though theoretically it should. So this sort of back porting it from production is attractive at least as a sanity/anxiety check
If you are launching a #Rails app, I really can’t recommend Hatchbox enough. It’s like having the ease of Heroku at the price of AWS/Digital Ocean, because that’s what it is.
I also love that we aren’t locked into anything since if Hatchbox vanished tomorrow, we’d just be left with properly configured servers on AWS that we could run ourselves the old fashioned way.
@harpaa01 haha. I mean, that’s their business. Mine would be totally fine. But yeah, I don’t see much risk of that. We set up a load balancer and an app server and deployed in like 10 minutes with Hatchbox. I’m pretty sure that would’ve taken me two days and I probably would’ve fucked part of it up.