<story><title>Django Community Survey</title><url>https://www.djangoproject.com/weblog/2015/may/07/community-survey/</url><text></text></story><parent_chain><item><author>iyn</author><text>Can you elaborate on the solutions in frontend?&lt;p&gt;Currently I&amp;#x27;m working on a project and I want to use React &amp;quot;the right way&amp;quot;. While it&amp;#x27;s not so hard to just integrate React into Django project, it&amp;#x27;s not so easy to manage the chaos when things start to grow. At the moment I&amp;#x27;m trying to integrate React, webpack, gulp and node (server side rendering for react) into Django workflow and make it work &amp;quot;natural&amp;quot;, but right now it just feels hacky and not the way I want it to work.&lt;p&gt;Would be great if you could share your workflows &amp;amp; ideas.</text></item><item><author>simonpantzare</author><text>As a long time Django user (first project on 1.1) I want to thank for a great framework and your wonderful release approach!&lt;p&gt;I often try out new new web dev platforms and frameworks but tend to rewrite projects that get too serious or large in Django, or when I&amp;#x27;m starting to miss too many features.&lt;p&gt;If I know that I am building something that others are going to work on, or if I know that the project will need to be maintained for a considerable amount of time, I tend to go with Django and a few familiar libraries (Celery, Django REST framework, django-extensions) right off the bat, as I feel comfortable that we won&amp;#x27;t run into issues where some important dependency becomes unmaintained or introduces backwards-incompatible changes. Much thanks to Django&amp;#x27;s predictable and well thought out releases.&lt;p&gt;Further, when I pick Django, I know that there is good support in monitoring and crash report systems such as Sentry, New Relic, and others. So that&amp;#x27;s one less thing to worry about.&lt;p&gt;The only area where I have started to use other solutions is frontend dev, as I find that the momentum in the Node community is so much higher in this area. I only wish that the Node community wasn&amp;#x27;t as fragmented and had a more long-term view on releases.</text></item></parent_chain><comment><author>simonpantzare</author><text>I put nginx in front and a location &amp;#x2F;static&amp;#x2F; block with a try_files directive that first tries to serve static files from Django (those collected with python manage.py collectstatic) and falls back to serve files that a gulp task generated.&lt;p&gt;To serve different assets in dev and prod I let gulp generate a manifest and have a custom template tag in Django that expands to different paths depending on settings.DEBUG:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  {% my_static &amp;#x27;css&amp;#x2F;all.css&amp;#x27; %}
&lt;/code&gt;&lt;/pre&gt;
expands to either &amp;#x2F;static&amp;#x2F;css&amp;#x2F;all.css or something like &amp;#x2F;static&amp;#x2F;css&amp;#x2F;all.min.abcd1234.css.&lt;p&gt;If nginx is serving a minified, hashed path it adds a Cache-Control: max-age=31556926 header to the response.</text></comment>
<story><title>Django Community Survey</title><url>https://www.djangoproject.com/weblog/2015/may/07/community-survey/</url><text></text></story><parent_chain><item><author>iyn</author><text>Can you elaborate on the solutions in frontend?&lt;p&gt;Currently I&amp;#x27;m working on a project and I want to use React &amp;quot;the right way&amp;quot;. While it&amp;#x27;s not so hard to just integrate React into Django project, it&amp;#x27;s not so easy to manage the chaos when things start to grow. At the moment I&amp;#x27;m trying to integrate React, webpack, gulp and node (server side rendering for react) into Django workflow and make it work &amp;quot;natural&amp;quot;, but right now it just feels hacky and not the way I want it to work.&lt;p&gt;Would be great if you could share your workflows &amp;amp; ideas.</text></item><item><author>simonpantzare</author><text>As a long time Django user (first project on 1.1) I want to thank for a great framework and your wonderful release approach!&lt;p&gt;I often try out new new web dev platforms and frameworks but tend to rewrite projects that get too serious or large in Django, or when I&amp;#x27;m starting to miss too many features.&lt;p&gt;If I know that I am building something that others are going to work on, or if I know that the project will need to be maintained for a considerable amount of time, I tend to go with Django and a few familiar libraries (Celery, Django REST framework, django-extensions) right off the bat, as I feel comfortable that we won&amp;#x27;t run into issues where some important dependency becomes unmaintained or introduces backwards-incompatible changes. Much thanks to Django&amp;#x27;s predictable and well thought out releases.&lt;p&gt;Further, when I pick Django, I know that there is good support in monitoring and crash report systems such as Sentry, New Relic, and others. So that&amp;#x27;s one less thing to worry about.&lt;p&gt;The only area where I have started to use other solutions is frontend dev, as I find that the momentum in the Node community is so much higher in this area. I only wish that the Node community wasn&amp;#x27;t as fragmented and had a more long-term view on releases.</text></item></parent_chain><comment><author>anewhnaccount</author><text>I&amp;#x27;ve not done it myself (I&amp;#x27;ve looked  but it was a small project so I just ignored server side rendering and used django-compressor for convienience&amp;#x27;s sake) but you should definitely check &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markfinger&amp;#x2F;python-react&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;markfinger&amp;#x2F;python-react&lt;/a&gt; if you haven&amp;#x27;t already</text></comment>