optional role for matrix-fluffygate #3677
Conversation
| { | ||
| "active_provider": "claude.ai", | ||
| "active_organization_id": "4c1644e0-e630-48f7-bb87-4d8387ef9cd8", | ||
| "active_project_id": "1d6c1d5c-5270-439c-9885-aff7168cb24d", | ||
| "active_project_name": "matrix-fluffygate", | ||
| "local_path": "/Users/alexis/Work/witi/witi-matrix-ansible/roles/custom/matrix-fluffygate" | ||
| } |
| The playbook can install and configure [Fluffygate](https://github.com/krille-chan/fluffygate), a simple Push Gateway for Fluffychat. | ||
|
|
||
| See the project's documentation to learn what it does and why it might be useful to you. | ||
|
|
||
| **Note**: most people don't need to install their own gateway. This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves, as you'll need access to your own Firebase/FCM and APNS credentials. |
There was a problem hiding this comment.
It may be useful to also mention Sygnal here (docs/configuring-playbook-sygnal.md) here and mention Fluffygate on the Sygnal docs page as well.
If this "mention" is also a brief comparison as to when one might use one or the other, it'd be even better. It seems like Sygnal is supports direct delivery via APNS , while Fluffygate only supports FCM? Maybe this makes setup easier as all platform-specific setup would happen on the FCM side?
| - `matrix_fluffygate_hostname` | ||
| - `matrix_fluffygate_path_prefix` |
There was a problem hiding this comment.
Should we consider automatically configuring matrix_fluffygate_hostname to point to matrix_server_fqn_matrix and matrix_fluffygate_path_prefix to be something like /fluffygate, etc?
This way we'll have a reasonable default.
Have you confirmed that hosting it under a path prefix works as expected?
There was a problem hiding this comment.
I'll clean things up bit later - very little time these days, yet wanted to contribute to the upstream.
I tried hosting on the same host but that did not work for some reason and I went with a dedicated hostname instead. Can try again later.
Co-authored-by: Suguru Hirahara <[email protected]>
Co-authored-by: Suguru Hirahara <[email protected]>
…-ansible-deploy into feature-fluffygate
| ## Adjusting DNS records | ||
|
|
||
| You will need to configure your DNS records to point the Fluffygate hostname to your server. This typically involves creating either: | ||
| - an A record pointing to your server's IPv4 address | ||
| - a CNAME record pointing to your server's hostname |
There was a problem hiding this comment.
Per existing lines for Sygnal here.
Please update the default CNAME record push, when addressing the comment.
| ## Adjusting DNS records | |
| You will need to configure your DNS records to point the Fluffygate hostname to your server. This typically involves creating either: | |
| - an A record pointing to your server's IPv4 address | |
| - a CNAME record pointing to your server's hostname | |
| ## Adjusting DNS records | |
| Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Fluffygate domain to the Matrix server. | |
| By default, you will need to create a CNAME record for `push`. See [Configuring DNS](configuring-dns.md) for details about DNS changes. | |
| If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration. |
No description provided.