self-hosted/Mailu
1
0
Fork 0
mirror of https://github.com/Mailu/Mailu.git synced 2025-01-18 03:21:36 +02:00
Code Issues Releases Activity

Fix issue-template whitespacing; Add some small formatting

Browse Source
This commit is contained in:
Dario Ernst 2020-09-11 22:39:21 +02:00
parent 8b0e2edc52
commit 2e574d7ffb
1 changed files with 18 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
ISSUE_TEMPLATE.md
View File

@ -1,4 +1,4 @@
Thank you for opening an issue with Mailu. Please understand that issues are meant for bugs and enhancement-requests. Thank you for opening an issue with Mailu. Please understand that issues are meant for bugs and enhancement-requests.
For **user-support questions**, reach out to us on [matrix](https://matrix.to/#/#mailu:tedomum.net). For **user-support questions**, reach out to us on [matrix](https://matrix.to/#/#mailu:tedomum.net).
To be able to help you best, we need some more information. To be able to help you best, we need some more information.
@ -16,21 +16,29 @@ Environment:
- [ ] docker swarm - [ ] docker swarm
Versions: Versions:
To find your version, get the image name of a mailu container and read the version from the tag (example for version 1.7). To find your version, get the image name of a mailu container and read the version from the tag (example for version 1.7).
`docker ps -a | grep mailu` ```
`140b09d4b09c mailu/roundcube:1.7 "docker-php-entrypoi…" 2 weeks ago Up 2 days (healthy) 80/tcp` $> docker ps -a | grep mailu
140b09d4b09c mailu/roundcube:1.7 "docker-php-entrypoi…" 2 weeks ago Up 2 days (healthy) 80/tcp
$> grep MAILU_VERSION docker-compose.yml mailu.env
```
## Description ## Description
<Further explain the bug in a few words. It should be clear what the unexpected behaviour is. Share it in an easy-to-understand language.> <Further explain the bug in a few words. It should be clear what the unexpected behaviour is. Share it in an easy-to-understand language.>
## Replication Steps ## Replication Steps
< Steps for replicating your issue> <Steps for replicating your issue>
## Expected behaviour ## Expected behaviour
<Explain what results you expected - be as specific as possible. Just saying "it doesn’t work as expected" is not useful. It's also helpful to describe what you actually experienced. > <Explain what results you expected - be as specific as possible. Just saying "it doesn’t work as expected" is not useful. It's also helpful to describe what you actually experienced.>
## Logs ## Logs
Often it is very useful to include log fragments of the involded component. You can get the logs via `docker logs <container name> --tail 1000`. For example for the admin container: Often it is very useful to include log fragments of the involved component. You can get the logs via `docker logs <container name> --tail 1000`. For example for the admin container:
`docker logs mailu_admin_1 --tail 1000` `docker logs mailu_admin_1 --tail 1000`
or using docker-compose `docker-compose -f /mailu/docker-compose.yml logs --tail 1000 admin` or using docker-compose `docker-compose -f /mailu/docker-compose.yml logs --tail 1000 admin`
If you can find the relevant section, please share only the parts that seem relevant. If you have any logs, please enclose them in code tags, like so:
````markdown
```
Your logs here!
```
````