gt; >
> > I am going through this tutorial on Tango with Django
> > - http://www.tangowithdjango.com/book/chapters/templates_static.html
> >
> > I extracted the specific part of the tutorial as seen in *BOLD*.
> >
> >
> > *4.4. The Static Med
> *4.4. The Static Media
>
> Server<http://www.tangowithdjango.com/book/chapters/templates_static.html#the-static-media-server>*
>
> *Now that you can dispatch static files, let’s look at uploading media.
> Many websites provide their users with the ability to do
Hi Max,
By default, the runserver command in a new django project will serve static
media, which I think is what the tutorial is referencing.
It's useful for developing your website, but be sure to read the tutorial's
warning:
> While using the Django development server to serve your static me
Using a static media server or not is more a choice. I don't think it is an
outdated concept, rather the opposite, depending on how you want to deploy
it. We are using Amazon CloudFront for our media and static files. That way
we don't get the load on our nginx servers (we genera
Hi DR,
Thanks for your reply.
I wanted to clarify -
1. The purpose of Static Media Server and
2. If it is an outdated concept
On Monday, October 13, 2014 4:57:32 PM UTC+8, Daniel Roseman wrote:
>
> On Monday, 13 October 2014 08:39:26 UTC+1, Max Nathaniel Ho wrote:
>>
>>
*.
> *4.4. The Static Media Server
> <http://www.tangowithdjango.com/book/chapters/templates_static.html#the-static-media-server>*
>
> *Now that you can dispatch static files, let’s look at uploading media.
> Many websites provide their users with the ability to do this - for
Hi all,
I am going through this tutorial on Tango with Django
- http://www.tangowithdjango.com/book/chapters/templates_static.html
I extracted the specific part of the tutorial as seen in *BOLD*.
*4.4. The Static Media Server
<http://www.tangowithdjango.com/book/chapters/templates_static.h
ion.
I want to make it possible to have the dynamic media files on a
separated server, first because the boost on the site (2 connections
opening the same time) and to cost cutting (a media server are cheaper
as I can use a vps with nginx or even the rackspace cloud files). Do
you have any advice?
I
On Apr 3, 1:10 pm, Enpaksh wrote:
> Yes tht is a posibility too and i have tried tht approach but the
> issue is tht there are lot of html files in my app and i am trying to
> avoid writing any explicit url because thn i have to keep track of all
> the pages tht reference
Yes tht is a posibility too and i have tried tht approach but the
issue is tht there are lot of html files in my app and i am trying to
avoid writing any explicit url because thn i have to keep track of all
the pages tht reference to the media server in tht fasion.
Can't i define my s
pproach! If you do this you are
negating the whole point of having a separate media server. You are
ensuring that a request for a media asset has to go through the whole
Django stack, for absolutely no purpose.
An HTML page is quite happy to reference media on a different domain -
you just have to
Absolutely not. You're thinking of everything from a "how does it
relate to my python program" standpoint. Using a media server has
nothing to do with django from a programming stand point. Python is a
great language but urlopen.read() is certainly not sufficient for
handling your
any requests coming to http://mysite.com/media to your media
server and let that handle it?
There's no reason for media traffic to load into Django and make
Django download the file and re-serve it. It's inefficient and silly.
(Unless of course, you are using Django to modify th
someone please
explicitly specify what needs to go in MEDIA_URL and MEDIA_ROOT and
how does urls.py routes to a cross domain media server. I am not
interested in any local directory structure to accomplish this task
because that is insecure and inefficient. Any help would be
appreciated.
It doesn'
On Apr 2, 4:21 pm, Media Server setup wrote:
> Hello,
>
> I have recently setup a Media server on a different box which I would
> like to use to serve static files to my django application. I
> personally find django documentation to be vague on this particular
> topic and I was
On Apr 2, 11:30 am, Dexter wrote:
> Hi,
> > Can someone please
> > explicitly specify what needs to go in MEDIA_URL and MEDIA_ROOT and
> > how does urls.py routes to a cross domain media server. I am not
> > interested in any local directory structure to accomplish th
Hi,
I don't have any experience with lighthttpd, but I guess you shouldn't use
django for serving your static files.
You should redirect your domain.tld/media folder to your box using
lighthttpd or apache.
Grtz, Dexter
On Fri, Apr 2, 2010 at 5:21 PM, Media Server setup wrote:
>
Hello,
I have recently setup a Media server on a different box which I would
like to use to serve static files to my django application. I
personally find django documentation to be vague on this particular
topic and I was hoping if someone who has done this type of setup
before would be able to
that is an extremely complex problem for such small problem...
if you are worried about caching, just append a number to the file or
add a date to it.
On Jun 22, 6:48 pm, alex <[EMAIL PROTECTED]> wrote:
> I already have {{ MEDIA_URL }} set in html, css, and js templates and
> that's working grea
I already have {{ MEDIA_URL }} set in html, css, and js templates and
that's working great. I would like to start setting far future caching
headers on media files based on the git abbreviated commit hash for
each file. i can think of three options for implementing this and
would appreciate feedba
I've just moved my media to a separate server. I run an rsync over
ssh whenever a user uploads a new profile image. Seems to work ok so
far.
The pain points are:
1) Setting up ssh keys so this can run unattended.
2) Because of (1), I had to run apache as a new user that has the
right permissi
Maybe a SFTP mount or some sort of rsync will suffice?
On Oct 29, 4:18 pm, "Marty Alchin" <[EMAIL PROTECTED]> wrote:
> On 10/29/07, Jökull <[EMAIL PROTECTED]> wrote:
>
> > There is a lively discussion on an interesting upcoming feature of
> > Django called FileStorage. This will allow any sort of
On 10/29/07, Jökull <[EMAIL PROTECTED]> wrote:
> There is a lively discussion on an interesting upcoming feature of
> Django called FileStorage. This will allow any sort of file storage
> mechanism to plug into FileFields and process uploads. A good example
> would be Amazon's S3 where a FileStora
I am in the planning stage of creating a Django media player. It is
intended for a small group of users, but still anticipating a lot of
bandwidth usage both upload and download as this is an MP3 repository
with a web frontend.
There is a lively discussion on an interesting upcoming feature of
Dj
On 1/5/07, stoKes <[EMAIL PROTECTED]> wrote:
...
> > We're doing exactly the same thing. This isn't a provided dj context
> > processor due to the slippery slope of including all settings in
> > context. It's been raised many times. Adding media_url should
> > probably be a cookbook entry...
what about defining images in your stylesheets?
The way we solve that is that if you reference your CSS with src="{{
media_url }}/css/style.css" and have urls in that CSS, define your urls
with relative addressing and they'll also come from the media server.
For us, we h
On Dec 13 2006, 7:46 pm, "Joseph Heck" <[EMAIL PROTECTED]> wrote:
Good point - done.
http://code.djangoproject.com/wiki/CookBookUsingExternalMedia
-joehttp://www.rhonabwy.com/wp/
On 12/13/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> On 12/13/06, Joseph Heck <[EMAIL PROTECTED]> wrote:
>
Good point - done.
http://code.djangoproject.com/wiki/CookBookUsingExternalMedia
-joe
http://www.rhonabwy.com/wp/
On 12/13/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
>
> On 12/13/06, Joseph Heck <[EMAIL PROTECTED]> wrote:
> > We're using
> >
> > blah blah blah
> ...
> > And then in the setti
Thanks all - that makes a lot more sense now. It was definately a case
of me looking for too simple a solution in the first place.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to t
On 12/13/06, Joseph Heck <[EMAIL PROTECTED]> wrote:
> We're using
>
> blah blah blah
...
> And then in the settings.py under TEMPLATE_CONTEXT_PROCESSORS, we added:
>"myproject.context_processors.common",
>
> There may well be a much better way to accomplish this all, but that worked
> out nic
What you want to use in your template is a reference to the media URL prior
to the static images. We're using
blah blah blah
blah.. It generally requires a bunch of search & replace for the first time
you implement it, and then just remembering to reference the {{media_url}}
thereafter as you bui
On 12/13/06, Tipan <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 13, 1:58 pm, "Waylan Limberg" <[EMAIL PROTECTED]> wrote:
> > On 12/13/06, Tipan <[EMAIL PROTECTED]> wrote:
> >
> > http://192.168.1.9:3000/gobites.jpg";>
> >
> > Generally speaking I believe the conventional way to do this when both
> >
On Dec 13, 1:58 pm, "Waylan Limberg" <[EMAIL PROTECTED]> wrote:
> On 12/13/06, Tipan <[EMAIL PROTECTED]> wrote:
>
> http://192.168.1.9:3000/gobites.jpg";>
>
> Generally speaking I believe the conventional way to do this when both
> servers are on one machine is to point all traffic to the static
On 12/13/06, Tipan <[EMAIL PROTECTED]> wrote:
>
> However, I can't seem to get an simple image to display through a
> Django template.
>
> I've tried all sorts of combinations and can't seem to make any
> headway.
>
> Any advice welcome. Details of my settings etc. below.
>
> Template call is simp
I need some advice on configuring a separate media server for our jpeg
images.
We are running Django on Apache 2.2 with mod_python 3.2.10 (python2.5)
on a Windows 2003 server.
As recommended in the docs, I am setting up a separate web server to
serve the media. I've installed Lighttpd 1
Thanks for the replies!
Because another IP addr isn't available, I decided to run Lighty on
port 81. I don't need SSL, so that seemed like the best solution, and
it's working well for me.
-Brandon
--~--~-~--~~~---~--~~
You received this message because you are
36 matches
Mail list logo
