Re: hello everyone! I'm working on Django Framework. but

Hi Andréas, Andréas Kühne wrote: > The main thing is that when you start runserver it continuesly checks for > changes in your .py files. So if you change a file, you get a reload. This > shouldn't be running on a production environment. > Another thing is that runserver also serves static files

Re: hello everyone! I'm working on Django Framework. but when I run the script $ ./manage.py runserver or $./manage.py runserver 0.0.0.0:8000 it only work on my system. how to make it public? so that

2017-10-19 9:37 GMT+02:00 Erik Rull : > Hello Andréas, > > Andréas Kühne wrote: > > 1. First of all, you shouldn't run django with runserver on a production > > system. runserver is just for development purposes, and doesn't do a lot > of > > optimization that you get when running it "correctly".

Re: hello everyone! I'm working on Django Framework. but when I run the script $ ./manage.py runserver or $./manage.py runserver 0.0.0.0:8000 it only work on my system. how to make it public? so that

Hello Andréas, Andréas Kühne wrote: > 1. First of all, you shouldn't run django with runserver on a production > system. runserver is just for development purposes, and doesn't do a lot of > optimization that you get when running it "correctly". not a lot of optimizations - uh really? I run Djang

Re: hello everyone! I'm working on Django Framework. but when I run the script $ ./manage.py runserver or $./manage.py runserver 0.0.0.0:8000 it only work on my system. how to make it public? so that

Hi, That is a bit outside of django. 1. First of all, you shouldn't run django with runserver on a production system. runserver is just for development purposes, and doesn't do a lot of optimization that you get when running it "correctly". 2. You need to be on a computer that is accessible from