mirror of
https://github.com/YunoHost-Apps/discourse_ynh.git
synced 2024-09-03 18:26:18 +02:00
Auto-update READMEs
This commit is contained in:
yunohost-bot
autoreadme_webhook
parent
83345a3c50
commit
d9b554c686
6 changed files with 29 additions and 674 deletions
105
README.md
105
README.md
|
|
@ -16,37 +16,6 @@ It shall NOT be edited by hand.
|
|||
|
||||
## Overview
|
||||
|
||||
Discourse is modern forum software for your community. Use it as a mailing list, discussion forum, long-form chat room, and more!
|
||||
|
||||
**Shipped version:** 2.8.14~ynh2
|
||||
|
||||
**Demo:** <https://try.discourse.org>
|
||||
|
||||
## Screenshots
|
||||
|
||||
|
||||
|
||||
## Disclaimers / important information
|
||||
|
||||
## Disclaimer
|
||||
|
||||
This package installs Discourse without Docker, for several reasons (mostly to support ARM architecture and low-profile servers, to mutualize nginx/postgresql/redis services and to simplify e-mail setup).
|
||||
As stated by the Discourse team:
|
||||
> The only officially supported installs of Discourse are [Docker](https://www.docker.io/) based. You must have SSH access to a 64-bit Linux server **with Docker support**. We regret that we cannot support any other methods of installation including cpanel, plesk, webmin, etc.
|
||||
|
||||
So please have this in mind when considering asking for Discourse support.
|
||||
|
||||
Moreover, you should have in mind Discourse [hardware requirements](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md#hardware-requirements):
|
||||
- modern single core CPU, dual core recommended
|
||||
- 1 GB RAM minimum (with swap)
|
||||
- 64 bit Linux compatible with Docker
|
||||
- 10 GB disk space minimum
|
||||
|
||||
Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
||||
- installation can last up to 3 hours,
|
||||
- first access right after installation could take a couple of minutes.
|
||||
|
||||
## Overview
|
||||
[Discourse](http://www.discourse.org) is the 100% open source discussion platform built for the next decade of the Internet. Use it as a:
|
||||
|
||||
- mailing list
|
||||
|
|
@ -55,80 +24,14 @@ Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
|||
|
||||
To learn more about the philosophy and goals of the project, [visit **discourse.org**](http://www.discourse.org).
|
||||
|
||||
## Configuration
|
||||
|
||||
Use the admin panel of your Discourse to configure this app.
|
||||
**Shipped version:** 2.8.14~ynh3
|
||||
|
||||
### Configuring "Reply-By-Email"
|
||||
**Demo:** <https://try.discourse.org>
|
||||
|
||||
* You should create a dedicated Yunohost user for Discourse whose mailbox will be used by the Discourse application. You can do this with `yunohost user create response`, for example. You should ensure that the email address is configured to be on your Discourse domain.
|
||||
## Screenshots
|
||||
|
||||
* You should then configure your Discourse `/var/www/discourse/config/discourse.conf` file with the correct SMTP configuration values. Please see [this comment](https://github.com/YunoHost-Apps/discourse_ynh/issues/2#issuecomment-409510325) for an explanation of what values to change. Please be aware, when you update the application, you will have to re-apply this configuration.
|
||||
|
||||
* You must enable the Pop3 configuration for Dovecot. See [this thread](https://forum.yunohost.org/t/how-to-enable-pop3-in-yunohost/1662/2) on how to do that. You can validate your configuration with `systemctl restart dovecot && dovecot -n`. Don't forget to open the ports you need (`995` is the default). You can validate that with `nmap -p 995 yunohostdomain.org`.
|
||||
|
||||
* You should then configure the Pop3 polling in the Discourse admin interface. Please see [this comment](https://meta.discourse.org/t/set-up-reply-via-email-support/14003) for how to do so. You will need to follow step 5 in that comment. You can specify your main Yunohost domain for the `pop3_polling_host`.
|
||||
|
||||
You should now be able to start testing. Try using the `/admin/email` "Send Test Email" and then view the "Sent" or "Skipped" etc. tabs. You should see a report on what happened with the email. You may also want to look in `/var/www/discourse/log/production.log` as well as `/var/www/mail.err`. You should perhaps also use [Rainloop](https://github.com/YunoHost-Apps/rainloop_ynh) or another Yunohost email client application to quickly test that both your user and the dedicated Yunohost Discourse user (`response@...`) is receiving mail.
|
||||
|
||||
### "Reply-By-Email" and mail forwarding
|
||||
|
||||
If you use the administration UI in YunoHost to setup a mail forwarding address for your users then you may face the problem whereby your users are replying by email from the forwarded email address and the Discourse software is not able to understand how to receive that email.
|
||||
|
||||
For example, your user has email address `foo@myyunohostdomain.org` and all mail is forwarded to `foo@theirexternalmail.com`. Discourse receives replies from `foo@theirexternalmail.com` but cannot understand how to deliver this to the user account with `foo@myyunohostdomain.org` configured.
|
||||
|
||||
Their is on-going work to allow for [multiple email addresses for one user](https://meta.discourse.org/t/additional-email-address-per-user-account-support/59847) in Discourse development but at current major version (2.3 as of 2019-08-06), there is no web interface for this functionality. It is possible to set it up via the command-line interface but it is **experimental** and you should not undertake this work unless you take some time to understand what it is you are going to do.
|
||||
|
||||
Here's how to setup a secondary mail address for a user account:
|
||||
|
||||
```bash
|
||||
$ cd /var/www/discourse
|
||||
$ RAILS_ENV=production /opt/rbenv/versions/2.7.1/bin/bundle exec rails c
|
||||
$ UserEmail.create!(user: User.find_by_username("foo"), email: "foo@theirexternalmail.com")
|
||||
```
|
||||
|
||||
## YunoHost specific features
|
||||
|
||||
* Integration with YunoHost users and SSO:
|
||||
* LDAP integration: on the login pop-up, you can choose "Login with LDAP" and use your YunoHost credentials
|
||||
* private mode: Forum only accessible by YunoHost users
|
||||
* public mode: Visible by anyone
|
||||
|
||||
#### Multi-user support
|
||||
|
||||
Supported, with LDAP (no SSO).
|
||||
|
||||
|
||||
|
||||
Default administrator and YunoHost users must login using LDAP:
|
||||
* click on the "with LDAP" button
|
||||
* use your YunoHost credentials
|
||||
|
||||
When disabling Local Login and other authentication services, clicking the `Login` or `Sign Up` button will directly bring up the LDAP Login popup.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Limitations
|
||||
|
||||
None at the moment.
|
||||
|
||||
## Additional information
|
||||
### Known non-impacting log messages
|
||||
```
|
||||
fatal: Not a git repository (or any of the parent directories): .git
|
||||
|
||||
bash: BASH_XTRACEFD: 7: invalid value for trace file descriptor
|
||||
```
|
||||
## How-tos
|
||||
### Install plugins
|
||||
```
|
||||
cd /var/www/discourse
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace plugin:install repo=https://github.com/discourse/discourse-solved (for example)
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace assets:precompile
|
||||
systemctl restart discourse
|
||||
```
|
||||
|
||||
|
||||
## Documentation and resources
|
||||
|
||||
|
|
|
|||
105
README_es.md
105
README_es.md
|
|
@ -16,37 +16,6 @@ No se debe editar a mano.
|
|||
|
||||
## Descripción general
|
||||
|
||||
Discourse is modern forum software for your community. Use it as a mailing list, discussion forum, long-form chat room, and more!
|
||||
|
||||
**Versión actual:** 2.8.14~ynh2
|
||||
|
||||
**Demo:** <https://try.discourse.org>
|
||||
|
||||
## Capturas
|
||||
|
||||
|
||||
|
||||
## informaciones importantes
|
||||
|
||||
## Disclaimer
|
||||
|
||||
This package installs Discourse without Docker, for several reasons (mostly to support ARM architecture and low-profile servers, to mutualize nginx/postgresql/redis services and to simplify e-mail setup).
|
||||
As stated by the Discourse team:
|
||||
> The only officially supported installs of Discourse are [Docker](https://www.docker.io/) based. You must have SSH access to a 64-bit Linux server **with Docker support**. We regret that we cannot support any other methods of installation including cpanel, plesk, webmin, etc.
|
||||
|
||||
So please have this in mind when considering asking for Discourse support.
|
||||
|
||||
Moreover, you should have in mind Discourse [hardware requirements](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md#hardware-requirements):
|
||||
- modern single core CPU, dual core recommended
|
||||
- 1 GB RAM minimum (with swap)
|
||||
- 64 bit Linux compatible with Docker
|
||||
- 10 GB disk space minimum
|
||||
|
||||
Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
||||
- installation can last up to 3 hours,
|
||||
- first access right after installation could take a couple of minutes.
|
||||
|
||||
## Overview
|
||||
[Discourse](http://www.discourse.org) is the 100% open source discussion platform built for the next decade of the Internet. Use it as a:
|
||||
|
||||
- mailing list
|
||||
|
|
@ -55,80 +24,14 @@ Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
|||
|
||||
To learn more about the philosophy and goals of the project, [visit **discourse.org**](http://www.discourse.org).
|
||||
|
||||
## Configuration
|
||||
|
||||
Use the admin panel of your Discourse to configure this app.
|
||||
**Versión actual:** 2.8.14~ynh3
|
||||
|
||||
### Configuring "Reply-By-Email"
|
||||
**Demo:** <https://try.discourse.org>
|
||||
|
||||
* You should create a dedicated Yunohost user for Discourse whose mailbox will be used by the Discourse application. You can do this with `yunohost user create response`, for example. You should ensure that the email address is configured to be on your Discourse domain.
|
||||
## Capturas
|
||||
|
||||
* You should then configure your Discourse `/var/www/discourse/config/discourse.conf` file with the correct SMTP configuration values. Please see [this comment](https://github.com/YunoHost-Apps/discourse_ynh/issues/2#issuecomment-409510325) for an explanation of what values to change. Please be aware, when you update the application, you will have to re-apply this configuration.
|
||||
|
||||
* You must enable the Pop3 configuration for Dovecot. See [this thread](https://forum.yunohost.org/t/how-to-enable-pop3-in-yunohost/1662/2) on how to do that. You can validate your configuration with `systemctl restart dovecot && dovecot -n`. Don't forget to open the ports you need (`995` is the default). You can validate that with `nmap -p 995 yunohostdomain.org`.
|
||||
|
||||
* You should then configure the Pop3 polling in the Discourse admin interface. Please see [this comment](https://meta.discourse.org/t/set-up-reply-via-email-support/14003) for how to do so. You will need to follow step 5 in that comment. You can specify your main Yunohost domain for the `pop3_polling_host`.
|
||||
|
||||
You should now be able to start testing. Try using the `/admin/email` "Send Test Email" and then view the "Sent" or "Skipped" etc. tabs. You should see a report on what happened with the email. You may also want to look in `/var/www/discourse/log/production.log` as well as `/var/www/mail.err`. You should perhaps also use [Rainloop](https://github.com/YunoHost-Apps/rainloop_ynh) or another Yunohost email client application to quickly test that both your user and the dedicated Yunohost Discourse user (`response@...`) is receiving mail.
|
||||
|
||||
### "Reply-By-Email" and mail forwarding
|
||||
|
||||
If you use the administration UI in YunoHost to setup a mail forwarding address for your users then you may face the problem whereby your users are replying by email from the forwarded email address and the Discourse software is not able to understand how to receive that email.
|
||||
|
||||
For example, your user has email address `foo@myyunohostdomain.org` and all mail is forwarded to `foo@theirexternalmail.com`. Discourse receives replies from `foo@theirexternalmail.com` but cannot understand how to deliver this to the user account with `foo@myyunohostdomain.org` configured.
|
||||
|
||||
Their is on-going work to allow for [multiple email addresses for one user](https://meta.discourse.org/t/additional-email-address-per-user-account-support/59847) in Discourse development but at current major version (2.3 as of 2019-08-06), there is no web interface for this functionality. It is possible to set it up via the command-line interface but it is **experimental** and you should not undertake this work unless you take some time to understand what it is you are going to do.
|
||||
|
||||
Here's how to setup a secondary mail address for a user account:
|
||||
|
||||
```bash
|
||||
$ cd /var/www/discourse
|
||||
$ RAILS_ENV=production /opt/rbenv/versions/2.7.1/bin/bundle exec rails c
|
||||
$ UserEmail.create!(user: User.find_by_username("foo"), email: "foo@theirexternalmail.com")
|
||||
```
|
||||
|
||||
## YunoHost specific features
|
||||
|
||||
* Integration with YunoHost users and SSO:
|
||||
* LDAP integration: on the login pop-up, you can choose "Login with LDAP" and use your YunoHost credentials
|
||||
* private mode: Forum only accessible by YunoHost users
|
||||
* public mode: Visible by anyone
|
||||
|
||||
#### Multi-user support
|
||||
|
||||
Supported, with LDAP (no SSO).
|
||||
|
||||
|
||||
|
||||
Default administrator and YunoHost users must login using LDAP:
|
||||
* click on the "with LDAP" button
|
||||
* use your YunoHost credentials
|
||||
|
||||
When disabling Local Login and other authentication services, clicking the `Login` or `Sign Up` button will directly bring up the LDAP Login popup.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Limitations
|
||||
|
||||
None at the moment.
|
||||
|
||||
## Additional information
|
||||
### Known non-impacting log messages
|
||||
```
|
||||
fatal: Not a git repository (or any of the parent directories): .git
|
||||
|
||||
bash: BASH_XTRACEFD: 7: invalid value for trace file descriptor
|
||||
```
|
||||
## How-tos
|
||||
### Install plugins
|
||||
```
|
||||
cd /var/www/discourse
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace plugin:install repo=https://github.com/discourse/discourse-solved (for example)
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace assets:precompile
|
||||
systemctl restart discourse
|
||||
```
|
||||
|
||||
|
||||
## Documentaciones y recursos
|
||||
|
||||
|
|
|
|||
105
README_eu.md
105
README_eu.md
|
|
@ -16,37 +16,6 @@ EZ editatu eskuz.
|
|||
|
||||
## Aurreikuspena
|
||||
|
||||
Discourse is modern forum software for your community. Use it as a mailing list, discussion forum, long-form chat room, and more!
|
||||
|
||||
**Paketatutako bertsioa:** 2.8.14~ynh2
|
||||
|
||||
**Demoa:** <https://try.discourse.org>
|
||||
|
||||
## Pantaila-argazkiak
|
||||
|
||||
|
||||
|
||||
## Ezespena / informazio garrantzitsua
|
||||
|
||||
## Disclaimer
|
||||
|
||||
This package installs Discourse without Docker, for several reasons (mostly to support ARM architecture and low-profile servers, to mutualize nginx/postgresql/redis services and to simplify e-mail setup).
|
||||
As stated by the Discourse team:
|
||||
> The only officially supported installs of Discourse are [Docker](https://www.docker.io/) based. You must have SSH access to a 64-bit Linux server **with Docker support**. We regret that we cannot support any other methods of installation including cpanel, plesk, webmin, etc.
|
||||
|
||||
So please have this in mind when considering asking for Discourse support.
|
||||
|
||||
Moreover, you should have in mind Discourse [hardware requirements](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md#hardware-requirements):
|
||||
- modern single core CPU, dual core recommended
|
||||
- 1 GB RAM minimum (with swap)
|
||||
- 64 bit Linux compatible with Docker
|
||||
- 10 GB disk space minimum
|
||||
|
||||
Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
||||
- installation can last up to 3 hours,
|
||||
- first access right after installation could take a couple of minutes.
|
||||
|
||||
## Overview
|
||||
[Discourse](http://www.discourse.org) is the 100% open source discussion platform built for the next decade of the Internet. Use it as a:
|
||||
|
||||
- mailing list
|
||||
|
|
@ -55,80 +24,14 @@ Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
|||
|
||||
To learn more about the philosophy and goals of the project, [visit **discourse.org**](http://www.discourse.org).
|
||||
|
||||
## Configuration
|
||||
|
||||
Use the admin panel of your Discourse to configure this app.
|
||||
**Paketatutako bertsioa:** 2.8.14~ynh3
|
||||
|
||||
### Configuring "Reply-By-Email"
|
||||
**Demoa:** <https://try.discourse.org>
|
||||
|
||||
* You should create a dedicated Yunohost user for Discourse whose mailbox will be used by the Discourse application. You can do this with `yunohost user create response`, for example. You should ensure that the email address is configured to be on your Discourse domain.
|
||||
## Pantaila-argazkiak
|
||||
|
||||
* You should then configure your Discourse `/var/www/discourse/config/discourse.conf` file with the correct SMTP configuration values. Please see [this comment](https://github.com/YunoHost-Apps/discourse_ynh/issues/2#issuecomment-409510325) for an explanation of what values to change. Please be aware, when you update the application, you will have to re-apply this configuration.
|
||||
|
||||
* You must enable the Pop3 configuration for Dovecot. See [this thread](https://forum.yunohost.org/t/how-to-enable-pop3-in-yunohost/1662/2) on how to do that. You can validate your configuration with `systemctl restart dovecot && dovecot -n`. Don't forget to open the ports you need (`995` is the default). You can validate that with `nmap -p 995 yunohostdomain.org`.
|
||||
|
||||
* You should then configure the Pop3 polling in the Discourse admin interface. Please see [this comment](https://meta.discourse.org/t/set-up-reply-via-email-support/14003) for how to do so. You will need to follow step 5 in that comment. You can specify your main Yunohost domain for the `pop3_polling_host`.
|
||||
|
||||
You should now be able to start testing. Try using the `/admin/email` "Send Test Email" and then view the "Sent" or "Skipped" etc. tabs. You should see a report on what happened with the email. You may also want to look in `/var/www/discourse/log/production.log` as well as `/var/www/mail.err`. You should perhaps also use [Rainloop](https://github.com/YunoHost-Apps/rainloop_ynh) or another Yunohost email client application to quickly test that both your user and the dedicated Yunohost Discourse user (`response@...`) is receiving mail.
|
||||
|
||||
### "Reply-By-Email" and mail forwarding
|
||||
|
||||
If you use the administration UI in YunoHost to setup a mail forwarding address for your users then you may face the problem whereby your users are replying by email from the forwarded email address and the Discourse software is not able to understand how to receive that email.
|
||||
|
||||
For example, your user has email address `foo@myyunohostdomain.org` and all mail is forwarded to `foo@theirexternalmail.com`. Discourse receives replies from `foo@theirexternalmail.com` but cannot understand how to deliver this to the user account with `foo@myyunohostdomain.org` configured.
|
||||
|
||||
Their is on-going work to allow for [multiple email addresses for one user](https://meta.discourse.org/t/additional-email-address-per-user-account-support/59847) in Discourse development but at current major version (2.3 as of 2019-08-06), there is no web interface for this functionality. It is possible to set it up via the command-line interface but it is **experimental** and you should not undertake this work unless you take some time to understand what it is you are going to do.
|
||||
|
||||
Here's how to setup a secondary mail address for a user account:
|
||||
|
||||
```bash
|
||||
$ cd /var/www/discourse
|
||||
$ RAILS_ENV=production /opt/rbenv/versions/2.7.1/bin/bundle exec rails c
|
||||
$ UserEmail.create!(user: User.find_by_username("foo"), email: "foo@theirexternalmail.com")
|
||||
```
|
||||
|
||||
## YunoHost specific features
|
||||
|
||||
* Integration with YunoHost users and SSO:
|
||||
* LDAP integration: on the login pop-up, you can choose "Login with LDAP" and use your YunoHost credentials
|
||||
* private mode: Forum only accessible by YunoHost users
|
||||
* public mode: Visible by anyone
|
||||
|
||||
#### Multi-user support
|
||||
|
||||
Supported, with LDAP (no SSO).
|
||||
|
||||
|
||||
|
||||
Default administrator and YunoHost users must login using LDAP:
|
||||
* click on the "with LDAP" button
|
||||
* use your YunoHost credentials
|
||||
|
||||
When disabling Local Login and other authentication services, clicking the `Login` or `Sign Up` button will directly bring up the LDAP Login popup.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Limitations
|
||||
|
||||
None at the moment.
|
||||
|
||||
## Additional information
|
||||
### Known non-impacting log messages
|
||||
```
|
||||
fatal: Not a git repository (or any of the parent directories): .git
|
||||
|
||||
bash: BASH_XTRACEFD: 7: invalid value for trace file descriptor
|
||||
```
|
||||
## How-tos
|
||||
### Install plugins
|
||||
```
|
||||
cd /var/www/discourse
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace plugin:install repo=https://github.com/discourse/discourse-solved (for example)
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace assets:precompile
|
||||
systemctl restart discourse
|
||||
```
|
||||
|
||||
|
||||
## Dokumentazioa eta baliabideak
|
||||
|
||||
|
|
|
|||
178
README_fr.md
178
README_fr.md
|
|
@ -16,9 +16,16 @@ Il NE doit PAS être modifié à la main.
|
|||
|
||||
## Vue d’ensemble
|
||||
|
||||
Discourse est un logiciel de forum moderne pour votre communauté. Utilisez-le comme liste de diffusion, forum de discussion, salle de discussion longue durée, et plus encore !
|
||||
[Discourse](http://www.discourse.org) est la plate-forme de discussion 100% open source conçue pour la prochaine décennie d'Internet. Utilisez-le comme :
|
||||
|
||||
**Version incluse :** 2.8.14~ynh2
|
||||
- liste de diffusion
|
||||
- forum de discussion
|
||||
- salle de discussion longue durée
|
||||
|
||||
Pour en savoir plus sur la philosophie et les objectifs du projet, [visitez **discourse.org**](http://www.discourse.org).
|
||||
|
||||
|
||||
**Version incluse :** 2.8.14~ynh3
|
||||
|
||||
**Démo :** <https://try.discourse.org>
|
||||
|
||||
|
|
@ -26,173 +33,6 @@ Discourse est un logiciel de forum moderne pour votre communauté. Utilisez-le c
|
|||
|
||||
|
||||
|
||||
## Avertissements / informations importantes
|
||||
|
||||
## Avertissement
|
||||
|
||||
Ce package installe Discourse sans Docker, pour plusieurs raisons (principalement pour prendre en charge l'architecture ARM et les serveurs discrets, pour mutualiser les services nginx/postgresql/redis et pour simplifier la configuration de la messagerie).
|
||||
Comme indiqué par l'équipe Discourse :
|
||||
> Les seules installations officiellement prises en charge de Discourse sont basées sur [Docker](https://www.docker.io/). Vous devez avoir un accès SSH à un serveur Linux 64 bits **avec prise en charge Docker**. Nous regrettons de ne pouvoir prendre en charge aucune autre méthode d'installation, notamment cpanel, plesk, webmin, etc.
|
||||
|
||||
Veuillez donc avoir cela à l'esprit lorsque vous envisagez de demander de l'aide à Discourse.
|
||||
|
||||
De plus, vous devriez avoir à l'esprit Discourse [exigences matérielles](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md#hardware-requirements) :
|
||||
- CPU monocœur moderne, double cœur recommandé
|
||||
- 1 Go de RAM minimum (avec swap)
|
||||
- Linux 64 bits compatible avec Docker
|
||||
- 10 Go d'espace disque minimum
|
||||
|
||||
Enfin, si vous installez sur un appareil ARM bas de gamme (par exemple Raspberry Pi) :
|
||||
- l'installation peut durer jusqu'à 3 heures,
|
||||
- le premier accès juste après l'installation peut prendre quelques minutes.
|
||||
|
||||
## Aperçu
|
||||
[Discourse](http://www.discourse.org) est la plate-forme de discussion 100% open source conçue pour la prochaine décennie d'Internet. Utilisez-le comme :
|
||||
|
||||
- liste de diffusion
|
||||
- forum de discussion
|
||||
- salle de discussion longue durée
|
||||
|
||||
Pour en savoir plus sur la philosophie et les objectifs du projet, [visitez **discourse.org**](http://www.discourse.org).
|
||||
|
||||
## Configuration
|
||||
|
||||
Utilisez le panneau d'administration de votre Discourse pour configurer cette application.
|
||||
|
||||
### Configuration de "Répondre par e-mail"
|
||||
|
||||
* Vous devez créer un utilisateur Yunohost dédié pour Discourse dont la boîte aux lettres sera utilisée par l'application Discourse. Vous pouvez le faire avec `yunohost user create response`, par exemple. Vous devez vous assurer que l'adresse e-mail est configurée pour être sur votre domaine Discourse.
|
||||
|
||||
* Vous devez ensuite configurer votre fichier Discourse `/var/www/discourse/config/discourse.conf` avec les valeurs de configuration SMTP correctes. Veuillez consulter [ce commentaire](https://github.com/YunoHost-Apps/discourse_ynh/issues/2#issuecomment-409510325) pour une explication des valeurs à modifier. Attention, lors de la mise à jour de l'application, vous devrez réappliquer cette configuration.
|
||||
|
||||
* Vous devez activer la configuration Pop3 pour Dovecot. Voir [ce fil](https://forum.yunohost.org/t/how-to-enable-pop3-in-yunohost/1662/2) pour savoir comment procéder. Vous pouvez valider votre configuration avec `systemctl restart dovecot && dovecot -n`. N'oubliez pas d'ouvrir les ports dont vous avez besoin ('995' est la valeur par défaut). Vous pouvez valider cela avec `nmap -p 995 yunohostdomain.org`.
|
||||
|
||||
* Vous devez ensuite configurer le sondage Pop3 dans l'interface d'administration de Discourse. Veuillez consulter [ce commentaire](https://meta.discourse.org/t/set-up-reply-via-email-support/14003) pour savoir comment procéder. Vous devrez suivre l'étape 5 de ce commentaire. Vous pouvez spécifier votre domaine Yunohost principal pour le `pop3_polling_host`.
|
||||
|
||||
Vous devriez maintenant pouvoir commencer à tester. Essayez d'utiliser le `/admin/email` « Envoyer un e-mail de test », puis affichez les onglets « Envoyé » ou « Ignoré », etc. Vous devriez voir un rapport sur ce qui s'est passé avec l'e-mail. Vous pouvez également regarder dans `/var/www/discourse/log/production.log` ainsi que `/var/www/mail.err`. Vous devriez peut-être également utiliser [Rainloop](https://github.com/YunoHost-Apps/rainloop_ynh) ou une autre application client de messagerie Yunohost pour tester rapidement que votre utilisateur et l'utilisateur dédié Yunohost Discourse (`response@...` ) reçoit du courrier.
|
||||
|
||||
### "Réponse par e-mail" et transfert de courrier
|
||||
|
||||
Si vous utilisez l'interface utilisateur d'administration de YunoHost pour configurer une adresse de transfert de courrier pour vos utilisateurs, vous risquez de rencontrer le problème selon lequel vos utilisateurs répondent par e-mail à partir de l'adresse e-mail transférée et le logiciel Discourse n'est pas capable de comprendre comment recevoir cet e-mail.
|
||||
|
||||
Par exemple, votre utilisateur a l'adresse e-mail "foo@myyunohostdomain.org" et tout le courrier est transféré à "foo@theirexternalmail.com". Discourse reçoit des réponses de `foo@theirexternalmail.com` mais ne peut pas comprendre comment les envoyer au compte utilisateur avec `foo@myyunohostdomain.org` configuré.
|
||||
|
||||
Leur travail est en cours pour permettre [plusieurs adresses e-mail pour un utilisateur](https://meta.discourse.org/t/additional-email-address-per-user-account-support/59847) dans le développement de discours mais dans la version majeure actuelle (2.3 au 06-08-2019), il n'y a pas d'interface Web pour cette fonctionnalité. Il est possible de le configurer via l'interface de ligne de commande mais c'est **expérimental** et vous ne devriez pas entreprendre ce travail à moins de prendre le temps de comprendre ce que vous allez faire.
|
||||
|
||||
Voici comment configurer une adresse e-mail secondaire pour un compte utilisateur :
|
||||
|
||||
```bash
|
||||
$ cd /var/www/discours
|
||||
$ RAILS_ENV=production /opt/rbenv/versions/2.6.0/bin/bundle exec rails c
|
||||
$ UserEmail.create!(user: User.find_by_username("foo"), email: "foo@theirexternalmail.com")
|
||||
```
|
||||
|
||||
## Fonctionnalités spécifiques à YunoHost
|
||||
|
||||
* Intégration avec les utilisateurs YunoHost et SSO :
|
||||
* Intégration LDAP : dans la pop-up de connexion, vous pouvez choisir "Se connecter avec LDAP" et utiliser vos identifiants YunoHost
|
||||
* mode privé : Forum uniquement accessible ## Disclaimer
|
||||
|
||||
Ce package installe Discourse sans Docker, pour plusieurs raisons (principalement pour prendre en charge l'architecture ARM et les serveurs discrets, pour mutualiser les services nginx/postgresql/redis et pour simplifier la configuration de la messagerie).
|
||||
Comme indiqué par l'équipe Discourse :
|
||||
> Les seules installations officiellement prises en charge de Discourse sont basées sur [Docker](https://www.docker.io/). Vous devez avoir un accès SSH à un serveur Linux 64 bits **avec prise en charge Docker**. Nous regrettons de ne pouvoir prendre en charge aucune autre méthode d'installation, notamment cpanel, plesk, webmin, etc.
|
||||
|
||||
Veuillez donc avoir cela à l'esprit lorsque vous envisagez de demander de l'aide à Discourse.
|
||||
|
||||
De plus, vous devriez avoir à l'esprit Discourse [exigences matérielles](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md#hardware-requirements) :
|
||||
- CPU monocœur moderne, double cœur recommandé
|
||||
- 1 Go de RAM minimum (avec swap)
|
||||
- Linux 64 bits compatible avec Docker
|
||||
- 10 Go d'espace disque minimum
|
||||
|
||||
Enfin, si vous installez sur un appareil ARM bas de gamme (par exemple Raspberry Pi) :
|
||||
- l'installation peut durer jusqu'à 3 heures,
|
||||
- le premier accès juste après l'installation peut prendre quelques minutes.
|
||||
|
||||
## Aperçu
|
||||
[Discourse](http://www.discourse.org) est la plate-forme de discussion 100% open source conçue pour la prochaine décennie d'Internet. Utilisez-le comme :
|
||||
|
||||
- liste de diffusion
|
||||
- forum de discussion
|
||||
- salle de discussion longue durée
|
||||
|
||||
Pour en savoir plus sur la philosophie et les objectifs du projet, [visitez **discourse.org**](http://www.discourse.org).
|
||||
|
||||
## Configuration
|
||||
|
||||
Utilisez le panneau d'administration de votre Discourse pour configurer cette application.
|
||||
|
||||
### Configuration de "Répondre par e-mail"
|
||||
|
||||
* Vous devez créer un utilisateur Yunohost dédié pour Discourse dont la boîte aux lettres sera utilisée par l'application Discourse. Vous pouvez le faire avec `yunohost user create response`, par exemple. Vous devez vous assurer que l'adresse e-mail est configurée pour être sur votre domaine Discourse.
|
||||
|
||||
* Vous devez ensuite configurer votre fichier Discourse `/var/www/discourse/config/discourse.conf` avec les valeurs de configuration SMTP correctes. Veuillez consulter [ce commentaire](https://github.com/YunoHost-Apps/discourse_ynh/issues/2#issuecomment-409510325) pour une explication des valeurs à modifier. Attention, lors de la mise à jour de l'application, vous devrez réappliquer cette configuration.
|
||||
|
||||
* Vous devez activer la configuration Pop3 pour Dovecot. Voir [ce fil](https://forum.yunohost.org/t/how-to-enable-pop3-in-yunohost/1662/2) pour savoir comment procéder. Vous pouvez valider votre configuration avec `systemctl restart dovecot && dovecot -n`. N'oubliez pas d'ouvrir les ports dont vous avez besoin ('995' est la valeur par défaut). Vous pouvez valider cela avec `nmap -p 995 yunohostdomain.org`.
|
||||
|
||||
* Vous devez ensuite configurer le sondage Pop3 dans l'interface d'administration de Discourse. Veuillez consulter [ce commentaire](https://meta.discourse.org/t/set-up-reply-via-email-support/14003) pour savoir comment procéder. Vous devrez suivre l'étape 5 de ce commentaire. Vous pouvez spécifier votre domaine Yunohost principal pour le `pop3_polling_host`.
|
||||
|
||||
Vous devriez maintenant pouvoir commencer à tester. Essayez d'utiliser le `/admin/email` « Envoyer un e-mail de test », puis affichez les onglets « Envoyé » ou « Ignoré », etc. Vous devriez voir un rapport sur ce qui s'est passé avec l'e-mail. Vous pouvez également regarder dans `/var/www/discourse/log/production.log` ainsi que `/var/www/mail.err`. Vous devriez peut-être également utiliser [Rainloop](https://github.com/YunoHost-Apps/rainloop_ynh) ou une autre application client de messagerie Yunohost pour tester rapidement que votre utilisateur et l'utilisateur dédié Yunohost Discourse (`response@...` ) reçoit du courrier.
|
||||
|
||||
### "Réponse par e-mail" et transfert de courrier
|
||||
|
||||
Si vous utilisez l'interface utilisateur d'administration de YunoHost pour configurer une adresse de transfert de courrier pour vos utilisateurs, vous risquez de rencontrer le problème selon lequel vos utilisateurs répondent par e-mail à partir de l'adresse e-mail transférée et le logiciel Discourse n'est pas capable de comprendre comment recevoir cet e-mail.
|
||||
|
||||
Par exemple, votre utilisateur a l'adresse e-mail "foo@myyunohostdomain.org" et tout le courrier est transféré à "foo@theirexternalmail.com". Discourse reçoit des réponses de `foo@theirexternalmail.com` mais ne peut pas comprendre comment les envoyer au compte utilisateur avec `foo@myyunohostdomain.org` configuré.
|
||||
|
||||
Leur travail est en cours pour permettre [plusieurs adresses e-mail pour un utilisateur](https://meta.discourse.org/t/additional-email-address-per-user-account-support/59847) dans le développement de discours mais dans la version majeure actuelle (2.3 au 06-08-2019), il n'y a pas d'interface Web pour cette fonctionnalité. Il est possible de le configurer via l'interface de ligne de commande mais c'est **expérimental** et vous ne devriez pas entreprendre ce travail à moins de prendre le temps de comprendre ce que vous allez faire.
|
||||
|
||||
Voici comment configurer une adresse e-mail secondaire pour un compte utilisateur :
|
||||
|
||||
```bash
|
||||
$ cd /var/www/discourse
|
||||
$ RAILS_ENV=production /opt/rbenv/versions/2.7.1/bin/bundle exec rails c
|
||||
$ UserEmail.create!(user: User.find_by_username("foo"), email: "foo@theirexternalmail.com")
|
||||
```
|
||||
|
||||
## Fonctionnalités spécifiques à YunoHost
|
||||
|
||||
* Intégration avec les utilisateurs YunoHost et SSO :
|
||||
* Intégration LDAP : dans la pop-up de connexion, vous pouvez choisir "Se connecter avec LDAP" et utiliser vos identifiants YunoHost
|
||||
* mode privé : Forum accessible uniquement par les utilisateurs de YunoHost
|
||||
* mode public : Visible par tous
|
||||
|
||||
#### Prise en charge multi-utilisateurs
|
||||
|
||||
Pris en charge, avec LDAP (pas de SSO).
|
||||
|
||||
|
||||
|
||||
L'administrateur par défaut et les utilisateurs YunoHost doivent se connecter via LDAP :
|
||||
* cliquez sur le bouton "avec LDAP"
|
||||
* utilisez vos identifiants YunoHost
|
||||
|
||||
Lors de la désactivation de la connexion locale et d'autres services d'authentification, cliquez sur le bouton « Connexion » ou « Inscription » pour afficher directement la fenêtre contextuelle de connexion LDAP.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Limites
|
||||
|
||||
Aucun pour le moment.
|
||||
|
||||
## Informations Complémentaires
|
||||
### Messages de journal connus sans impact
|
||||
```
|
||||
fatal: Not a git repository (or any of the parent directories): .git
|
||||
|
||||
bash: BASH_XTRACEFD: 7: invalid value for trace file descriptor
|
||||
```
|
||||
## Mode d'emploi
|
||||
### Installer des plugins
|
||||
```
|
||||
cd /var/www/discourse
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace plugin:install repo=https://github.com/discourse/discourse-solved (for example)
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace assets:precompile
|
||||
systemctl restart discourse
|
||||
```
|
||||
|
||||
## Documentations et ressources
|
||||
|
||||
- Site officiel de l’app : <http://Discourse.org>
|
||||
|
|
|
|||
105
README_gl.md
105
README_gl.md
|
|
@ -16,37 +16,6 @@ NON debe editarse manualmente.
|
|||
|
||||
## Vista xeral
|
||||
|
||||
Discourse is modern forum software for your community. Use it as a mailing list, discussion forum, long-form chat room, and more!
|
||||
|
||||
**Versión proporcionada:** 2.8.14~ynh2
|
||||
|
||||
**Demo:** <https://try.discourse.org>
|
||||
|
||||
## Capturas de pantalla
|
||||
|
||||
|
||||
|
||||
## Avisos / información importante
|
||||
|
||||
## Disclaimer
|
||||
|
||||
This package installs Discourse without Docker, for several reasons (mostly to support ARM architecture and low-profile servers, to mutualize nginx/postgresql/redis services and to simplify e-mail setup).
|
||||
As stated by the Discourse team:
|
||||
> The only officially supported installs of Discourse are [Docker](https://www.docker.io/) based. You must have SSH access to a 64-bit Linux server **with Docker support**. We regret that we cannot support any other methods of installation including cpanel, plesk, webmin, etc.
|
||||
|
||||
So please have this in mind when considering asking for Discourse support.
|
||||
|
||||
Moreover, you should have in mind Discourse [hardware requirements](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md#hardware-requirements):
|
||||
- modern single core CPU, dual core recommended
|
||||
- 1 GB RAM minimum (with swap)
|
||||
- 64 bit Linux compatible with Docker
|
||||
- 10 GB disk space minimum
|
||||
|
||||
Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
||||
- installation can last up to 3 hours,
|
||||
- first access right after installation could take a couple of minutes.
|
||||
|
||||
## Overview
|
||||
[Discourse](http://www.discourse.org) is the 100% open source discussion platform built for the next decade of the Internet. Use it as a:
|
||||
|
||||
- mailing list
|
||||
|
|
@ -55,80 +24,14 @@ Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
|||
|
||||
To learn more about the philosophy and goals of the project, [visit **discourse.org**](http://www.discourse.org).
|
||||
|
||||
## Configuration
|
||||
|
||||
Use the admin panel of your Discourse to configure this app.
|
||||
**Versión proporcionada:** 2.8.14~ynh3
|
||||
|
||||
### Configuring "Reply-By-Email"
|
||||
**Demo:** <https://try.discourse.org>
|
||||
|
||||
* You should create a dedicated Yunohost user for Discourse whose mailbox will be used by the Discourse application. You can do this with `yunohost user create response`, for example. You should ensure that the email address is configured to be on your Discourse domain.
|
||||
## Capturas de pantalla
|
||||
|
||||
* You should then configure your Discourse `/var/www/discourse/config/discourse.conf` file with the correct SMTP configuration values. Please see [this comment](https://github.com/YunoHost-Apps/discourse_ynh/issues/2#issuecomment-409510325) for an explanation of what values to change. Please be aware, when you update the application, you will have to re-apply this configuration.
|
||||
|
||||
* You must enable the Pop3 configuration for Dovecot. See [this thread](https://forum.yunohost.org/t/how-to-enable-pop3-in-yunohost/1662/2) on how to do that. You can validate your configuration with `systemctl restart dovecot && dovecot -n`. Don't forget to open the ports you need (`995` is the default). You can validate that with `nmap -p 995 yunohostdomain.org`.
|
||||
|
||||
* You should then configure the Pop3 polling in the Discourse admin interface. Please see [this comment](https://meta.discourse.org/t/set-up-reply-via-email-support/14003) for how to do so. You will need to follow step 5 in that comment. You can specify your main Yunohost domain for the `pop3_polling_host`.
|
||||
|
||||
You should now be able to start testing. Try using the `/admin/email` "Send Test Email" and then view the "Sent" or "Skipped" etc. tabs. You should see a report on what happened with the email. You may also want to look in `/var/www/discourse/log/production.log` as well as `/var/www/mail.err`. You should perhaps also use [Rainloop](https://github.com/YunoHost-Apps/rainloop_ynh) or another Yunohost email client application to quickly test that both your user and the dedicated Yunohost Discourse user (`response@...`) is receiving mail.
|
||||
|
||||
### "Reply-By-Email" and mail forwarding
|
||||
|
||||
If you use the administration UI in YunoHost to setup a mail forwarding address for your users then you may face the problem whereby your users are replying by email from the forwarded email address and the Discourse software is not able to understand how to receive that email.
|
||||
|
||||
For example, your user has email address `foo@myyunohostdomain.org` and all mail is forwarded to `foo@theirexternalmail.com`. Discourse receives replies from `foo@theirexternalmail.com` but cannot understand how to deliver this to the user account with `foo@myyunohostdomain.org` configured.
|
||||
|
||||
Their is on-going work to allow for [multiple email addresses for one user](https://meta.discourse.org/t/additional-email-address-per-user-account-support/59847) in Discourse development but at current major version (2.3 as of 2019-08-06), there is no web interface for this functionality. It is possible to set it up via the command-line interface but it is **experimental** and you should not undertake this work unless you take some time to understand what it is you are going to do.
|
||||
|
||||
Here's how to setup a secondary mail address for a user account:
|
||||
|
||||
```bash
|
||||
$ cd /var/www/discourse
|
||||
$ RAILS_ENV=production /opt/rbenv/versions/2.7.1/bin/bundle exec rails c
|
||||
$ UserEmail.create!(user: User.find_by_username("foo"), email: "foo@theirexternalmail.com")
|
||||
```
|
||||
|
||||
## YunoHost specific features
|
||||
|
||||
* Integration with YunoHost users and SSO:
|
||||
* LDAP integration: on the login pop-up, you can choose "Login with LDAP" and use your YunoHost credentials
|
||||
* private mode: Forum only accessible by YunoHost users
|
||||
* public mode: Visible by anyone
|
||||
|
||||
#### Multi-user support
|
||||
|
||||
Supported, with LDAP (no SSO).
|
||||
|
||||
|
||||
|
||||
Default administrator and YunoHost users must login using LDAP:
|
||||
* click on the "with LDAP" button
|
||||
* use your YunoHost credentials
|
||||
|
||||
When disabling Local Login and other authentication services, clicking the `Login` or `Sign Up` button will directly bring up the LDAP Login popup.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Limitations
|
||||
|
||||
None at the moment.
|
||||
|
||||
## Additional information
|
||||
### Known non-impacting log messages
|
||||
```
|
||||
fatal: Not a git repository (or any of the parent directories): .git
|
||||
|
||||
bash: BASH_XTRACEFD: 7: invalid value for trace file descriptor
|
||||
```
|
||||
## How-tos
|
||||
### Install plugins
|
||||
```
|
||||
cd /var/www/discourse
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace plugin:install repo=https://github.com/discourse/discourse-solved (for example)
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace assets:precompile
|
||||
systemctl restart discourse
|
||||
```
|
||||
|
||||
|
||||
## Documentación e recursos
|
||||
|
||||
|
|
|
|||
|
|
@ -16,37 +16,6 @@
|
|||
|
||||
## 概况
|
||||
|
||||
Discourse is modern forum software for your community. Use it as a mailing list, discussion forum, long-form chat room, and more!
|
||||
|
||||
**分发版本：** 2.8.14~ynh2
|
||||
|
||||
**演示：** <https://try.discourse.org>
|
||||
|
||||
## 截图
|
||||
|
||||
|
||||
|
||||
## 免责声明 / 重要信息
|
||||
|
||||
## Disclaimer
|
||||
|
||||
This package installs Discourse without Docker, for several reasons (mostly to support ARM architecture and low-profile servers, to mutualize nginx/postgresql/redis services and to simplify e-mail setup).
|
||||
As stated by the Discourse team:
|
||||
> The only officially supported installs of Discourse are [Docker](https://www.docker.io/) based. You must have SSH access to a 64-bit Linux server **with Docker support**. We regret that we cannot support any other methods of installation including cpanel, plesk, webmin, etc.
|
||||
|
||||
So please have this in mind when considering asking for Discourse support.
|
||||
|
||||
Moreover, you should have in mind Discourse [hardware requirements](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md#hardware-requirements):
|
||||
- modern single core CPU, dual core recommended
|
||||
- 1 GB RAM minimum (with swap)
|
||||
- 64 bit Linux compatible with Docker
|
||||
- 10 GB disk space minimum
|
||||
|
||||
Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
||||
- installation can last up to 3 hours,
|
||||
- first access right after installation could take a couple of minutes.
|
||||
|
||||
## Overview
|
||||
[Discourse](http://www.discourse.org) is the 100% open source discussion platform built for the next decade of the Internet. Use it as a:
|
||||
|
||||
- mailing list
|
||||
|
|
@ -55,80 +24,14 @@ Finally, if installing on a low-end ARM device (e.g. Raspberry Pi):
|
|||
|
||||
To learn more about the philosophy and goals of the project, [visit **discourse.org**](http://www.discourse.org).
|
||||
|
||||
## Configuration
|
||||
|
||||
Use the admin panel of your Discourse to configure this app.
|
||||
**分发版本：** 2.8.14~ynh3
|
||||
|
||||
### Configuring "Reply-By-Email"
|
||||
**演示：** <https://try.discourse.org>
|
||||
|
||||
* You should create a dedicated Yunohost user for Discourse whose mailbox will be used by the Discourse application. You can do this with `yunohost user create response`, for example. You should ensure that the email address is configured to be on your Discourse domain.
|
||||
## 截图
|
||||
|
||||
* You should then configure your Discourse `/var/www/discourse/config/discourse.conf` file with the correct SMTP configuration values. Please see [this comment](https://github.com/YunoHost-Apps/discourse_ynh/issues/2#issuecomment-409510325) for an explanation of what values to change. Please be aware, when you update the application, you will have to re-apply this configuration.
|
||||
|
||||
* You must enable the Pop3 configuration for Dovecot. See [this thread](https://forum.yunohost.org/t/how-to-enable-pop3-in-yunohost/1662/2) on how to do that. You can validate your configuration with `systemctl restart dovecot && dovecot -n`. Don't forget to open the ports you need (`995` is the default). You can validate that with `nmap -p 995 yunohostdomain.org`.
|
||||
|
||||
* You should then configure the Pop3 polling in the Discourse admin interface. Please see [this comment](https://meta.discourse.org/t/set-up-reply-via-email-support/14003) for how to do so. You will need to follow step 5 in that comment. You can specify your main Yunohost domain for the `pop3_polling_host`.
|
||||
|
||||
You should now be able to start testing. Try using the `/admin/email` "Send Test Email" and then view the "Sent" or "Skipped" etc. tabs. You should see a report on what happened with the email. You may also want to look in `/var/www/discourse/log/production.log` as well as `/var/www/mail.err`. You should perhaps also use [Rainloop](https://github.com/YunoHost-Apps/rainloop_ynh) or another Yunohost email client application to quickly test that both your user and the dedicated Yunohost Discourse user (`response@...`) is receiving mail.
|
||||
|
||||
### "Reply-By-Email" and mail forwarding
|
||||
|
||||
If you use the administration UI in YunoHost to setup a mail forwarding address for your users then you may face the problem whereby your users are replying by email from the forwarded email address and the Discourse software is not able to understand how to receive that email.
|
||||
|
||||
For example, your user has email address `foo@myyunohostdomain.org` and all mail is forwarded to `foo@theirexternalmail.com`. Discourse receives replies from `foo@theirexternalmail.com` but cannot understand how to deliver this to the user account with `foo@myyunohostdomain.org` configured.
|
||||
|
||||
Their is on-going work to allow for [multiple email addresses for one user](https://meta.discourse.org/t/additional-email-address-per-user-account-support/59847) in Discourse development but at current major version (2.3 as of 2019-08-06), there is no web interface for this functionality. It is possible to set it up via the command-line interface but it is **experimental** and you should not undertake this work unless you take some time to understand what it is you are going to do.
|
||||
|
||||
Here's how to setup a secondary mail address for a user account:
|
||||
|
||||
```bash
|
||||
$ cd /var/www/discourse
|
||||
$ RAILS_ENV=production /opt/rbenv/versions/2.7.1/bin/bundle exec rails c
|
||||
$ UserEmail.create!(user: User.find_by_username("foo"), email: "foo@theirexternalmail.com")
|
||||
```
|
||||
|
||||
## YunoHost specific features
|
||||
|
||||
* Integration with YunoHost users and SSO:
|
||||
* LDAP integration: on the login pop-up, you can choose "Login with LDAP" and use your YunoHost credentials
|
||||
* private mode: Forum only accessible by YunoHost users
|
||||
* public mode: Visible by anyone
|
||||
|
||||
#### Multi-user support
|
||||
|
||||
Supported, with LDAP (no SSO).
|
||||
|
||||
|
||||
|
||||
Default administrator and YunoHost users must login using LDAP:
|
||||
* click on the "with LDAP" button
|
||||
* use your YunoHost credentials
|
||||
|
||||
When disabling Local Login and other authentication services, clicking the `Login` or `Sign Up` button will directly bring up the LDAP Login popup.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Limitations
|
||||
|
||||
None at the moment.
|
||||
|
||||
## Additional information
|
||||
### Known non-impacting log messages
|
||||
```
|
||||
fatal: Not a git repository (or any of the parent directories): .git
|
||||
|
||||
bash: BASH_XTRACEFD: 7: invalid value for trace file descriptor
|
||||
```
|
||||
## How-tos
|
||||
### Install plugins
|
||||
```
|
||||
cd /var/www/discourse
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace plugin:install repo=https://github.com/discourse/discourse-solved (for example)
|
||||
sudo -i -u discourse RAILS_ENV=production bin/rake --trace assets:precompile
|
||||
systemctl restart discourse
|
||||
```
|
||||
|
||||
|
||||
## 文档与资源
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue