docker-zulip VS Zulip

Running an arbitrary thing in Docker is far easier than without it. If I want to run the PHP/MySQL-based Matomo, I can just grab the ready-made docker-compose.yml [0] and tell my main nginx to proxy_pass onto it. I don’t need to figure out how to configure MySQL/MariaDB/PHP-FPM and what hacks did my distro introduce to it (at least I’m not using Debian/Ubuntu, so there shouldn’t be that many). Similarly, I can get Zulip in Docker [1] (even if it’s apparently in alpha state) and not mess with the Python packaging trainwreck, and also setting up all of Redis, PostgreSQL, RabbitMQ and memcached.

[0]: https://github.com/matomo-org/docker/tree/master/.examples/n...

[1]: https://github.com/zulip/docker-zulip

> complicated to deploy. Not just a simple docker container or anything.

Huh? https://github.com/zulip/docker-zulip

We started with this, but slightly modified it for our use - added database backup, and changed the configuration, as we needed to configure things that are not possible to configure via env vars (SSO, for example).

> Because there isn't a good replacement in open source software

https://github.com/zulip/zulip/blob/9.4/LICENSE (Apache 2) and if you mean "good [hosted] replacement" https://zulip.com/for/open-source/

It, of course, does not speak to your decentralized wishlist but I'm sure they'd welcome an issue describing your goals

If you are willing to explore a hybrid model of chat, there is Zulip: https://github.com/zulip/zulip

👩‍💻 GitHub link | ⭐ 21.4K stars | 💻 Website link

Search engines are great at rendering content using JavaScript, they're just not able to explore the Zulip web application's URL structure, so they tend to index one page per Zulip installation.

The current solution is that projects that want their publicly available content to be search engine indexed set up https://github.com/zulip/zulip-archive, which usually involves hooking a GitHub action up to GitHub Pages for a 0-infrastructure deployment. Ultimately, that's the same model as an IRC indexing project like this one: a separate tool from the chat server is responsible for search engine indexing.

Lean runs one here: https://leanprover-community.github.io/archive/, but it looks like it hasn't updated in a year, so likely whoever in the Lean community needs to investigate why it isn't updating.

https://github.com/zulip/zulip/issues/21881 tracks our goal of making the server natively offer search engine indexing. The current separate archive tool model has some advantages (search engine load can't break the server, for example), but I think it'll be worth doing the native version when we can find the resources for it.

Source: I lead the Zulip project.

Zulip does this: https://github.com/zulip/zulip/blob/main/zerver/models/__ini...

Zulip in general is a great example of a large open source Django app that's been maintained and actively developed for a long time. I use it as a reference quite a lot.

We’d like to fix this! You can upvote https://github.com/zulip/zulip/issues/21881 to help us prioritize this feature.

GitHub: Zulip GitHub Repository