Why Do I Get Uninitialized Constant Devise Name Error When Running Webrick Server

uninitialized constant Devise (NameError)

I fixed it... My script/rails and config/unicorn_init.sh wasn't executable so a simple chmod u+x on these files solved my problem. It wasn't a problem with devise !

Devise Error: NameError (uninitialized constant Unlock)

This was never properly resolved. I ended overriding the built-in devise callback functions (which is a horrible practice)

Old versions of Rails3 and Ruby 1.9.3 are most probably the culprits - but I don't have the privilege of upgrading - too much legacy code working in production already.

Story of my life :(

Rails - uninitialized constant error by Puma when trying to start the server (WIndows 11)

Solution:-

Apparently, there was a conflict with the version. As Abhinay mentioned in the comment, I switched to Ruby 2.7.5, and the app started working.



Related Topics



Leave a reply



Submit