#django

hi

for production, what's a good place to put the code directory? under /home?

are there additional costs (besides increased RAM, etc, on the server) to using VOIP on my webpage?

mun: home is for user home directories, not very good option (you may have many developers logging to production server and accessing the code) - ours lies in /urs/local/share/

usr *

logos234: is /usr/local/share root only?

mun: its root owned, you can see that youself doing a simple ls

raj: how would you use VOIP on your webpage?

logos234: so do your dev accounts have root access?

heedly, make phone calls

akin to google hangouts, I suppose

basically call landlines

or mobile phones

I guess it would depend on the client you use.

but there are better technologies than VOIP for web stuff.

mun: yeah but only some of us, and its necessary for monitoring and maitenance purposes

heedly, what do you mean?

logos234: right

raj: HTML5 has i belive mcrophone support as input.

or flash

or maybe webrtc

I'm really jusst throwing ideas at you.

heedly, yes, that's fine

I don't know what is out there.

but what about actually connecting to phone

s

is it a good idea to deploy in a virtualenv even in production?

yes

always

virtualenv protects you from others changing module versions

FunkyBob: right. where do you put your code on production servers usually?

is having a separate app user and putting it under /home/app a good idea?

I tend to run multiple sites per server... but keep it all organised

so /srv/www/{project}/

and in there html/ for static and media, env/ for the virtualenv... code/ for, well, the code

logs/ ... and so on

FunkyBob: right. so you have one account for all sites?

ideally one user per site

raj: you'd need some backend software like asterisk

or a 3rd party VOIP provider

FunkyBob: right.

but the VOIP client would most likely best be run on the server.

FunkyBob: does that mean all your app users are sudoers?

no

why would I let anyone sudo?

no, seriously, mun ... why?

FunkyBob: but to write into /srv/www wouldn't you need sudo?

I set up their project dirs, owned by them...

oh right

actually, in most cases the clients never ssh into the server at all

FunkyBob: in my case, it's just me and one other dev for now

i just wonder how to set it all up for production

i guess putting it all under /srv/www makes things neater

sure does

makes it safer, too

avoids, for instance, default config of web server serving up all you code, logs, etc

heedly, yes, I was looking into asterisk, but how do I get html5 to stream the voice to asterisk, and vice versa

raj: also look at FreeSWITCH

how come date_format(timezone.now(), 'DATETIME_FORMAT') in a tag ignores the value i set for DATETIME_FORMAT in settings.py?

nvm, use_l10n=False made it work

how to fix this http://wklej.to/htZkM/text warning?

i'm using "unique_together = ('email', 'is_active')"? now

Katharsis: it want unique=True on the email field

i know.

if that dsnt make sence for your use-case, and you really want unique_together = ('email, 'is_active'), then ignore the warning

FunkyBob: hi again

FunkyBob: since you put your code under /srv/www do you run gunicorn or whichever with sudo?

FunkyBob: you put your code in /srv? :(

doismellburning: where do you put yours?

mun: /opt/$orgname/$appname

doismellburning: right. would you also need to run with sudo?

i'm just not sure where to put mine

mun: no

mun: you probably don't need/want to run your code as root

doismellburning: but isn't root needed to write to /opt?

mun: normally, sure

mun: root's needed to write to /bin too, but doesn't mean you need to be root to run /bin/ls

mun: I install as root (normally with a package manager - `sudo apt-get install myapp`; sometimes just `sudo tar zxvf myapp.tgz /opt/foo/myapp/`) but definitely don't _run_ as root