paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-10-23 16:14:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs/development/using: Small wording change.

Browse Source 
An attempt to make the point about Django/Tornado server processes
auto-restarting less wordy.
This commit is contained in:
Chris Bobbe
2020-01-14 11:20:55 -08:00
committed by Tim Abbott
parent 60f3c06d91
commit 6c3fcc252e
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/development/using.md
View File

@@ -12,12 +12,11 @@ encounters.
Here's what you need to do to see your changes take effect: Here's what you need to do to see your changes take effect:
* If you change Python code used by the main Django/Tornado server * The main Django/Tornado server processes are run on top of Django's
processes, these services are run on top of Django's [manage.py [manage.py runserver][django-runserver], which will automatically
runserver][django-runserver] which will automatically restart the restart them when you save changes to Python code they use. You can
Zulip Django and Tornado servers whenever you save changes to Python watch this happen in the `run-dev.py` console to make sure the backend
code. You can watch this happen in the `run-dev.py` console to make has reloaded.
sure the backend has reloaded.
* The Python queue workers will also automatically restart when you * The Python queue workers will also automatically restart when you
save changes. However, you may need to ctrl-C and then restart save changes. However, you may need to ctrl-C and then restart