Viktor Schmidt

Check a frequent misstep involves misconfiguring CSRF protection when integrating Devise. Previously, `protect_from_forgery` was automatically prepended to the `before_action` chain, ensuring CSRF tokens were verified before any controller action. However,...

I am not sure, if I have the same issue, but in my case I am using GitHub actions, and bundle is not installing all gems I need. In my...

> @viktorianer I don't think this has the same cause. The symptom of this issue is that `bundle install` fails, but in your case it looks like that is successful...

Take a look at https://github.com/rails/rails/pull/50914. Actually, the guide needs an update here now.

Not sure if it helps, but Rails logs now to `STDOUT` by default, see https://github.com/rails/rails/pull/47138. Could we modify the following lines, to provide a different format and logger? ```ruby config.logger...

I've been [closely following the discussion](https://discuss.rubyonrails.org/t/add-devcontainer-flag-to-rails-new-command/84507/6?u=viktorianer) on adding a `devcontainer` flag to `rails new` command. The idea is promising, but there are complexities in the setup, as illustrated by examples...

> Could we also generate the `.vscode` folder with the recommended extensions file? Including ruby-lsp, and commands to start the Rails server. Although this would not be specifically for containers...

One more annoying thing, which I solved in my docker environment, is the installation of Ruby, Bundler and Node/Yarn version correct. Here is an output, where you can see the...

> I'm agnostic as to which approach is taken, my larger point is really that I think it's worth considering spinning up a database as well (or providing the option...

My point is, now you have to define Ruby in `Gemfile` (let's say `ruby "3.2.2"`) and in `.devcontainer` (let's say `ARG VARIANT=3-bullseye`). So, at least, you have here 2 places,...