I agree Flag to not leave so many comments in the default Gemfile wasn’t a very constructive thread, but I think there is some merit in reviewing these comments. You can see the current base Gemfile in that thread. Here’s what I’m proposing:
- For each gem there is a link or a solid explanation of what the gem does.
- Gems that you can change are called out. Gems that you shouldn’t change are not.
- It’s better to have multi-line comments or extra spacing than it is to have confusing comments.
- I don’t know much about
jbuilder. I’ve never used it. Does every single Rails user need it on by default?
- Removed note about bundling edge rails as it’s only useful for power users.
- Explained how to change your DB + added a link to Configuring Rails Applications — Ruby on Rails Guides (which could probably be better but that’s another story)
- If you google
has_secure_passwordyou don’t get any great results. I imagine this confuses lots of people when it’s mentioned in the Gemfile. I’ve removed it and made the comment around
bcryptmore generic for this reason.
- I removed
image_processingentirely. Active Storage Overview — Ruby on Rails Guides introduces it, but I don’t see why every single user needs to be told about it.
bootsnapto the bottom. It’s not something new users should think about.