Re: subprocess behave diferent in the server than in the client.

...@googlegroups.com > *Subject: *Re: subprocess behave diferent in the server than in the > client. > > playing a littlie bit more, I found out that does work if I am using the > manage.py runserver. > but doesn't work using the production django =(. > > > > On

Re: subprocess behave diferent in the server than in the client.

ooglegroups.com Subject: Re: subprocess behave diferent in the server than in the client. playing a littlie bit more, I found out that does work if I am using the manage.py runserver. but doesn't work using the production django =(. On Monday, March 30, 2015 at 5:53:59 PM UTC-5, dk wrote: >

Re: subprocess behave diferent in the server than in the client.

What is your production stack (nginx/uwsgi/permissions folder etc. etc.)? Do you have any logger / stack trace to debug it? Thanks On 03/31/2015 05:12 PM, dk wrote: playing a littlie bit more, I found out that does work if I am using the manage.py runserver. but doesn't work using the producti

Re: subprocess behave diferent in the server than in the client.

playing a littlie bit more, I found out that does work if I am using the manage.py runserver. but doesn't work using the production django =(. On Monday, March 30, 2015 at 5:53:59 PM UTC-5, dk wrote: > hi, I have a button in my webpage that lunch a subprocess and check the > ping of the compu

subprocess behave diferent in the server than in the client.

hi, I have a button in my webpage that lunch a subprocess and check the ping of the computer and save the information in a text file. that's it, very basic stuff. If I am doing my click in the server computer everything works, the subprocess will ping the computer, make the file and save the