helm
Synapse
Our great sponsors
helm | Synapse | |
---|---|---|
9 | 367 | |
278 | 11,720 | |
7.9% | - | |
8.2 | 9.8 | |
3 days ago | 5 months ago | |
Smarty | Python | |
GNU Affero General Public License v3.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
helm
- Nextcloud AIO Unhealthy Containers
-
🔥 How to execute occ commands in K8s pod?
When using the Nextcloud Helm Charts, how do you execute OCC commands within a Kubernetes the pod? I've tried:
-
Fresh install Nextcloud on Kubernetes produces errors
I'm running Nextcloud in Kubernetes, using Nextcloud's Helm Chart. With a default installation (no apps or configuration changes), I get the following errors in the logs:
-
Is Kubernetes a good choice for multiple instances of the same app to be deployed automatically?
In each namespace you would deploy a nextcloud instance via whatever method you like. For example, the nextcloud helm chart.
-
How do you enable/disable apps on a docker image/helm deployment?
I'm using the official helm chart to install nextcloud: https://github.com/nextcloud/helm
-
How to setup a remote development environment with code-server and nextcloud
A nextcloud installation (you can install via helm within the same k8s cluster)
-
NextCloud on NFS
There is already a GitHub issue: https://github.com/nextcloud/helm/issues/10
-
New Install Memcache Issues - Need Help Please
I'm not a Nextcloud expert, but your config file looks okay compared to some instances deployed using the nextcloud helm chart.The resulting config uses APCu for memcache.local ('memcache.local' => '\OC\Memcache\APCu') as recommended in the memory caching documentation.
-
Best way to automate docker-compose actions and configuration changes?
For nextcloud in particular, what you want can be done. I've seen it done in their kubernetes helm chart (https://github.com/nextcloud/helm) .
Synapse
-
Organizing OpenStreetMap Mapping Parties
What are you thinking of here? Synapse has supported purging room history since 2016: https://github.com/matrix-org/synapse/pull/911, and configurable data retention since 2019: https://github.com/matrix-org/synapse/pull/5815.
Meanwhile, Matrix has never needed the full room history to be synchronised - when a server joins a room, it typically only grabs the last 20 messages. (It does needs to grab all the key-value state about the room, although these days that happens gradually in the background).
If you're wondering why Matrix implementations are often greedy on disk space, it's because they typically cache the key-value state aggressively (storing a snapshot of it for the room on a regular basis). However, that's just an implementation quirk; folks could absolutely come up with fancier datastructures to store it more efficiently; it's just not got to the top of anyone's todo list yet - things like performance and UX are considered much more important than disk usage right now.
-
GrapheneOS is moving off Matrix
some context re the Matrix isses, long history apparently: https://github.com/matrix-org/synapse/issues/14481#issuecomm...
-
Non-profit Matrix.org Foundation seems to be moving funds to for-profit Element
Why not Matrix? Here's one reason: it has incredibly hard-to-debug edge cases, and plenty of bugs. One of my favourites is the one where people are kicked out of your room at random, which was reported a year ago[0]. It wasn't fixed, however, because the head of the Matrix foundation (Matthew) presumably didn't like the issue being posted on Twitter.
This is honestly really disappointing behaviour from a platform owner.
[0]: https://github.com/matrix-org/synapse/issues/14481
-
The Future of Synapse and Dendrite
> That doesn't make this situation any less bad to the rest of the community.
How is the community suffering here? Let's say Element adds a bunch of baller stuff to their versions over the next few months and then closes the source. Can't the community just fork the last AGPL version? You might say, "well then no one can take the AGPL fork and make their own closed-source business", but do you want them to? Even if you do, they still can with the existing Apache-licensed version, just like Element is doing right now.
You're arguing that Element will lose a lot of contributions, but TFA points out that despite being super open, the vast majority of contributions are still made by Element employees (which seems to be true [0]). It's not the case that Element is looking to monetize the (small) contributions of others, it is the case that others are looking to monetize the (huge) contributions of Element.
And besides, aren't the MSCs the core of Matrix? It's already super possible to build your own compliant client and server.
The situation is that Element needs money to keep developing the ecosystem. It would be cool if there were a big network of donors and contributions, but there isn't. You're essentially saying, "that's fine, go out of business then, and the community will keep developing the ecosystem", but that's not happening now, and it can still happen anyway with the Apache-licensed versions, which again people can still contribute to.
[0]: https://github.com/matrix-org/synapse/graphs/contributors
- Synapse v1.95.0 Released
- Matrix Synapse how use python scripts?
- Synapse v1.91.2 Released
- Synapse v1.89.0 is out
- Synapse v1.88.0 is out
- Synapse v1.87.0 (Matrix Server) Released
What are some alternatives?
Jackett - API Support for your favorite torrent trackers
dendrite - Dendrite is a second-generation Matrix homeserver written in Go!
Transmission - Official Transmission BitTorrent client repository
conduit
docker-mods - Documentation and Examples of base container modifications
Rocket.Chat - The communications platform that puts data protection first.
Kodi Home Theater Software - Kodi is an award-winning free and open source home theater/media center software and entertainment hub for digital media. With its beautiful interface and powerful skinning engine, it's available for Android, BSD, Linux, macOS, iOS, tvOS and Windows.
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
Jellyfin - The Free Software Media System
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
Home Assistant - :house_with_garden: Open source home automation that puts local control and privacy first.
matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker