grouprise issueshttps://git.hack-hro.de/grouprise/grouprise/-/issues2024-01-26T17:55:51+01:00https://git.hack-hro.de/grouprise/grouprise/-/issues/806matrix: rooms for groups need to be specified as "room ID" (not "room alias")2024-01-26T17:55:51+01:00Lars Krusematrix: rooms for groups need to be specified as "room ID" (not "room alias")Currently the descriptions for the "private matrix room" and "public matrix room" group settings explicitly state, that room aliases (starting with "#") are allowed.
But in fact the implementation requires a room ID (starting with "!")....Currently the descriptions for the "private matrix room" and "public matrix room" group settings explicitly state, that room aliases (starting with "#") are allowed.
But in fact the implementation requires a room ID (starting with "!").
Using a room alias leads to the loss of notification messages (and any other room interactions), since room aliases are not resolved.https://git.hack-hro.de/grouprise/grouprise/-/issues/738Visualize content structure in database2021-11-24T11:02:12+01:00Lars KruseVisualize content structure in databaseCurrently it is hard to comprehend the meaning of the various involved database objects (contributions, associations, content).
We should document or visualize this somehow in order to ease development.Currently it is hard to comprehend the meaning of the various involved database objects (contributions, associations, content).
We should document or visualize this somehow in order to ease development.https://git.hack-hro.de/grouprise/grouprise/-/issues/717doc: Missing points during deb deployment2021-07-16T05:03:35+02:00Robertdoc: Missing points during deb deploymentThe documentation didn't handle the following points, which came up during a deployment:
1. After setting up the database, one has to execute the migrations.
1. One has to change/ set the `ALLOWED_HOSTS` setting.
1. The problem with the...The documentation didn't handle the following points, which came up during a deployment:
1. After setting up the database, one has to execute the migrations.
1. One has to change/ set the `ALLOWED_HOSTS` setting.
1. The problem with the locales and the calendar remains (#706). The calendar refused to render with locale `en_US.UTF-8`. I had to `dpkg-reconfigure locales` and setting `de_DE.UTF-8` as a default locale.https://git.hack-hro.de/grouprise/grouprise/-/issues/714Include user documentation2021-05-18T03:53:58+02:00Lars KruseInclude user documentationCurrently grouprise does not include user-oriented manuals or guides.
The workaround currently used in some communities is to provide a manually copied set of articles (e.g. https://stadtgestalten.org/stadt/help/ or https://stadtgestalt...Currently grouprise does not include user-oriented manuals or guides.
The workaround currently used in some communities is to provide a manually copied set of articles (e.g. https://stadtgestalten.org/stadt/help/ or https://stadtgestalten.org/nutzungshinweise/).
Probably we want to provide a centralized approach instead in order to simplify the deployment of new communities.
I can imagine the following approaches:
* A) we maintain a central wiki (or publish documentation within a group in a grouprise instance, e.g. https://gestadten.org/)
* B) we ship documentation pages as part of the software
* C) we populate some articles during the first installation of the software (similar to [moinmoin's language setup](http://master19.moinmo.in/LanguageSetup))
These options differ regarding the required complexity for contributors as well as centralized vs. distributed.
Right now I would like to add documentation for the `matrix_chat` extension and I am not sure, where to do this.
What do you think?https://git.hack-hro.de/grouprise/grouprise/-/issues/683Doku: deb-Quelle "deb.grouprise.org"2020-09-11T02:51:09+02:00Lars KruseDoku: deb-Quelle "deb.grouprise.org"Für die grouprise-Installation auf einem Debian-System ist die folgende Quelle hilfreich:
```
deb https://deb.grouprise.org/ unstable main
```
Zudem sind für Debian Buster einige Backports-Pakete notwendig:
```
deb http://deb.debian.org...Für die grouprise-Installation auf einem Debian-System ist die folgende Quelle hilfreich:
```
deb https://deb.grouprise.org/ unstable main
```
Zudem sind für Debian Buster einige Backports-Pakete notwendig:
```
deb http://deb.debian.org/debian buster-backports main
```
Dies sollten wir irgendwo dokumentieren.https://git.hack-hro.de/grouprise/grouprise/-/issues/614grouprise settings2019-01-18T09:55:36+01:00Robertgrouprise settingsIch möchte die Settings sortieren. Dafür sammle ich alle Dinge ein, die wir selbst definieren.
Es gibt zwei Möglichkeiten:
* Wir definieren ein `dict`:
```
GROUPRISE = {
'SETTING1': 'blafasel',
...
}
```
* Wir lassen...Ich möchte die Settings sortieren. Dafür sammle ich alle Dinge ein, die wir selbst definieren.
Es gibt zwei Möglichkeiten:
* Wir definieren ein `dict`:
```
GROUPRISE = {
'SETTING1': 'blafasel',
...
}
```
* Wir lassen es als einzelne Settings mit Präfix:
```
GROUPRISE_SETTING1 = 'blafasel'
...
```
Welche Variante findet ihr besser?Release 3RobertRoberthttps://git.hack-hro.de/grouprise/grouprise/-/issues/502Extract Software features from tools text2021-05-14T17:32:18+02:00RobertExtract Software features from tools text* auf einer eigenen Seite unterbringen (statisch, plattformunabhängig)
* Link zu ergänzenden Infos (per Plattform)
* Design: Infoboxen, Bilder
siehe auch #484* auf einer eigenen Seite unterbringen (statisch, plattformunabhängig)
* Link zu ergänzenden Infos (per Plattform)
* Design: Infoboxen, Bilder
siehe auch #484https://git.hack-hro.de/grouprise/grouprise/-/issues/367Create documentation2018-02-06T18:21:26+01:00RobertCreate documentation* außerhalb von GitLab
* Installation, Konfiguration, ...
* evtl. auch Code-Dokumentation?* außerhalb von GitLab
* Installation, Konfiguration, ...
* evtl. auch Code-Dokumentation?https://git.hack-hro.de/grouprise/grouprise/-/issues/329runserver fails with empty secret key2017-05-06T20:13:27+02:00Robertrunserver fails with empty secret key```
$ python manage.py runserver
Traceback (most recent call last):
File "manage.py", line 10, in <module>
execute_from_command_line(sys.argv)
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/core/manageme...```
$ python manage.py runserver
Traceback (most recent call last):
File "manage.py", line 10, in <module>
execute_from_command_line(sys.argv)
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/core/management/__init__.py", line 363, in execute_from_command_line
utility.execute()
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/core/management/__init__.py", line 355, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/core/management/base.py", line 283, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/core/management/commands/runserver.py", line 62, in execute
super(Command, self).execute(*args, **options)
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/core/management/base.py", line 330, in execute
output = self.handle(*args, **options)
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/core/management/commands/runserver.py", line 73, in handle
if not settings.DEBUG and not settings.ALLOWED_HOSTS:
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/conf/__init__.py", line 56, in __getattr__
self._setup(name)
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/conf/__init__.py", line 41, in _setup
self._wrapped = Settings(settings_module)
File "/home/robert/.virtualenvs/stadt/lib/python3.4/site-packages/django/conf/__init__.py", line 129, in __init__
raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
```Mai Release (1.8)