mirror of
https://github.com/docker-mailserver/docker-mailserver.git
synced 2025-07-10 01:15:00 +02:00
docs(fix): Update wiki references to the new docs url
Additionally replaces old references to `tvial` images with the new `mailserver` docker image name.
This commit is contained in:
parent
724fe72d20
commit
463bc967d2
17 changed files with 37 additions and 37 deletions
|
@ -39,7 +39,7 @@ version: '2'
|
|||
|
||||
services:
|
||||
mail:
|
||||
image: tvial/docker-mailserver:latest
|
||||
image: mailserver/docker-mailserver:latest
|
||||
hostname: mail
|
||||
domainname: domain.com
|
||||
container_name: mail
|
||||
|
|
|
@ -20,7 +20,7 @@ The [dovecot-solr Plugin](https://wiki2.dovecot.org/Plugins/FTS/Solr) is used in
|
|||
restart: always
|
||||
|
||||
mailserver:
|
||||
image: tvial/docker-mailserver:latest
|
||||
image: mailserver/docker-mailserver:latest
|
||||
...
|
||||
volumes:
|
||||
...
|
||||
|
|
|
@ -144,7 +144,7 @@ spec:
|
|||
# mountPath: /tmp/files
|
||||
containers:
|
||||
- name: docker-mailserver
|
||||
image: tvial/docker-mailserver:latest
|
||||
image: mailserver/docker-mailserver:latest
|
||||
imagePullPolicy: Always
|
||||
volumeMounts:
|
||||
- name: config
|
||||
|
|
|
@ -190,7 +190,7 @@ The second part of the setup is the actual mail container. So, in another folder
|
|||
version: '2'
|
||||
services:
|
||||
mail:
|
||||
image: tvial/docker-mailserver:latest
|
||||
image: mailserver/docker-mailserver:latest
|
||||
hostname: ${HOSTNAME}
|
||||
domainname: ${DOMAINNAME}
|
||||
container_name: ${CONTAINER_NAME}
|
||||
|
@ -379,7 +379,7 @@ This allows for support of wild card certificates: `SSL_DOMAIN=*.example.com`. H
|
|||
version: '3.8'
|
||||
services:
|
||||
mail:
|
||||
image: tvial/docker-mailserver:stable
|
||||
image: mailserver/docker-mailserver:stable
|
||||
hostname: mail
|
||||
domainname: example.com
|
||||
volumes:
|
||||
|
@ -427,7 +427,7 @@ Depending of your Traefik configuration, certificates may be stored using a file
|
|||
You can easily generate a self-signed SSL certificate by using the following command:
|
||||
|
||||
```sh
|
||||
docker run -it --rm -v "$(pwd)"/config/ssl:/tmp/docker-mailserver/ssl -h mail.my-domain.com -t tvial/docker-mailserver generate-ssl-certificate
|
||||
docker run -it --rm -v "$(pwd)"/config/ssl:/tmp/docker-mailserver/ssl -h mail.my-domain.com -t mailserver/docker-mailserver generate-ssl-certificate
|
||||
|
||||
# Press enter
|
||||
# Enter a password when needed
|
||||
|
|
|
@ -8,7 +8,7 @@ This project is Open Source. That means that you can contribute on enhancements,
|
|||
|
||||
!!! attention
|
||||
|
||||
**Before opening an issue**, read the [`README`][github-file-readme] carefully, use the [Wiki][wiki], the Postfix/Dovecot documentation and your search engine you trust. The issue tracker is not meant to be used for unrelated questions!
|
||||
**Before opening an issue**, read the [`README`][github-file-readme] carefully, study the [documentation][docs], the Postfix/Dovecot documentation and your search engine you trust. The issue tracker is not meant to be used for unrelated questions!
|
||||
|
||||
When opening an issue, please provide details use case to let the community reproduce your problem. Please start the mail server with env `DMS_DEBUG=1` and paste the output into the issue.
|
||||
|
||||
|
@ -43,7 +43,7 @@ The development workflow is the following:
|
|||
2. When your changes are validated, your branch is merged
|
||||
3. CI builds the new `:edge` image immediately and your changes will be includes in the next version release.
|
||||
|
||||
[wiki]: https://docker-mailserver.github.io/docker-mailserver
|
||||
[docs]: https://docker-mailserver.github.io/docker-mailserver/edge
|
||||
[github-file-readme]: https://github.com/docker-mailserver/docker-mailserver/blob/master/README.md
|
||||
[github-file-env]: https://github.com/docker-mailserver/docker-mailserver/blob/master/ENVIRONMENT.md
|
||||
[commit]: https://help.github.com/articles/closing-issues-via-commit-messages/
|
||||
|
|
|
@ -27,7 +27,7 @@ We are going to use this docker based mailserver:
|
|||
|
||||
services:
|
||||
mail:
|
||||
image: tvial/docker-mailserver:latest
|
||||
image: mailserver/docker-mailserver:latest
|
||||
hostname: mail
|
||||
domainname: example.org
|
||||
container_name: mail
|
||||
|
@ -76,7 +76,7 @@ We are going to use this docker based mailserver:
|
|||
|
||||
On your server you may have to do it differently.
|
||||
|
||||
- Pull the docker image: `docker pull tvial/docker-mailserver:latest`
|
||||
- Pull the docker image: `docker pull mailserver/docker-mailserver:latest`
|
||||
|
||||
- Now generate the DKIM keys with `./setup.sh config dkim` and copy the content of the file `config/opendkim/keys/domain.tld/mail.txt` on the domain zone configuration at the DNS server. I use [bind9](https://github.com/docker-scripts/bind9) for managing my domains, so I just paste it on `example.org.db`:
|
||||
|
||||
|
|
|
@ -60,7 +60,7 @@ Feel free to add your configuration if you achived the same goal using different
|
|||
version: '2'
|
||||
services:
|
||||
mail:
|
||||
image: tvial/docker-mailserver:release-v7.2.0
|
||||
image: mailserver/docker-mailserver:release-v7.2.0
|
||||
restart: always
|
||||
networks:
|
||||
- proxy
|
||||
|
|
|
@ -187,7 +187,7 @@ Then with plain `docker-compose`:
|
|||
```yaml
|
||||
services:
|
||||
mail:
|
||||
image: tvial/docker-mailserver:latest
|
||||
image: mailserver/docker-mailserver:latest
|
||||
volumes:
|
||||
- ./cron/sa-learn:/etc/cron.d/sa-learn
|
||||
```
|
||||
|
@ -199,7 +199,7 @@ version: "3.3"
|
|||
|
||||
services:
|
||||
mail:
|
||||
image: tvial/docker-mailserver:latest
|
||||
image: mailserver/docker-mailserver:latest
|
||||
# ...
|
||||
configs:
|
||||
- source: my_sa_crontab
|
||||
|
@ -351,7 +351,7 @@ proxy_interfaces = X.X.X.X (your public IP)
|
|||
### What About Updates
|
||||
|
||||
You can of course use a own script or every now and then pull && stop && rm && start the images but there are tools available for this.
|
||||
There is a page in the [Update and Cleanup][docs-maintenance] wiki page that explains how to use it the docker way.
|
||||
There is a section in the [Update and Cleanup][docs-maintenance] documentation page that explains how to use it the docker way.
|
||||
|
||||
### How to adjust settings with the `user-patches.sh` script
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ title: Home
|
|||
|
||||
Please first have a look at the [`README.md`][github-file-readme] to setup and configure this server.
|
||||
|
||||
This wiki provides you with advanced configuration, detailed examples, and hints.
|
||||
This documentation provides you with advanced configuration, detailed examples, and hints.
|
||||
|
||||
## Getting Started
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue