protonmail-bridge-nextcoud-.../docker-compose.yml

services:
  protonmail-bridge:
    image: dancwilliams/protonmail-bridge:latest
    ports:
      - 1025:25/tcp
      - 1143:143/tcp
    restart: unless-stopped
    volumes:
      - protonmail:/root

volumes:
  protonmail:
    name: protonmail
Add a docker compose file (#70) It's quite the norm to include a docker-compose file, generally in the README or the root for people to copy and modify. For example as https://github.com/wfg/docker-openvpn-client has done so. If there are [Environmental variables](https://github.com/wfg/docker-openvpn-client#environment-variables), they should also be documented - in this case there isn't. 2023-05-02 06:26:43 +00:00			`services:`
			`protonmail-bridge:`
Update docs to reflect community fork and recent changes - Rewrite README: update all refs from shenxn to dancwilliams, remove deb build references, document what changed from upstream, simplify tags section, update all docker run and compose commands, add architecture table, add version update automation section, add credits - Update SECURITY.md: replace shenxn contact with dancwilliams GitHub issue reporting, clarify scope (container vs bridge itself) - Update docker-compose.yml: point to dancwilliams/protonmail-bridge, remove deprecated version key 2026-02-25 02:17:41 +00:00			`image: dancwilliams/protonmail-bridge:latest`
Add a docker compose file (#70) It's quite the norm to include a docker-compose file, generally in the README or the root for people to copy and modify. For example as https://github.com/wfg/docker-openvpn-client has done so. If there are [Environmental variables](https://github.com/wfg/docker-openvpn-client#environment-variables), they should also be documented - in this case there isn't. 2023-05-02 06:26:43 +00:00			`ports:`
			`- 1025:25/tcp`
			`- 1143:143/tcp`
			`restart: unless-stopped`
Improve Docker Compose documentation and example (#95) - Clean up the example `docker-compose.yml` file by removing unnecessary configuration/comments and add missing volume declaration - Update the project README.md with instructions on how to use the project with Docker Compose 2024-02-08 03:06:43 +00:00			`volumes:`
			`- protonmail:/root`
Update docs to reflect community fork and recent changes - Rewrite README: update all refs from shenxn to dancwilliams, remove deb build references, document what changed from upstream, simplify tags section, update all docker run and compose commands, add architecture table, add version update automation section, add credits - Update SECURITY.md: replace shenxn contact with dancwilliams GitHub issue reporting, clarify scope (container vs bridge itself) - Update docker-compose.yml: point to dancwilliams/protonmail-bridge, remove deprecated version key 2026-02-25 02:17:41 +00:00
Add a docker compose file (#70) It's quite the norm to include a docker-compose file, generally in the README or the root for people to copy and modify. For example as https://github.com/wfg/docker-openvpn-client has done so. If there are [Environmental variables](https://github.com/wfg/docker-openvpn-client#environment-variables), they should also be documented - in this case there isn't. 2023-05-02 06:26:43 +00:00			`volumes:`
			`protonmail:`
			`name: protonmail`