Sfoglia il codice sorgente

Replace "Warnings" with the colorfully decorated one

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
pull/4033/head
Suguru Hirahara 1 anno fa
parent
commit
16eda7a072
Non sono state trovate chiavi note per questa firma nel database ID Chiave GPG: E4F9743DAB4B7B75
5 ha cambiato i file con 15 aggiunte e 23 eliminazioni
  1. +3
    -5
      docs/configuring-playbook-conduit.md
  2. +3
    -5
      docs/configuring-playbook-conduwuit.md
  3. +3
    -5
      docs/configuring-playbook-dendrite.md
  4. +3
    -3
      docs/configuring-playbook-matrix-registration.md
  5. +3
    -5
      docs/uninstalling.md

+ 3
- 5
docs/configuring-playbook-conduit.md Vedi File

@@ -8,11 +8,9 @@ By default, the playbook installs [Synapse](https://github.com/element-hq/synaps

💡 **Note**: The playbook also supports installing a (currently) faster-moving Conduit fork called [conduwuit](./configuring-playbook-conduwuit.md).

⚠️ **Warnings**:

- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.

- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
> [!WARNING]
> - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
> - **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding

## Adjusting the playbook configuration



+ 3
- 5
docs/configuring-playbook-conduwuit.md Vedi File

@@ -8,11 +8,9 @@ By default, the playbook installs [Synapse](https://github.com/element-hq/synaps

💡 **Note**: conduwuit is a fork of [Conduit](./configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html).

⚠️ **Warnings**:

- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.

- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
> [!WARNING]
> - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
> - **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding

## Adjusting the playbook configuration



+ 3
- 5
docs/configuring-playbook-dendrite.md Vedi File

@@ -6,11 +6,9 @@ See the project's [documentation](https://element-hq.github.io/dendrite/) to lea

By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document.

⚠️ **Warnings**:

- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.

- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
> [!WARNING]
> - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
> - **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding

## Adjusting the playbook configuration



+ 3
- 3
docs/configuring-playbook-matrix-registration.md Vedi File

@@ -1,8 +1,8 @@
# Setting up matrix-registration (optional)

⚠️ **Warnings**:
- This is a poorly maintained and buggy project. It's better to avoid using it.
- This is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)
> [!WARNING]
> - This is a poorly maintained and buggy project. It's better to avoid using it.
> - This is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)

The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you. It is a simple python application to have a token based Matrix registration.



+ 3
- 5
docs/uninstalling.md Vedi File

@@ -1,10 +1,8 @@
# Uninstalling

⚠️ **Warnings**:
- If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating.
- If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**.

-----------------
> [!WARNING]
> - If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating.
> - If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**.

## Uninstalling using a script



Caricamento…
Annulla
Salva