This appears 2434 in 2 days. The same error but for 'assets' 110 times.
There are 3000 instances of a similar error. production.log is up to 50MB in 2 days from these errors. How do we fix them?
What's the url of a request causing this error?
Here's my theory: the requests look something like "/wagn/files/blah" or "/wagn/assets/blah". Those made sense in your previous installation (where Wagn was installed in the wagn/ directory) but not in the current one, where it's at the root.
Most likely these are broken requests coming from external sources, like crawlers or bookmarks or tweets or anything that stored a url to the site.
In other words: your problem isn't a noisy log file; your problem is that you're getting a ton of requests to the site that are currently getting server errors as a result!
If my theory is correct, I would recommend an apache rewrite rule that redirects /wagn/files/blah to /files/blah.
Hmm. We thought it was somehow doing that on its own, since it actually directs people to the page regardless. I had thought we needed to do a redirect, but then when we tried going to the old URLs, they still worked, so it seemed like it wasn't necessary. Will try that.
you may have been seeing cached versions of those pages. It's worth trying a hard-reload.
Where we should make the change? There are .htacess files in a few different places. Do we have to reinstall the gem? Does RewriteRule /wagn/files(.*) /files$1 sound about right.
You shouldn't have to reinstall the gem; basically Wagn shouldn't be involved in the process at all. This is about apache configuration; a rewrite rule would modify the request before it ever reaches Wagn. I don't know the apache syntax off hand.
it occurs to me, by the way, that you may have been thrown off by the fact that /wagn/ would still work. That's because there are legacy routes to support that as basically an alternate url for reading a card. But /wagn/files/... was never supported.
The problem was that there are two .htaccess files, and both of them live inside the wagn gem. Because we don't know how this whole gem-wrapped-in-passenger business really works, or anything about gems, we have no idea: a) which one, if either, I should be editing; b) how to get it recognized once I've edited it.