Mouws/protonmail-bridge-nextcoud-podman
1
0
Fork 1
mirror of https://github.com/shenxn/protonmail-bridge-docker.git synced 2026-03-27 05:45:58 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
255 Commits 1 Branch 0 Tags 629 KiB
32eb851fc4
Commit Graph

3 Commits

Author SHA1 Message Date
Dan Williams
8c5061f641 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-24 20:17:41 -06:00
Mark Monteiro
9d2bf07c78
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 11:06:43 +08:00
Daniel Nathan Gray
67415bd261
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 14:26:43 +08:00