--
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "pylons-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pylons-discuss/o5SB8r3jpUk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pylons-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
To unsubscribe from this group and all its topics, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
--
Randall,
Please look for me at tonight's SF Python presentation meet up at Yelp. I'll also be at next Wednesday's hack night for Pyramid in PyCharm. I'd like to see what you're doing.
--steve
>>>> an email to pylons-discuss+unsubscribe@googlegroups.com.
>>>> To post to this group, send email to pylons-discuss@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/pylons-discuss.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "pylons-discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to pylons-discuss+unsubscribe@googlegroups.com.
>>> To post to this group, send email to pylons-discuss@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/pylons-discuss.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>--
>>You received this message because you are subscribed to the Google Groups
>>"pylons-discuss" group.
>>To unsubscribe from this group and stop receiving emails from it, send an
>>email to pylons-discuss+unsubscribe@googlegroups.com.
>>To post to this group, send email to pylons-discuss@googlegroups.com.
>>>> an email to pylons-discus...@googlegroups.com.
>>>> To post to this group, send email to pylons-...@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/pylons-discuss.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "pylons-discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to pylons-discus...@googlegroups.com.
>>> To post to this group, send email to pylons-...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/pylons-discuss.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>--
>>You received this message because you are subscribed to the Google Groups
>>"pylons-discuss" group.
>>To unsubscribe from this group and stop receiving emails from it, send an
>>email to pylons-discus...@googlegroups.com.
>>To post to this group, send email to pylons-...@googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "pylons-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pylons-discuss/o5SB8r3jpUk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
2014-10-28 15:51 GMT+01:00 Sascha Gottfried <sascha.g...@googlemail.com>:
> This is the announcement of the package from the author...
> http://blog.startifact.com/posts/announcing-bowerstatic.html
>
>
> On Tue, Oct 28, 2014 at 11:16 AM, Sascha Gottfried
> <sascha.g...@googlemail.com> wrote:
>>
>> Today I found bowerstatic, successor of fanstatic, and want to highlight
>> the history page of the docs. It is a great introduction into the topic and
>> gives answers to some questions found in this thread.
>>
>> Bowerstatic@readthedocs - History
I have made an integration of bowerstatic in Pyramid:
https://github.com/mrijken/pyramid_bowerstatic
It is not released yet, because it will need some testing first.
Marc
Op 11 nov. 2014 18:45 schreef "John Anderson" <son...@gmail.com>:
>>
> I still don't think just putting it behind a CDN as a cache quite solves the asset deployment issue. Using the same domain as your application is going to pass around all the cookies for that domain on every static asset request. You have to be able to customize the root URL of static assets when it generates the URL in production. This is why you see things like twimg.com and yimg.com, or just applications using akamai URLs directly. It doesn't make much sense to use up application server workers (like gunicorn) to serve a CSS file, especially if you aren't using gevent because then you are going to have a static set of threads + processes that you've configured, especially since you rarely expose it directly and are usually sitting behind a proxy like nginx anyways.
>
In my situation the CDN is behind a different domain name as the main site: cdn.example.com vs www.example.com. In bowerstatic you can define that the statics assets will have a different base than the regular pages. Therefor cdn.example.com has no cookies. For me this is a nice solution, but will not be others.
In my situation the CDN is behind a different domain name as the main site: cdn.example.com vs www.example.com. In bowerstatic you can define that the statics assets will have a different base than the regular pages. Therefor cdn.example.com has no cookies. For me this is a nice solution, but will not be others.
Yes with www. But of course it can also be a different domain.