You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
I'm new to using fastly and this is probably a super edge case, but I had an issue over the past few days that broke an app of mine. It's a rails 4.1 app that is multi-tenant using postgresql scemas.
I had a machine failure, so I needed to build my dev environment from scratch again and while restoring my dev environment I ran into several issues using this version 0.1.3 of the gem. When I first did bundle on the new machine, I was prompted that fastly 1.02 doesn't exist in any of the sources. So I ran bundle update --sources fastly-rails which then updated my gemfile to the latest fastly. This then manifested itself in two different ways:
On my dev environment OSX 10.9.3 (on both my mac pro and macbook pro) any namespaced controller (including devise) throws a 'Uninitialized Constant error'. All other controllers seem to route just fine. Here's an example of the error
For now, I've commented out the fastly gem and my app is working again. I'd love to use it again, so if there's any other information you need from me to help track down the cause of this please let me know.
The text was updated successfully, but these errors were encountered:
I'm new to using fastly and this is probably a super edge case, but I had an issue over the past few days that broke an app of mine. It's a rails 4.1 app that is multi-tenant using postgresql scemas.
I had a machine failure, so I needed to build my dev environment from scratch again and while restoring my dev environment I ran into several issues using this version 0.1.3 of the gem. When I first did bundle on the new machine, I was prompted that fastly 1.02 doesn't exist in any of the sources. So I ran
bundle update --sources fastly-rails
which then updated my gemfile to the latest fastly. This then manifested itself in two different ways:For now, I've commented out the fastly gem and my app is working again. I'd love to use it again, so if there's any other information you need from me to help track down the cause of this please let me know.
The text was updated successfully, but these errors were encountered: