Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Update example run-dev output. 

Signed-off-by: Anders Kaseorg <anders@zulip.com>
This commit is contained in:
Anders Kaseorg 2023-12-15 12:57:49 -08:00 committed by Tim Abbott
parent 940c2a1ded
commit 839b04a253
1 changed files with 12 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
docs/development/setup-recommended.md
View File

@ -373,34 +373,24 @@ Next, start the Zulip server:
$ ./tools/run-dev $ ./tools/run-dev
``` ```
You will see several lines of output starting with something like: You will see something like:
```console ```console
2016-05-04 22:20:33,895 INFO: process_fts_updates starting Starting Zulip on:
Recompiling templates
2016-05-04 18:20:34,804 INFO: Not in recovery; listening for FTS updates
done
Validating Django models.py...
System check identified no issues (0 silenced).
Django version 1.8 http://localhost:9991/
Tornado server is running at http://localhost:9993/
Quit the server with CTRL-C.
2016-05-04 18:20:40,716 INFO Tornado loaded 0 event queues in 0.001s
2016-05-04 18:20:40,722 INFO Tornado 95.5% busy over the past 0.0 seconds
Performing system checks...
```
And ending with something similar to: Internal ports:
9991: Development server proxy (connect here)
9992: Django
9993: Tornado
9994: webpack
```console Tornado server (re)started on port 9993
http://localhost:9994/webpack-dev-server/
webpack result is served from http://localhost:9991/webpack/
content is served from /srv/zulip
webpack: bundle is now VALID. 2023-12-15 20:57:14.206 INFO [process_queue] 13 queue worker threads were launched
2016-05-06 21:43:29,553 INFO Tornado 31.6% busy over the past 10.6 seconds frontend:
2016-05-06 21:43:35,007 INFO Tornado 23.9% busy over the past 16.0 seconds frontend (webpack 5.89.0) compiled successfully in 8054 ms
``` ```
Now the Zulip server should be running and accessible. Verify this by Now the Zulip server should be running and accessible. Verify this by