Ok yes seems like a slam dunk.. hell how about an --install-media for
python setup.py install ;)
On Jun 3, 10:18 pm, Jannis Leidel wrote:
> Am 30.05.2010 um 05:54 schrieb BrettH:
>
> > +1 on Option 2.
>
> > I have written a basic deployment app (not quite ready for release
>
Am 30.05.2010 um 05:54 schrieb BrettH:
> +1 on Option 2.
>
> I have written a basic deployment app (not quite ready for release
> yet) that deploys a virtualenv for each version of your project,
> roughly equivalent to Google App Engine. I specifically need to split
> out the USER_MEDIA so that
Am 28.05.2010 um 01:27 schrieb burc...@gmail.com:
> Hi all,
>
>> - a media files path resolver -- following a similar directory structure as
>> the app templates loader (/media/ vs. /templates/)
>> - build_static -- a mangement command that'll collect media files from apps
>> from various
+1 on Option 2.
I have written a basic deployment app (not quite ready for release
yet) that deploys a virtualenv for each version of your project,
roughly equivalent to Google App Engine. I specifically need to split
out the USER_MEDIA so that it isn't versioned. Internally if the
developer does
On May 27, 2010, at 5:27 PM, burc...@gmail.com wrote:
> Hi all,
>
>> - a media files path resolver -- following a similar directory structure as
>> the app templates loader (/media/ vs. /templates/)
>> - build_static -- a mangement command that'll collect media files from apps
>> from various
Hi all,
> - a media files path resolver -- following a similar directory structure as
> the app templates loader (/media/ vs. /templates/)
> - build_static -- a mangement command that'll collect media files from apps
> from various locations using the media files path resolver and uses a file
Am 27.05.2010 um 17:23 schrieb Luke Plant:
> A Django 1.3 proposal. It is a pretty small feature/change in some
> ways, but needs some discussion.
>
> = Motivation =
>
> This is intended to make it easier to cope with the distinction
> between user provided media and developer provided
On May 27, 2010, at 9:23 AM, Luke Plant wrote:
> A Django 1.3 proposal. It is a pretty small feature/change in some
> ways, but needs some discussion.
>
> = Motivation =
>
[...]
I am on board with the motivation here. The reasons given are exactly why
we made a similar change to Pinax.
> =
A Django 1.3 proposal. It is a pretty small feature/change in some
ways, but needs some discussion.
= Motivation =
This is intended to make it easier to cope with the distinction
between user provided media and developer provided media. This is a
significant pain point when it comes to