-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Invalid route name, already in use: 'rails_service_blob' #1046
Comments
Thanks for submitting your first issue to Houdini! |
I should mention that removing those lines causes problems when running in development with just |
Noticed that removing these lines breaks |
If you have a chance, add The reason we need to repeat those lines in here is that, bizarrely, Rails ActiveStorage is totally not secured by default. |
Thanks! I added a line like this in
|
I'll have to dig into this further. Unfortunately, I won't have time this week. |
I have a tentative fix for this but it needs to be tested further. In config/initializers/devise.rb, add the following line:
There seems to be a weird interaction between devise and activestorage that isn't well documented. I will have to report the bug to Devise when I have the chance. |
It's alive! Thanks so much @wwahammy. I realise this is a temporary fix, but great to be able to get past this for now. |
@BenSturmfels was this ever addressed? |
@wwahammy it looks like this wasn't addressed holistically. I just updated our trial production instance, disabled the
|
(and ran |
As @iRunner mentioned in #524, the
bin/rails server --environment=production
fails for me with an errorInvalid route name, already in use: 'rails_service_blob'
. This running the recentmain
branch on a Debian Bullseye VM with Ruby 2.7.4 and Bundler 2.2.5.Removing
config/routes.rb
lines 292-305 appears to fix the issue, allowing the server to start up. These lines appear to be nearly identical togems/activestorage-6.1.5/config/routes.rb
lines 3-17 except for a minor difference in the last line.I'm also seeing the same on my local Guix operating system, so it doesn't appear to be specific to the above VM.
The text was updated successfully, but these errors were encountered: