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

docs: Remove manual flush memcached advice. 

Co-authored-by: Tim Abbott <tabbott@zulip.com>
This commit is contained in:
Bedo Khaled 2024-03-23 10:05:12 +02:00 committed by Tim Abbott
parent b42cd1022b
commit ed5e0fa141
2 changed files with 18 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/subsystems/schema-migrations.md
View File

@ -180,12 +180,17 @@ If you follow the processes described above, `tools/provision` and
migrations and run migrations on (`./manage.py migrate`) or rebuild
the relevant database automatically as appropriate.
While developing migrations, you may accidentally corrupt
your databases while debugging your new code.
You can always rebuild these databases from scratch.
Notably, both `manage.py migrate` (`git grep post_migrate.connect` for
details) and restarting `tools/run-dev` will flush `memcached`, so you
shouldn't have to worry about cached objects from a previous database
schema.
Use `tools/rebuild-test-database` to rebuild the database
used for `test-backend` and other automated tests.
While developing migrations, you may accidentally corrupt your
databases while debugging your new code. You can always rebuild these
databases from scratch:
Use `tools/rebuild-dev-database` to rebuild the database
used in [manual testing](../development/using.md).
- Use `tools/rebuild-test-database` to rebuild the database
used for `test-backend` and other automated tests.
- Use `tools/rebuild-dev-database` to rebuild the database
used in [manual testing](../development/using.md).

14
docs/tutorials/new-feature-tutorial.md
View File

@ -83,14 +83,13 @@ following commands:
./manage.py migrate
```
You can read our
It's highly recommended to read our
[database migration documentation](../subsystems/schema-migrations.md)
to learn more about creating and applying database migrations.
**Test your changes:** Once you've run the migration, flush memcached
on your development server (`./scripts/setup/flush-memcached`) and then
[restart the development server](../development/remote.md#running-the-development-server)
to avoid interacting with cached objects.
**Test your changes:** Once you've run the migration, [restart the
development
server](../development/remote.md#running-the-development-server).
### Backend changes
@ -262,9 +261,8 @@ Running migrations:
Applying zerver.NNNN_realm_mandatory_topics... OK
```
Once you've run the migration, flush memcached on your development
server (`./scripts/setup/flush-memcached`) and then [restart the development server](../development/remote.md#running-the-development-server)
to avoid interacting with cached objects.
Once you've run the migration, [restart the development
server](../development/remote.md#running-the-development-server).
### Handle database interactions