Re: Calling out for Help!
On 10/02/2011 6:19pm, Cal Leeming [Simplicity Media Ltd] wrote: On Wed, Feb 9, 2011 at 4:38 PM, Dev@CB mailto:d...@churchbudget.com>> wrote: Well, the "python manage.py runserver" command returned a screen full of errors. What would be the appropriate way to post that? If you don't wish to copy and paste them all, I think the best way is to look at the last error and try to make sense of what it says. Even so, I found in my early django - when I was probably around your level of dev experience - the absolute easiest way forward was to have a known good setup to go back to and then add in the changes (which too frequently I made all at once) one at a time. Ahh, I hear you say, I haven't yet reached the stage of having a known good setup! Well you really have no choice other than to start again with an eagle-eye and follow the tutorial project very carefully. You cannot afford to use your brain until after it works and you want to try a variation. Good luck. And persevere, it is worth it. Mike -- 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.
Re: Calling out for Help!
Hi, Please also don't take offence if this sounds harsh, but I never have seen much point in beating around the bush, and these are just my own opinions, others may disagree. This may sound old fashioned, but you haven't even greeted yourself to the community with your name, or at the very least a nickname. Also, based on your last response of "returned a screen full of errors", you can't expect us to then reply with "OH a screen full of errors, sure we know what that is, here's a fix". By the sounds of it, you are looking for someone to give you a quick easy solution, and it isn't gonna happen buddy. Many of us help those in need on the list, but asking us to essentially do your job for you falls under the category of "taking the piss". My advice, re-submit your question to the list with precise questions and enough debug/log to show the problem, and we will try our best to answer them. Cal On Wed, Feb 9, 2011 at 4:38 PM, Dev@CB wrote: > Well, the "python manage.py runserver" command returned a screen full > of errors. What would be the appropriate way to post that? I don't > want to burn anyone's special eyes. > And since we are using Apache, I'm going to say we are also using > wsgi. > > > Well, the first thing to see when deploying a django project is the > > settings.py file. Here you'll see the database information. > > > > Then the second step will be testing it (with the command python > > manage.py runserver, it should start the development server, NOT for > > using in production). > > > > The last thing will see the Apache configuration, and it'll depend if > > you're using wsgi or fcgi... More information here: > http://docs.djangoproject.com/en/dev/howto/deployment/http://www.djangobook.com/en/beta/chapter21/ > > > > Hope it isn't that difficult, you can see the configs from the old > > server, right? > > > > Good luck! > > Andres- Hide quoted text - > > > > - Show quoted text - > > -- > 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. > > -- 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.
Re: Calling out for Help!
Hi Justin, Take a chill man, the folks here on this group will surely help you. > Well, the "python manage.py runserver" command returned a screen full > of errors. What would be the appropriate way to post that? I don't > want to burn anyone's special eyes. First try to google that error in most of the cases you'll find a solution, because errors are faced by others also. and if you not get any solution then post the error you are getting along with traceback. > And since we are using Apache, I'm going to say we are also using > wsgi. mod-wsgi right? One thing here I want to ask: Have you specified your application directory in httpd.conf file ? And finally, test every thing locally then commit it and then checkout over amazon instance. Its not much difficult :) Hope it helps Jitesh -- 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.
Re: Calling out for Help!
On Wed, Feb 9, 2011 at 11:38 AM, Dev@CB wrote: > Well, the "python manage.py runserver" command returned a screen full > of errors. What would be the appropriate way to post that? I don't > want to burn anyone's special eyes. > And since we are using Apache, I'm going to say we are also using > wsgi. > > > Well, the first thing to see when deploying a django project is the > > settings.py file. Here you'll see the database information. > > > > Then the second step will be testing it (with the command python > > manage.py runserver, it should start the development server, NOT for > > using in production). > > > > The last thing will see the Apache configuration, and it'll depend if > > you're using wsgi or fcgi... More information here: > http://docs.djangoproject.com/en/dev/howto/deployment/http://www.djangobook.com/en/beta/chapter21/ > > > > Hope it isn't that difficult, you can see the configs from the old > > server, right? > > > > Good luck! > > Andres- Hide quoted text - > > > > - Show quoted text - > > -- > 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. > > As far as getting errors on the development server, you need to look in settings.py. The values in this file will be different for development than for the production machine. Find the development version of this file. (It might be similarly named) -- Joel Goldstick -- 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.
Re: Calling out for Help!
On Wed, Feb 9, 2011 at 11:31 AM, Dev@CB wrote: > I can't let it go.. the whole "ask a question" and "the return key is > your friend" thing. I thought I was writing an intro blerb to the > moderators... anyway, it was in a little web form box and I just kept > typing. I didn't realize it was going to end up as a post. If I wanted > sarcasm I'd start a conversion with my employer. > > On Feb 8, 12:20 pm, Andres Lucena wrote: > > On Tue, Feb 8, 2011 at 6:11 PM, Tom Evans > wrote: > > > On Tue, Feb 8, 2011 at 5:01 PM, Dev@CB wrote: > > >> Tom, why are you discouraging me? > > > > > My intention was not to discourage you; it was to encourage you to ask > > > a sensible question in a legible manner. If you take slight at that, > > > then I have no problem with not corresponding with you further. > > > > I think that is always helpful this text: > > > > http://www.catb.org/~esr/faqs/smart-questions.html > > > > Specially the part: > > > > 1. Try to find an answer by searching the archives of the forum you > > plan to post to. > > 2. Try to find an answer by searching the Web. > > 3. Try to find an answer by reading the manual. > > 4. Try to find an answer by reading a FAQ. > > 5. Try to find an answer by inspection or experimentation. > > 6. Try to find an answer by asking a skilled friend. > > 7. If you're a programmer, try to find an answer by reading the source > code. > > > > And the return key is your friend ;) > > -- > 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. > > I'm wondering how a report that takes several hours to run will suddenly run in minutes by moving the application to a more robust server environment. The difference in processors between the two environment 'might' be 2 or 3 times different. That could get you from 2 hours to 1/2 hour. The amount of memory available might also be larger, and that would help. But wouldn't you be better off reviewing the model that creates the report? Have you run that report on the local development server? If you haven't, I'd start there. You could add code to find out where the bottlenecks. -- Joel Goldstick -- 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.
Re: Calling out for Help!
Well, the "python manage.py runserver" command returned a screen full of errors. What would be the appropriate way to post that? I don't want to burn anyone's special eyes. And since we are using Apache, I'm going to say we are also using wsgi. > Well, the first thing to see when deploying a django project is the > settings.py file. Here you'll see the database information. > > Then the second step will be testing it (with the command python > manage.py runserver, it should start the development server, NOT for > using in production). > > The last thing will see the Apache configuration, and it'll depend if > you're using wsgi or fcgi... More information > here:http://docs.djangoproject.com/en/dev/howto/deployment/http://www.djangobook.com/en/beta/chapter21/ > > Hope it isn't that difficult, you can see the configs from the old > server, right? > > Good luck! > Andres- Hide quoted text - > > - Show quoted text - -- 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.
Re: Calling out for Help!
I can't let it go.. the whole "ask a question" and "the return key is your friend" thing. I thought I was writing an intro blerb to the moderators... anyway, it was in a little web form box and I just kept typing. I didn't realize it was going to end up as a post. If I wanted sarcasm I'd start a conversion with my employer. On Feb 8, 12:20 pm, Andres Lucena wrote: > On Tue, Feb 8, 2011 at 6:11 PM, Tom Evans wrote: > > On Tue, Feb 8, 2011 at 5:01 PM, Dev@CB wrote: > >> Tom, why are you discouraging me? > > > My intention was not to discourage you; it was to encourage you to ask > > a sensible question in a legible manner. If you take slight at that, > > then I have no problem with not corresponding with you further. > > I think that is always helpful this text: > > http://www.catb.org/~esr/faqs/smart-questions.html > > Specially the part: > > 1. Try to find an answer by searching the archives of the forum you > plan to post to. > 2. Try to find an answer by searching the Web. > 3. Try to find an answer by reading the manual. > 4. Try to find an answer by reading a FAQ. > 5. Try to find an answer by inspection or experimentation. > 6. Try to find an answer by asking a skilled friend. > 7. If you're a programmer, try to find an answer by reading the source code. > > And the return key is your friend ;) -- 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.
Re: Calling out for Help!
I have found http://stackoverflow.com/questions/tagged/django to be an awesome resource. CH -- 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.
Re: Calling out for Help!
On Tue, Feb 8, 2011 at 6:11 PM, Tom Evans wrote: > On Tue, Feb 8, 2011 at 5:01 PM, Dev@CB wrote: >> Tom, why are you discouraging me? >> > > My intention was not to discourage you; it was to encourage you to ask > a sensible question in a legible manner. If you take slight at that, > then I have no problem with not corresponding with you further. > I think that is always helpful this text: http://www.catb.org/~esr/faqs/smart-questions.html Specially the part: 1. Try to find an answer by searching the archives of the forum you plan to post to. 2. Try to find an answer by searching the Web. 3. Try to find an answer by reading the manual. 4. Try to find an answer by reading a FAQ. 5. Try to find an answer by inspection or experimentation. 6. Try to find an answer by asking a skilled friend. 7. If you're a programmer, try to find an answer by reading the source code. And the return key is your friend ;) -- 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.
Re: Calling out for Help!
On Tue, Feb 8, 2011 at 5:01 PM, Dev@CB wrote: > Tom, why are you discouraging me? > My intention was not to discourage you; it was to encourage you to ask a sensible question in a legible manner. If you take slight at that, then I have no problem with not corresponding with you further. Enjoy your lunch. Tom -- 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.
Re: Calling out for Help!
Andres, Thank you for your kind, helpful reply. Heading to lunch now, more django later! Thank you again, Justin -- 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.
Re: Calling out for Help!
Tom, why are you discouraging me? -- 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.
Re: Calling out for Help!
On Tue, Feb 8, 2011 at 4:26 PM, Dev@CB wrote: > Hello. I hope someone is maybe having a slow day and can spend a > little time with me. Here's the whole story: Several months ago, our > company started a django project. This project was headed by one man. > Well, as of early January, he is no longer with the company. Now, we, > the survivors, have the task of completing the project. Oh, little > more background: Everything was set up on an Amazon cloud server. I > think originally the project seemed simple enough to be run on a > “small cloud”. So, here is where we are at now: This one report > actually turned out to be a monster and took several hours to run. > That’s not good; that report needs to run in a few minutes with more > data being processed. So, I created a “large cloud” (with AutoScaling, > a feature not available to small clouds), installed Apache, PHP, > MySQL, Python, and Django. I used SCP to copy the data from one server > to another. Now, I need to align the configuration files to make it > all work on the new server. This is where I need help. The small > server was a Ubuntu distro and the large is a SUSE Enterprise 64-bit > version, and some default paths and different things are not the same. > I mentioned I did all the setup myself to give you the idea that I’m > linux-savvy, but in truth, that was all a learning experience. I’m > learning fast, but my supervisor wants all this done last week. Can > anyone help me? At least give me a good push in the right directions, > so that I can take off on my own again. Please? > My first piece of advice is discover the return key on your keyboard. The second is to ask a question. Cheers Tom -- 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.
Re: Calling out for Help!
On Tue, Feb 8, 2011 at 5:26 PM, Dev@CB wrote: > Hello. I hope someone is maybe having a slow day and can spend a > little time with me. Here's the whole story: Several months ago, our > company started a django project. This project was headed by one man. > Well, as of early January, he is no longer with the company. Now, we, > the survivors, have the task of completing the project. Oh, little > more background: Everything was set up on an Amazon cloud server. I > think originally the project seemed simple enough to be run on a > “small cloud”. So, here is where we are at now: This one report > actually turned out to be a monster and took several hours to run. > That’s not good; that report needs to run in a few minutes with more > data being processed. So, I created a “large cloud” (with AutoScaling, > a feature not available to small clouds), installed Apache, PHP, > MySQL, Python, and Django. I used SCP to copy the data from one server > to another. Now, I need to align the configuration files to make it > all work on the new server. This is where I need help. The small > server was a Ubuntu distro and the large is a SUSE Enterprise 64-bit > version, and some default paths and different things are not the same. > I mentioned I did all the setup myself to give you the idea that I’m > linux-savvy, but in truth, that was all a learning experience. I’m > learning fast, but my supervisor wants all this done last week. Can > anyone help me? At least give me a good push in the right directions, > so that I can take off on my own again. Please? > Well, the first thing to see when deploying a django project is the settings.py file. Here you'll see the database information. Then the second step will be testing it (with the command python manage.py runserver, it should start the development server, NOT for using in production). The last thing will see the Apache configuration, and it'll depend if you're using wsgi or fcgi... More information here: http://docs.djangoproject.com/en/dev/howto/deployment/ http://www.djangobook.com/en/beta/chapter21/ Hope it isn't that difficult, you can see the configs from the old server, right? Good luck! Andres -- 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.
Calling out for Help!
Hello. I hope someone is maybe having a slow day and can spend a little time with me. Here's the whole story: Several months ago, our company started a django project. This project was headed by one man. Well, as of early January, he is no longer with the company. Now, we, the survivors, have the task of completing the project. Oh, little more background: Everything was set up on an Amazon cloud server. I think originally the project seemed simple enough to be run on a “small cloud”. So, here is where we are at now: This one report actually turned out to be a monster and took several hours to run. That’s not good; that report needs to run in a few minutes with more data being processed. So, I created a “large cloud” (with AutoScaling, a feature not available to small clouds), installed Apache, PHP, MySQL, Python, and Django. I used SCP to copy the data from one server to another. Now, I need to align the configuration files to make it all work on the new server. This is where I need help. The small server was a Ubuntu distro and the large is a SUSE Enterprise 64-bit version, and some default paths and different things are not the same. I mentioned I did all the setup myself to give you the idea that I’m linux-savvy, but in truth, that was all a learning experience. I’m learning fast, but my supervisor wants all this done last week. Can anyone help me? At least give me a good push in the right directions, so that I can take off on my own again. Please? -- 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.
