#django

if anyone can help me, I'd really appreciate it. I've made a simple little django app and am trying to learn how to deploy to heroku. I'm following a guide and I need to install some dependencies. All of them installed fine except psycopg2. "pip install psycopg2" gives me this output: http://pastebin.com/SnH1wWWa

I've scoured stackexchange and google looking for answers, but can't find what I have to do

if you only need psycopg2 on heroku, and not locally, don't install it locally

will I need to add psycopg2 to requirements.txt? or does heroku already know to use it

https://devcenter.heroku.com/articles/django this is the guide I'm following by the way

yes, you'll need to add it to your requirements

that's how heroku knows what to install

thank you

np

has anyone had the pleasure of setting up ssl with nginx?

I know it's a non django related question, but yeah.

There isn't much to it.. Point nginx at your cert and key, and turn ssl on.

You may want to specify certain protocols/ciphers.

if you're using a load balancer, terminate the SSL there instead of continuing it on to your nginx servers

__love__ don't think I'm using a load balancer.

{{ STATIC_URL }} should i not use this in templates any more over {% static %}

I keep getting a 400 error and this The plain HTTP request was sent to HTTPS port

fission6: i don't know that it really matters one way or the other

just looking at the docs, https://docs.djangoproject.com/en/1.5/howto/sta...

any ideas?

IIRC, {% static %} has the advantage of being able to compute hostname components of the URL which may change, such as CDN containers.

Since it calls down to the storage backend to get the URL.

folks -- I'm trying to override submit_line.html to add some logic based on the logged in user, but I can't seem to access request.user in here -- any thoughts? something as simple as request.user.is_superuser doesn't appear to be available.

thanks mattmcc ill start using that after yrs with {{ STATIC_URL }}

aah: you have the request context processor turned on, right?

The auth context processor is on by default, you don't have to go through request.

Though you do still have to use RequestContext.

mattmcc: what do you use

{{ STATIC_URL }} or {% static %}

My stuff's still STATIC_URL, largely because I haven't needed to switch.

word

nevermind I fixed it I wasn't listening at port 433

heh, i just converted an app to use {% static 'url %}

deploying static files sure has gotten better...

at first glance, collectstatic looked laborious and odd…but, i'm sold

same here. haven't needed to switch

how does `collectstatic` look complicated?

just seemed strange to make copies. also, wasn't entirely clear which setting was doing what…but once i actually used it, it was clear

yeah, the static/media stuff could use some better names

…like, so many different settings w/ the word 'STATIC' to wrap your head around

also, the MEDIA_ ones

i think STATIC_ROOT and STATIC_URL are fine

STATICFILES_DIRS should be ASSET_DIRS

then it's easy to explain that your assets get collected into the static root

honestly, i feel like coming at it now for the first time it might not feel as odd. but given the learned behavior of older implementations and usage it was harder

giarc: Don't make copies, make symlinks. ;)

I think both media and static stuff could be named better, but I understand the historical reasons that brought us where we are

and MEDIA_* should be UPLOADS_*

mattmcc: WHAT?

symlinks?

collectstatic -l

ah

mattmcc: oh god no

mattmcc: what does that do for assets that need compilation?

wasn't aware of that...

serving from a CDN anwyay..so, symlinks wont work

Yeah, if you're compiling or hosting offiste, obviously symlinks are out.

so basically if you're doing anything of consequence… ;)

but symlinks makes total sense for same host

for non-compiled, same host, yes

( used to symlink the admin static files in anyway! )

…what sort of 'media' you folks having users upload that needs compiling?

…just curious

none

we're talking about static files

hence 'collectSTATIC'

__love__: "mattmcc: what does that do for assets that need compilation?" ?

giarc: LESS/SASS, JS that you want to compress, etc.

I compile my user photo uploads into a giant sprite via PIL. Makes for bad load times, but really interesting slideshows.

Heh.

even just combining and minifying css and js

i'm on a shared hosting provider and i have 2 domains. they both use the same django project. does it make sense to clone my repo twice onto the server and keep them separate that way or should i configure my project to manage both domains?

ah, gotcha w/ minified js etc

is that even possible with fcgi?

guess i misread that…thought you were referring to uploaded content

( MEDIA rather than STATIC files… ;-) )

thoughts?

krassinger: if it should be identical content for both domains, I don't see any reason to run two instances

krassinger: you could configure the webserver to serve the same code for each domain. seems simpler than having 2 copies

krassinger: the FastCGI task will happily answer requests from wherever

same app stack, same content, then one project. But if they diverge, I'd have two projects (or at least two settings files) sharing apps. Still one Django install, of course.

anyone ever done a nested {% include %} for, say, a Menu structure,, and had problems?

I'm trying to concoct a test case for a PR

FunkyBob: memory is hazy but I seem to recal a problem like that

Given models Supplier and Order, where Order has attribute supplier=ForeignKey(Supplier), can I do a filter() on Supplier to get suppliers with > 0 order records? I'm currently using a list comprehension to iterate over Supplier, which obviously is suboptimal. My nose has been in the docs, to no avail. :/

tbaxter: yeah, there was potentially an infinite recursion issue