Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blog(qchat): add paragraph #7

Merged
merged 2 commits into from
Oct 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -149,6 +149,8 @@ Note that:

We've seen the client side of QChat in QGIS. To route the messages through WebSockets, there’s also a backend. [The GitHub repository is available here](https://github.com/geotribu/gischat).

The question might be: why is it not based on a chat standard, like `xmpp` or `matrix`? This is a good question: following the [KISS](https://en.m.wikipedia.org/wiki/KISS_principle) principle, we developed this backend quickly with Qt's websocket availability in QGIS, in order to make it as simple as possible using some trivial message. Making the plugin compatible with a chat standard is under consideration and will probably represent the next consistent step.

### Set up your own instance

If you'd like to set up your own QChat backend, [you can follow the instructions on the repository](https://github.com/geotribu/gischat#deploy-a-self-hosted-instance). There's no need for a database, as it’s stateless and simply relies on WebSockets. It’s a [simple Docker image](https://hub.docker.com/r/gounux/gischat) that runs with a few environment variables.
Expand Down
Loading