Sent from my iPhone

> On 24 Nov 2014, at 16:43, richard schneeman <richard.schnee...@gmail.com> 
> wrote:
> 
> > pushed to a CDN which the apps use for an asset host
> 
> I recommend not doing this. You can set up your CDN to "pull" instead which 
> is much more sane and less error prone: 
> https://devcenter.heroku.com/articles/using-amazon-cloudfront-cdn. Source: 
> hundreds of Heroku support tickets. 
> 
> >  assets precompilation is really boring, slow and even complicated
> 
> Agreed, however your solution only moves the slow, complicated, boringness to 
> the realm of your users; it doesn't get rid of them. Now instead of you 
> having to wait for your assets to precompile before an app is deployed, your 
> users have to wait for assets to be compiled the first time they hit a page. 
> If you think 30 seconds is a long time to wait for compilation on push, how 
> do you think a user will feel about a 30 second long request to your 
> homepage? 

It's interesting that you mention that. In development mode (with debug assets 
off) the consolidated assets build and serve in milliseconds. I'm still unsure 
as to why the asset pre-compile takes so long.

> 
>> On Mon, Nov 24, 2014 at 7:27 AM, Ken Collins <k...@actionmoniker.com> wrote:
>> And another reason for pre-compilation is that it can happen on district 
>> asset host boxes or even be pushed to a CDN which the apps use for an asset 
>> host. 
>> 
>>  - Ken
>> 
>> 
>>> On November 24, 2014 at 10:09:54 AM, James Coleman (jtc...@gmail.com) wrote:
>>> 
>>> The reason for asset precompilation in production environments isn't just 
>>> caching and speed on the first request, it's also that you don't want to 
>>> have to have a JS environment (e.g. TheRubyRacer) in production.
>>> 
>>> 2014-11-23 18:32 GMT-05:00 Bráulio Bhavamitra <brau...@eita.org.br>:
>>>> Hello all,
>>>> 
>>>> For me, assets precompilation is really boring, slow and even complicated 
>>>> as additional configuration is necessary.
>>>> 
>>>> That is why I've made a live asset compilation so that on the first 
>>>> request the assets get compiled and put on the static asset path 
>>>> (public/assets), just like rake assets:precompile do, so that on the next 
>>>> request it is going to be served by Nginx.
>>>> 
>>>> Please comment on the idea. GEM source code at 
>>>> https://github.com/coletivoEITA/assets_live_compile
>>>> 
>>>> cheers,
>>>> 
>>>> bráulio
>>>> 
>>>> 
>>>> -- 
>>>> 
>>>> "Lute pela sua ideologia. Seja um com sua ideologia. Viva pela sua 
>>>> ideologia. Morra por sua ideologia" P.R. Sarkar
>>>> 
>>>> EITA - Educação, Informação e Tecnologias para Autogestão
>>>> http://cirandas.net/brauliobo
>>>> http://eita.org.br
>>>> 
>>>> "Paramapurusha é meu pai e Parama Prakriti é minha mãe. O universo é meu 
>>>> lar e todos nós somos cidadãos deste cosmo. Este universo é a imaginação 
>>>> da Mente Macrocósmica, e todas as entidades estão sendo criadas, 
>>>> preservadas e destruídas nas fases de extroversão e introversão do fluxo 
>>>> imaginativo cósmico. No âmbito pessoal, quando uma pessoa imagina algo em 
>>>> sua mente, naquele momento, essa pessoa é a única proprietária daquilo que 
>>>> ela imagina, e ninguém mais. Quando um ser humano criado mentalmente 
>>>> caminha por um milharal também imaginado, a pessoa imaginada não é a 
>>>> propriedade desse milharal, pois ele pertence ao indivíduo que o está 
>>>> imaginando. Este universo foi criado na imaginação de Brahma, a Entidade 
>>>> Suprema, por isso a propriedade deste universo é de Brahma, e não dos 
>>>> microcosmos que também foram criados pela imaginação de Brahma. Nenhuma 
>>>> propriedade deste mundo, mutável ou imutável, pertence a um indivíduo em 
>>>> particular; tudo é o patrimônio comum de todos."
>>>> Restante do texto em 
>>>> http://cirandas.net/brauliobo/blog/a-problematica-de-hoje-em-dia
>>>> --
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Ruby on Rails: Core" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to rubyonrails-core+unsubscr...@googlegroups.com.
>>>> To post to this group, send email to rubyonrails-core@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/rubyonrails-core.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Ruby on Rails: Core" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to rubyonrails-core+unsubscr...@googlegroups.com.
>>> To post to this group, send email to rubyonrails-core@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/rubyonrails-core.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Ruby on Rails: Core" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to rubyonrails-core+unsubscr...@googlegroups.com.
>> To post to this group, send email to rubyonrails-core@googlegroups.com.
>> Visit this group at http://groups.google.com/group/rubyonrails-core.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Reply via email to