Introduce railsrc

[stevepolitodesign]

Introduces railsrc in an effort to prepare for the eventual removal of the
suspenders executable.

With this change, calling rails new will automatically set the following
options:

--database=postgresql

If you need to use another database, you can override this value like so: rails new my_app --database=mysql or rails new my_app --no_rc to skip this file all
together

[JoelQ]

Would this make it more challenging to generate a Rails app that deviates from this standard? Since now it wouldn't just be picking a different generator or setting a command-line flag but would require modifying a dotfile (or potentially adding a local .railsrc?)

[JoelQ]

Perhaps out of scope for this PR but I wonder if there are other flags we'd want to set here? I know when I've generated new Rails apps I've always set the test framework to RSpec but IIRC @seanpdoyle might be trying to change that convention.

[mike-burns]

Would this make it more challenging to generate a Rails app that deviates from this standard?

I'm pretty sure a command line flag overrides the dotfile.

[brian-penguin]

Personally, I don't like Tailwind and I wouldn't reach for it by default. I think especially since you need to also run a build process for Tailwind

[LkeMitchll]

I also wouldn't use tailwind by default. Tailwind can be useful later as a progressive enhancement:

https://andy-bell.co.uk/i-used-tailwind-for-the-u-in-cube-css-and-i-liked-it/

But at the very start of a project I would be looking to disable it or remove it somehow to decrease dependencies, and speed up the build process.

I'm not sure what this new tool is capable of scaffolding for us, but something I always do is create a folder structure under /app/assets/stylesheets

With something like:

base/
components/
utilities/
app.scss

...as children, plus a CSS reset. It doesn't have to be exactly this, but folders are much easier to remove or ignore than tailwind boilerplate.

[stevepolitodesign]

@JoelQ

Would this make it more challenging to generate a Rails app that deviates from this standard?

I'm pretty sure a command line flag overrides the dotfile.

Just confirming this is true. Running rails new my_app --database=mysql would override postgresql. However, there's no option to "unset" the CSS.

However, there's always the option to run rails new my_app --no-rc to skip the .railsrc all together.

[stevepolitodesign]

@LkeMitchll

I also wouldn't use tailwind by default. Tailwind can be useful later as a progressive enhancement:

https://andy-bell.co.uk/i-used-tailwind-for-the-u-in-cube-css-and-i-liked-it/

But at the very start of a project I would be looking to disable it or remove it somehow to decrease dependencies, and speed up the build process.

I'm not sure what this new tool is capable of scaffolding for us, but something I always do is create a folder structure under /app/assets/stylesheets

With something like:

base/
components/
utilities/
app.scss

...as children, plus a CSS reset. It doesn't have to be exactly this, but folders are much easier to remove or ignore than tailwind boilerplate.

This could be a responsibility of suspenders, and captured in a generator which would be called on existing applications. I'll make a note of it when I started building it out.