64898b2c79
Some checks failed
Code scanning / CodeQL (push) Failing after 15s
Zulip production suite / Ubuntu 22.04 production build (push) Failing after 26s
Zulip production suite / Debian 12 production install with custom db name and user (push) Has been skipped
Zulip production suite / Ubuntu 22.04 production install and PostgreSQL upgrade with pgroonga (push) Has been skipped
Zulip production suite / Ubuntu 24.04 production install (push) Has been skipped
Zulip production suite / Ubuntu 26.04 production install (push) Has been skipped
Zulip production suite / Debian 13 production install (push) Has been skipped
Zulip production suite / 7.0 Version Upgrade (push) Has been skipped
Zulip production suite / 8.0 Version Upgrade (push) Has been skipped
Zulip production suite / 6.0 Version Upgrade (push) Has been skipped
Zulip production suite / 10.0 Version Upgrade (push) Has been skipped
Zulip production suite / 9.0 Version Upgrade (push) Has been skipped
Zulip production suite / 12.0 Version Upgrade (push) Has been skipped
Zulip production suite / 11.0 Version Upgrade (push) Has been skipped
GitHub Actions Security Analysis with zizmor / zizmor (push) Failing after 3s
Zulip CI / Debian 12 (Python 3.11, backend + documentation) (push) Failing after 26s
Zulip CI / Ubuntu 22.04 (Python 3.10, backend + frontend) (push) Failing after 3s
Zulip CI / Ubuntu 24.04 (Python 3.12, backend) (push) Failing after 25s
Zulip CI / Ubuntu 26.04 (Python 3.14, backend) (push) Failing after 25s
Zulip CI / Debian 13 (Python 3.13, backend) (push) Failing after 28s
Zulip production suite / Required jobs (push) Has been cancelled
Zulip CI / Required jobs (push) Has been cancelled
API Documentation Update Check / check-feature-level-updated (push) Has been cancelled
API Documentation Update Check / notify-if-api-docs-changed (push) Has been cancelled
43 lines
1.3 KiB
Markdown
43 lines
1.3 KiB
Markdown
If you ever want to recreate your development environment again from
|
|
scratch (e.g., to test a change you've made to the provisioning
|
|
process, or because you think something is broken), you can do so
|
|
using the following steps:
|
|
|
|
1. To find the distribution name to unregister (delete), open Command
|
|
Prompt or PowerShell and use the following command:
|
|
|
|
```console
|
|
$ wsl --list --verbose
|
|
```
|
|
|
|
If you are unsure about which distribution to unregister, you can log
|
|
into the WSL distributions to ensure you are deleting the one
|
|
containing your development environment using the command:
|
|
|
|
```console
|
|
wsl -d <Distribution Name>
|
|
```
|
|
|
|
2. To uninstall your WSL distribution, enter the command:
|
|
|
|
```console
|
|
$ wsl --unregister <Distribution Name>
|
|
```
|
|
|
|
For more information, checkout the [official documentation for WSL
|
|
commands](https://learn.microsoft.com/en-us/windows/wsl/basic-commands#unregister-or-uninstall-a-linux-distribution)
|
|
|
|
3. **Next, follow the setup instructions**, starting from [[Step 1:
|
|
Install
|
|
prerequisites]](/development/setup-recommended.md#step-1-install-prerequisites)
|
|
|
|
If you just want to rebuild the development database, the following is
|
|
much faster:
|
|
|
|
```console
|
|
$ ./tools/rebuild-dev-database
|
|
```
|
|
|
|
For more details, see the [schema migration
|
|
documentation](/subsystems/schema-migrations.md#local-schema-rebuilds).
|