snapshot of https://github.com/zulip/zulip.git @ 48c69911c7dd4e03b20552eb3bd77ad8151c1357 (2026-09-15)

2026-09-15 15:05:30 +05:00
commit 64898b2c79
8999 changed files with 1757358 additions and 0 deletions
--- a/docs/development/setup/vagrant-rebuild.md
+++ b/docs/development/setup/vagrant-rebuild.md
@@ -0,0 +1,15 @@
+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 `vagrant destroy` and then `vagrant up`. This will usually be
+much faster than the original `vagrant up` since the base image is
+already cached on your machine (it takes about 5 minutes to run with a
+fast Internet connection).
+
+Any additional programs (e.g., Zsh, emacs, etc.) or configuration that
+you may have installed in the development environment will be lost
+when you recreate it. To address this, you can create a script called
+`tools/custom_provision` in your Zulip Git checkout; and place any
+extra setup commands there. Vagrant will run `tools/custom_provision`
+every time you run `vagrant provision` (or create a Vagrant guest via
+`vagrant up`).