@maxwell
I thought we were going to wait a little while longer on this to try
to fix any remaining bugs and do a pull request when it's ready.. but
this works for me, if nothing else it will give us more feedback from
people running in production environments and make it easier to track
down the remaining bugs. :)
On Mar 28, 5:08 pm, Justin Thomas <
jus...@justinthomas.name> wrote:
> Just to my 'dev' pod. Thanks!
> On Mar 28, 2012 4:43 PM, "Daniel Grippi" <
dan...@joindiaspora.com> wrote:
>
>
>
>
>
>
>
> > Yep, we did remove Jammit. You'll wanna call assets:precompile instead.
>
> > Again, you shouldn't deploy to any production box quite yet as we still
> > have some bugs to work out.
>
> > Sent from my iPad
>
> > On Mar 28, 2012, at 4:12 PM, Justin Thomas <
jus...@justinthomas.name>
> > wrote:
>
> > Did jammit get removed? My deploy script calls that gem, but it is now
> > generating an error that it is not included in the Gemfile.
>
> > I'm fine with that, incidentally. jammit has always been a pain to work
> > around.
> > On Mar 28, 2012 3:03 PM, "Maxwell Salzberg" <
maxw...@joindiaspora.com>
> > wrote:
>
> >> All,
>
> >> After much hemming and hawing, I decided to merge the WIP asset-pipeline
> >> branch (most leg work done by Stevenh512) into master. As a result some
> >> small bugs might still be present, and a handful of cukes are now failing
> >> for various reasons.
>
> >> This is something we have been wanting for a long time. Since there was
> >> no questions IF it was going to get merged, and I was spending too much
> >> time trying to get very different code bases to stay up to date, we decided
> >> to just merge away. Ultimately, it is going ruin less people's pull
> >> request and/or day, and save lots of people time in the long run.
>
> >> I am pretty certain the merge did not lose anything, but it would be very
> >> helpful to me if you helped us out by trying it out. Please excuse me if
> >> you do see something that might have went missing, it was not intentional
>
> >> It is *not* recommended to deploy this to your production boxes right
> >> away. It would be much appreciated if you could help test this branch on
> >> your local dev setup, or any staging environments you might have. *Please
> >> download the new code, and help us make all the tests pass.* I will