discourse

Inofficial User Guide

von Ben Hest, https://forum.digikey.com/t/an-unofficial-discourse-user-reference-guide/

This is a “quick” how-to guide for using Discourse 27 forum/community software. It contains a majority of the common features avialble to users/content editors, but may not have complete coverage of the featureset. If anyone sees anything to add or correct, feel free to comment. If you’d like to learn more about the Discourse Editor’s syntax take a look at the commonmark 30 (a flavor of markdown) docs for more info.

Operations

forum.netzwissen.de läuft mit separaten Containern für Datenbank und Web. Siehe https://meta.discourse.org/t/how-to-move-from-standalone-container-to-separate-web-and-data-containers/29413 Entsprechend gibt es separate *.yml Konfigurationen für den Daten-Container und den Web-Container.

root@develd:/var/discourse/containers# ls -la
total 28
drwxr-xr-x  2 root root 4096 Aug 20 10:11 .
drwxr-xr-x 12 root root 4096 Apr 30 05:37 ..
-rw-r--r--  1 root root 4637 Nov 11  2020 app.yml.inactive
-rw-r--r--  1 root root 1124 Nov 11  2020 data.yml
-rw-r--r--  1 root root    0 Nov 11  2020 .gitkeep
-rw-r--r--  1 root root 5059 Aug 20 10:11 web_only.yml
root@develd:/var/discourse# ./launcher 
Usage: launcher COMMAND CONFIG [--skip-prereqs] [--docker-args STRING]
Commands:
    start:       Start/initialize a container
    stop:        Stop a running container
    restart:     Restart a container
    destroy:     Stop and remove a container
    enter:       Open a shell to run commands inside the container
    logs:        View the Docker logs for a container
    bootstrap:   Bootstrap a container for the config based on a template
    run:         Run the given command with the config in the context of the last bootstrapped image
    rebuild:     Rebuild a container (destroy old, bootstrap, start new)
    cleanup:     Remove all containers that have stopped for > 24 hours
    start-cmd:   Generate docker command used to start container

Options:
    --skip-prereqs             Don't check launcher prerequisites
    --docker-args              Extra arguments to pass when running docker
    --skip-mac-address         Don't assign a mac address
    --run-image                Override the image used for running the container

Logs

/var/discourse/shared/standalone/log/

Allgemeine Debug info

/var/discourse/discourse-doctor

Found containers/app.yml

==================== YML SETTINGS ====================
DISCOURSE_HOSTNAME=forum.netzwissen.de
SMTP_ADDRESS=mail.netzwissen.de
DEVELOPER_EMAILS=REDACTED
SMTP_PASSWORD=REDACTED
SMTP_PORT=587
SMTP_USER_NAME=noreply-discourse@netzwissen.de
LETSENCRYPT_ACCOUNT_EMAIL=REDACTED

==================== DOCKER INFO ====================
DOCKER VERSION: Docker version 19.03.8, build afacb8b7f0

DOCKER PROCESSES (docker ps -a)

CONTAINER ID        IMAGE                 COMMAND                  CREATED             STATUS                    PORTS                   NAMES
7333f3210491        local_discourse/app   "/sbin/boot"             16 hours ago        Up 16 hours               127.0.0.1:884->80/tcp   app
539c78cffb6a        0dbf6b4c454b          "docker-entrypoint.s…"   5 weeks ago         Exited (0) 17 hours ago                           zammad-docker-compose_zammad-memcached_1

Discourse container app is running

=========== Upgrade ==========

<code>
./launcher stop web_only && ./launcher rebuild data && ./launcher rebuild web_only

plugins

Discourse version at forum.netzwissen.de: Discourse 2.5.0.beta4 Discourse version at localhost: NOT FOUND

DNS PROBLEM

This server reports NOT FOUND, but forum.netzwissen.de reports Discourse 2.5.0.beta4 . This suggests that you have a DNS problem or that an intermediate proxy is to blame. If you are using Cloudflare, or a CDN, it may be improperly configured.

MEMORY INFORMATION

OS: Linux RAM (MB): 4038

            total        used        free      shared  buff/cache   available

Mem: 3944 2781 152 106 1010 786 Swap: 2047 533 1514

DISK SPACE CHECK

———- OS Disk Space ———- Filesystem Size Used Avail Use% Mounted on /dev/sda2 32G 23G 7,3G 76% /

DISK INFORMATION

Disk /dev/loop0: 93,9 MiB, 98484224 bytes, 192352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 93,8 MiB, 98336768 bytes, 192064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sda: 32 GiB, 34359738368 bytes, 67108864 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 9D35B183-C931-43A4-88DD-659ED1FAA7EE

Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 67106815 67102720 32G Linux filesystem

Disk /dev/sdb: 64 GiB, 68719476736 bytes, 134217728 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A21695AA-E44F-4FA6-9DA0-FAAD967CC8F7

Device Start End Sectors Size Type /dev/sdb1 2048 134215679 134213632 64G Linux filesystem

END DISK INFORMATION

MAIL TEST

For a robust test, get an address from http://www.mail-tester.com/ Sending mail to REDACTED . . Testing sending to admin@netzwissen.de using mail.netzwissen.de:587. SMTP server connection successful. Sending to admin@netzwissen.de. . . Mail accepted by SMTP server.

If you do not receive the message, check your SPAM folder or test again using a service like http://www.mail-tester.com/.

If the message is not delivered it is not a problem with Discourse.

Check the SMTP server logs to see why it failed to deliver the message.

DONE!

The output of this program may be available at http://forum.netzwissen.de/ZDAyMGU5MzhkZjcxYjM5.txt You should inspect that file carefully before sharing the URL.

</code>

Plugin Installation

Maintenance

- One CPU and 1GB of memory, with swap, is the minimum for a basic Discourse community. As your community grows you may need more memory or CPU resources.

- [Our Docker container install](https://github.com/discourse/discourse/blob/master/docs/INSTALL.md) is the only one we officially support. It guarantees easy updates, and all recommended optimizations from the Discourse team.

- You should get an email notification when new versions of Discourse are released. To update your instance via our easy one click upgrade process, visit [/admin/upgrade](/admin/upgrade).

- Some other things you might eventually want to set up:

  1. [Multiple Discourse instances on the same server](https://meta.discourse.org/t/multisite-configuration-with-docker/14084)
  2. [Import old content from vBulletin, PHPbb, Vanilla, Drupal, BBPress, etc](https://github.com/discourse/discourse/tree/master/script/import_scripts)
  3. A firewall on your server? [Configure firewall](https://meta.discourse.org/t/configure-a-firewall-for-discourse/20584).
  4. A user friendly [offline page when rebuilding or upgrading?](https://meta.discourse.org/t/adding-an-offline-page-when-rebuilding/45238)
cd /var/discourse git pull ./launcher rebuild app

User Operations

Mass invite

  1. One user per line.
  2. Email is required in the first column, and the email must be valid.
  3. Any permissions groups you want this user to be a member of should be in second column. For multiple groups, separate group names with a semicolon group_1;group_2;group_3
  4. Normally invited users arrive at the homepage. If you would rather invited users end up on a specific topic, enter that Topic ID in the third column.

name@example.com,group_1;group_2,topic_id

Statistics

Zutritt zum COntainer

docker exec -it e6fe156e2091 /bin/bash
  • discourse.txt
  • Zuletzt geändert: vor 8 Monaten
  • von thommie4