Message ID | 20240125170042.12022-2-maxim.cournoyer@gmail.com |
---|---|
State | New |
Headers | show |
Series | Add a button to copy a message Message-ID to the clipboard. | expand |
> +You should now be able to visit http://0.0.0.0:1234 in your browser > +and see your local mumi instance running. Could you also mention just before this paragraph, the `mumi web' command that starts the web server?
Hi, Arun Isaac <arunisaac@systemreboot.net> writes: >> +You should now be able to visit http://0.0.0.0:1234 in your browser >> +and see your local mumi instance running. > > Could you also mention just before this paragraph, the `mumi web' > command that starts the web server? Done.
diff --git a/README.org b/README.org index fd1d77b..d092de7 100644 --- a/README.org +++ b/README.org @@ -11,3 +11,27 @@ run #+BEGIN_SRC shell $ guix shell -D mumi #+END_SRC + +** Running a local instance of mumi + +First copy some test mail data to be indexed: + +#+begin_src shell + $ cp -a tests/data data +#+end_src + +Then, to have these emails indexed, run: + +#+begin_src shell + $ ./pre-inst-env mumi fetch +#+end_src + +You should now be able to visit http://0.0.0.0:1234 in your browser +and see your local mumi instance running. + +** Disabling browser caching + +If you modify the CSS or JavaScript source files, you'll want to make +sure your browser doesn't keep cached copies. This can be done by +changing a preference in the development tools menus, which is called +something like "Disable cache (while DevTools is active)".