#django

I will

it's just doing manage.py syncdb, right?

Clientkill: huh?

the tutorial is a lot more than that

ok

gah

so I followed the tut

and it said do the test run of the server

and I'm getting the confirmation that the server is running at a local address but I can't connect to it

...

are you trying to connect to it from the machine it's running on?

FunkyBob: I admire you mate...

as it will be showing you, it's by default bound to 127.0.0.1 ... localhost... so other machines can't connect

oh

well, since I'm on SSH, no

Clientkill: if you want otherwise.... try "./manage.py runserver 0:8000"

I did that

it won't connect to 0:8000

FunkyBob: I think if he's using SSH then the solution would be open the port, or run it as sudo on port 80

never seen anything like 0:8000

Y3K: no

when i wanted to hit the runserver from other machines, i'd just bind to a non-loopback ip of the desired interface

I can't sudo that command anyways

I don't know what I should run it as

you don't need to sudo it

so what should I do?

I can't have it as a localhost

what I said to do

0:8000 didn't work

don't just say" didn't work"...

that's fucking useless

WHAT HAPPENEd to make you say it didn't work?

okay, it says the server is running on 0:8000

when I connect, it says it can't connect

"when I connect"

how are you connecting?

you _do_ understand I cna't see your scree... or read your mind... right?

screen

In my browser

go on...

I type in http://0:8000/

ok... now at some point here you need to engage your own brain

ah

telling django runserver to bind to "0:8000" is telling it to bind to port 8000 on _all_ IPs on the machine

so... instead of '0' there... put the address you SSH to

ok

it worked

this sounds relavent to my interestes

interests

because I'm going to need to run the dev server over an SSH connection in the very near future

it's exactly the same as running a dev server on your local machine

any ideas why logging is very slow? such as `logger = logging.getLogger(__name__);logger.error("somethinfg")`, it takes about 1.8 sec to log one line. (django is running under uWSGI)

[unless your local machine is windows... then... well.. sucks to be you :)]

except i'm not going to be able to go to 127.blah.blah.blah, right?

Wolfram74: _running_ it is no different... _connecting_ to it is

that would be the hang up i'm anticipating

and now you know the brute-force solution

yay, violence?

FunkyBob: here's another catch

I'm in my site directory and there's no settings.py

Clientkill: are you in the dir with manage.py?

yea

then, as I told you before, settings.py is in your project module...

we never got to that

Clientkill: type "find ." when you're in your workspace [where manage.py is]

yes we fucking well did

not my fault if you ignore half of what I say

you just said one thing about it and we moved on to the next topic

:)

I'm listening to everything you're saying

did this guy just skip wading through the tutorial?

no?

Wolfram74: I reckon

This is the problem with IRC channels

Clientkill: so, you're in your workspace

the dir where 'manage.py' is .... y es?

yes

it's right in there

what's right in there?

manage.py

are you in the terminal or using a desktop and stuff?

ok

that is your _workspace_

hey guys, lets say you have an important operation wrapped in a transaction, if something fails you'd want to roll back the transaction, but lets say you want to log its sucess or failure? how can you reliably do something to your database that will happen independantly of the other transaction's stuff?

right

inside that there is another dir... of the same name.... yes?

yes

settings.py is there

that is your _project_ _module_

as I told you before, settings.py and urls.py and some other stuff will be in there

_o_ _k_

you know, google hangouts have a really convenient screen sharing component to them

If I ever start partner programming, i'm gonna use it

now... I'm going to lunch

I'd rather learn on my own, if you're referencing this situation

Clientkill: have fun with the tutorial

thank you for the help

</sincere>

Derailed: take a look at this https://docs.djangoproject.com/en/dev/topics/db...

I can add whatever engine I want, right?

thanks prudnikov. what happens if you have a commit_manually nested inside a 'commit_on_success'?

you know what I think would improve the 4 part tutorial?

what