That is correct. The point of the separate subdomain is to help deployments
for the web. It's nicer and simpler sometimes to separate a domain or even
an entire server dedicated for media or S3.
On an intranet, you have a bit more flexibility. :)
--
You received this message because you are su
I found it !!
I figured that for intranet use I don't need two server{} statment in
conf, I just delete the one with media and re-write location to
second. And now it's workin super.
Thanks to everyone for help.
On 18 Mar, 10:18, maciekjbl wrote:
> On 17 Mar, 22:54, Matt Robenolt wrote:
>
> >
On 17 Mar, 22:54, Matt Robenolt wrote:
> You set up a 'media.aplikacje' alias in your nginx config, but your
> media is still attempting to be pulled from 'aplikacje/media/', so at
> this point, your MEDIA_URL is wrong. MEDIA_URL needs to be 'http://
> media.aplikacje/'
I change it couple times
You set up a 'media.aplikacje' alias in your nginx config, but your
media is still attempting to be pulled from 'aplikacje/media/', so at
this point, your MEDIA_URL is wrong. MEDIA_URL needs to be 'http://
media.aplikacje/'
Or, you can change the server{} config for nginx to have the alias /
media
On Thu, Mar 17, 2011 at 3:04 PM, maciekjbl wrote:
> Ok ... so my main problem is that it's my first Django, Apache, Nginx
> instalation ever.
I'd say keep it simple. specially on an intranet-only setup where
you're unlikely to need the absolute maximum performance.
the two-server advice is usef
Ok ... so my main problem is that it's my first Django, Apache, Nginx
instalation ever.
I just don't know where to look when it's about debugging, and not
where in terms of places but order of search.
What I know is mod_wsgi works because I have data in place.
I know that proxy works because of a
On Thu, Mar 17, 2011 at 7:53 AM, maciekjbl wrote:
> My problem is in the intranet this site
> won't see the world :)
why is this a problem? you can use the same setup.
the main difference (at least for my own intranet-only apps) is that
usually you don't get as many users, nor exposive growth.
Nate it looks really interesting but I see the same problem that I
already have.
Most of help about setting up Django is base on assumption that it
will be site in the internet. My problem is in the intranet this site
won't see the world :) . I know it should be less work to do and less
problems b
You might want to try Nginx proxying to Gunicorn. This is what we use for
DjangoZoom and it works really well. Pretty easy to set up as well. Here are
a few resources that provide instructions for how to set it up:
http://www.rkblog.rk.edu.pl/w/p/deploying-django-project-gunicorn-and-nginx/
http:
I'm still fighting with this configutarion.
What I manage is that I don't have any error's in apache, but media
still don't work.
I try to use example from lincolnloop and it's fail for me completly.
Any help ?
On 11 Mar, 20:23, maciekjbl wrote:
> Reload, restart and still nothing.
>
> I have
Reload, restart and still nothing.
I have my admin-media syn-linked to my media folder, is it wrong ?
Because I see alias to this folder.
>From apache error log I know only that every request get [error
500].
On 11 Mar, 13:42, krzysiekpl wrote:
> In my opinion you should add alias in nginx.conf
In my opinion you should add alias in nginx.conf for admin media
files. Put this code in server{}
# admin uses admin-media/
# alias works different than root above by dropping admin-
media
location ^~ /media/admin/ {
alias /usr/local/lib/python2.6/dist-packages/django/
Hi,
I know this topic was discussed a lot, but in every post for this
topic there are diffrent configuration and this stop helping for me.
Long story short : I changed DEBUG = True to False and all static
media are gone, so this is something wrong in web server conf.
#settings.py#
impor
13 matches
Mail list logo
