Re: django 1.4, wsgi, flex deploy best practices

lashContent", > > "${width}", "${height}", > > swfVersionStr, xiSwfUrlStr, > > flashvars, params, attributes); > > > > > > *From:* django-users@googlegroups.com [mailto: > djang

RE: django 1.4, wsgi, flex deploy best practices

}", swfVersionStr, xiSwfUrlStr, flashvars, params, attributes); From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Joni Bekenstein Sent: Friday, June 01, 2012 9:40 AM To: django-users@googlegroups.com Subject: Re: django

Re: django 1.4, wsgi, flex deploy best practices

You can configure a basePath through flashvars as you said, but you don't have to make django serve the index.html to set that dynamically. You can put it by hand, allowing you to deploy on different servers in a decoupled manner. Maybe I'm missing something here but I don't see anything wrong

django 1.4, wsgi, flex deploy best practices

I use Flex for the client side and XML between client and server. I am a "one man team" and so elegance sometimes gets sacrifices for "it works". My typical deploy has been /var/www/html/my flex swf and html code And /home/projectname/current/djangositename This works well, except that I