paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-03 13:33:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Format Markdown with Prettier.

Browse Source 
Signed-off-by: Anders Kaseorg <anders@zulip.com>
This commit is contained in:
Anders Kaseorg
2021-08-20 13:54:08 -07:00
committed by Anders Kaseorg
parent 35c1c8d41b
commit a4dbc1edd4
108 changed files with 1933 additions and 1753 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/development/using.md
View File

@@ -1,5 +1,4 @@
Using the development environment
=================================
# Using the development environment
This page describes the basic edit/refresh workflows for working with
the Zulip development environment. Generally, the development
@@ -40,12 +39,12 @@ the development environment][authentication-dev-server].
- For changes that don't affect the database model, the Zulip
development environment will automatically detect changes and
restart:
- The main Django/Tornado server processes are run on top of
- The main Django/Tornado server processes are run on top of
Django's [manage.py runserver][django-runserver], which will
automatically restart them when you save changes to Python code
they use. You can watch this happen in the `run-dev.py` console
to make 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, as long as they haven't crashed (which can happen if
they reloaded into a version with a syntax error).
- If you change the database schema (`zerver/models.py`), you'll need
@@ -69,9 +68,9 @@ the development environment][authentication-dev-server].
- By default, the development server homepage just shows a list of the
users that exist on the server and you can log in as any of them by
just clicking on a user.
- This setup saves time for the common case where you want to test
- This setup saves time for the common case where you want to test
something other than the login process.
- You can test the login or registration process by clicking the
- You can test the login or registration process by clicking the
links for the normal login page.
- Most changes will take effect automatically. Details:
- If you change CSS files, your changes will appear immediately via