We'll have to dig into it more to figure out what changed, or if not, how to support all of the rails versions with ignoring app/manifests.
On Nov 5, 2012, at 6:06 PM, Josh <josh.m.sha...@gmail.com> wrote:
> Negative. Tried with 3.2.9.rc2.
> On Thursday, November 1, 2012 12:50:59 PM UTC-4, Josh Nichols wrote:
> Can you try this in your config/application.rb (after removing that bit in environment.rb)?
> # don't attempt to auto-require the moonshine manifests into the rails env
> I grabbed this from the generator (https://github.com/railsmachine/moonshine/blob/master/lib/generators/...), which means that new applications would get this by default. Was this a fresh 3.2.9rc1 app, or was it an existing app upgraded?
> I'd rather not have to manifests out of app/manifests if we can avoid it.
> - Josh
> On Oct 31, 2012, at 7:12 PM, Josh <josh.m...@gmail.com> wrote:
>> My app is 3.2.8 and I have this in my environment.rb:
>> Rails.configuration.paths['app/manifests'] = 'app/manifests'
>> ...I'm not really sure what it does, I *thought* it did something like exclude app/manifests from the autoload path - but reading what it says, that doesn't seem to make sense. Regardless of what I think it's supposed to do, that line allows my app to run, and my tests to run. Without it, I get errors about shadow_puppet not being installed in dev and in test even though it is installed.
>> That all said, 3.2.9.rc1 breaks my app in a similar way (No such file to load -- shadow_puppet)
>> Can we relocate application_manifest somehow?
>> Looks like it's relatively hardcoded right now:
>> <3 yous guys,
>> P.S., I wrote all of that, and then changed "app/manifests" to "lib/manifests" in capistrano_integration.rb and moved the folder/file and all things are merry again.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.