I believe the term is “knock on wood” otherwise it’s rather inappropriate.
I have ‘spring’ only as a development dependency but I don’t even believe I’m using it. It was included by the default rails generation and I’m sure I’d be fine removing it as well. But I haven’t seen any problems. Gemfile.lock has spring at 1.6.1
I’m using Puma on both dev and prod and use “rails s” for running my local setup. No issues this way for me.
@AstonJ just readded spring again to 2 apps, because I wanted to try it again and see if the issues I had were resolved.
Its a great speedup for our specs, so we don’t have to boot rails every time we want to execute a spec.
And yes puma is the new default webserver for rails 5 because of actioncable