Yeah, that makes good sense - I tried finding out info on djangoproject but didn't quite understand what they were for.
Thanks On Jan 17, 7:04 pm, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > On Fri, 2009-01-16 at 21:06 -0800, DragonSlayre wrote: > > I'm using django-thumbs (http://code.google.com/p/django-thumbs/) to > > create some thumbnails for my site: > > > class Image(models.Model): > > title = models.CharField(max_length=50, blank=True, null=True) > > caption = models.CharField(max_length=100, blank=True, null=True) > > photo = ImageWithThumbsField( > > upload_to="site_images", > > sizes=((270,150),)) > > > And in my settings my media path is as following: > > > MEDIA_ROOT = os.path.abspath(os.path.join(PROJECT_DIR, 'site_media')) > > MEDIA_URL = 'static/' > > > I'm trying to upload my images into the 'site_media/static/ > > site_images/' location > > > When I upload however, it puts the image into 'site_media/ > > site_images/' > > The strange thing though, is that the location that gets stored in the > > database is 'static/site_images/imageName.jpg' > > > I'm really not sure what's going on, and feel completely confused. > > The MEDIA_ROOT is the path on the storage system (the hard-drive, > typically) where the data is saved. > > The MEDIA_URL is the URL used by the web browser to access the media. It > is entirely unrelated to the location on the hard-drive. Even though > URLs and directory paths both use '/' as a separator, they don't refer > to the same namespace of objects. The web browser requesting the media > is using a URL and has absolutely no idea where you might have chosen to > store the data on the disk. > > However (and this is an important point), to make things a little > simpler on the code developer, when you're using the straightforward > file-saving operations, as you are doing, Django makes the filesystem > layout underneath MEDIA_ROOT match the URL space layout referred to by > URL_ROOT. > > I'm not familiar with the django-thumbs project, so I have no idea why > it's putting the MEDIA_URL portion on the front of the filename it > saves. What I will mention, though, is that Django's normal ImageField > model field only stores "site_images/imageName.jpg" in the case you > describe. So a template might put MEDIA_URL on the front of that to get > the URL and something wanting to access the file directory (a cronjob or > something similar) would prepend MEDIA_ROOT to the name in the database. > > Does that clear things up a bit? MEDIA_URL is the URL used by external > things like web browsers to access the object. MEDIA_ROOT talks about > where the image is stored on disk. They are unrelated concepts (in the > sense that URLs are not file paths), although you would normally have to > configure your webserver so that requests for MEDIA_URL were served by > files under MEDIA_ROOT. > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
