One of my common frustrations when setting up a Rails app is that I’ll do “rails new”, set up the application, and then get a little way in before remembering that I either wanted to disable turbolinks, or choose a different database, or whatever the option may be. Obviously you can append the optio…

Great summary, Betsy. I’d like to throw my support behind both an interactive option and a minimal option, as well as better tooling and documentation for adding things you’ve said no to after the fact. While some might think “the list of things installed by default is insane”, it represents my hone…

My read on 5 is that it’s a mistake to lump them into the same question. If you ask how many people wish spring would just go away, you will cut through the lack of consensus: people passionately dislike spring. Bootsnap seems generally neutral for most devs.

Honestly, I like Spring! Trying to get my teammates to practice TDD pre-Spring and the same post-Spring was like night and day. It’s amazing how many hardcore technical arguments people made to avoid saying “20-second boot times annoy me too much for TDD to work for me,” and just as amazing how thos…

Excellent reply. I really appreciate your perspective.

I think a solution will probably arise from unifying and/or expanding the Template “API” and the AppBuilder , probably expanding Templates with some of the features from AppBuilder. A better template API would allow more “stacks” to be expressed and shared as templates, so you could rails new blog -…

Having a rails new --interactive option is a great idea! :+1: I am also tired of maintaining an ever-growing list of features to exclude :smiley: For the work I’ve been doing an interactive mode would be more valuable than templates, as every app has different requirements and every team different…

rails new --interactive is really great idea! It would be really awesome if we have ability to re-add the skipped frameworks. In one of my recent projects, I created the new rails app with rails new my_app --api but later we had to revert the api flag as we also needed rails views in the app.

I have started a draft PR to add support for the new rails command: rails new --minimal What exactly are we going to skip? everything… everything? cc/ @Betsy_Haibel @dhh can someone help make the final call on what exactly is excluded? Here is the PR: https://github.com/rails/rails/pull/39282

@DHH because there are so many ideas going on in this thread, do you think it would be worth making a Basecamp project or similar to coordinate this work? I think the work-to-be coordinated is fast exceeding what a Discourse thread can support.

[image] DHH: as well as better tooling and documentation for adding things you’ve said no to after the fact I’ve got an idea for adding back gems that were opted-out of: [image] Add `rails install` which installs the gem and runs install generator A May Of WTFs Eve…

Interactive "rails new"

A May Of WTFs

DHH (DHH) May 10, 2020, 11:49pm 52

That sounds like a great idea! If we’re letting you run stuff straight from a URL, we should probably preview what you’re about to run. But do like the idea of expanding the API and making the system itself use it!

Topic		Replies	Views
Interactive `rails new` rubyonrails-core	9	460	June 26, 2019
Create new app and add gems interactively rubyonrails-talk	2	520	September 24, 2021
Rails interactive rubyonrails-core	5	229	September 2, 2011
Running rails new as a "newbie" A May Of WTFs	3	1152	May 9, 2020
I have to disable more than I use with rails new A May Of WTFs	0	948	May 8, 2020

Interactive "rails new"

Related topics

More Resources