Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helm chart for protonmail-bridge-docker #23

Closed
Eagleman7 opened this issue Feb 3, 2021 · 2 comments
Closed

Helm chart for protonmail-bridge-docker #23

Eagleman7 opened this issue Feb 3, 2021 · 2 comments

Comments

@Eagleman7
Copy link

Eagleman7 commented Feb 3, 2021

Hello!

I've used your container to setup an helm chart app for kubernetes:
https:/k8s-at-home/charts/tree/master/charts/protonmail-bridge

This will provide an easier way to run your app in kubernetes since it can be installed with 2 command:

helm repo add k8s-at-home https://k8s-at-home.com/charts/
helm install k8s-at-home/protonmail-bridge

Then the desciption from the kubernetes ticket still applies:

  1. Get the name of your deployed pod kubectl get pods
  2. Run interactively on the pod (setup only) kubectl exec --stdin --tty protonmail-bridge-deployment-6c79fd7f84-ftwcw -- /bin/bash
  3. Once logged in, execute the init command bash /protonmail/entrypoint.sh init
  4. You should now see the CLI for protonmail-bridge, authenticate with login
  5. (optional) if you're like me and use split address mode, change mode and info are good for printing the details.
  6. Copy your SMTP server info (or IMAP, your choice)
  7. delete the active pod so a new one gets created (which will properly fire up with your persisted settings)
@shenxn
Copy link
Owner

shenxn commented Feb 4, 2021

Thanks for the contribution. I already updated README to metion the helm chart and this issue.

@shenxn shenxn closed this as completed Feb 4, 2021
@Eagleman7
Copy link
Author

Eagleman7 commented Apr 11, 2023

Get the name of your deployed pod kubectl get pods

Run interactively on the pod (setup only) kubectl exec --stdin --tty -n core protonmail-bridge-deployment-6c79fd7f84-ftwcw -- /bin/bash

chmod +x /protonmail/entrypoint.sh

kill 19

Once logged in, execute the init command bash /protonmail/entrypoint.sh init

You should now see the CLI for protonmail-bridge, authenticate with login

(optional) if you're like me and use split address mode, change mode and info are good for printing the details.

Copy your SMTP server info (or IMAP, your choice)

delete the active pod so a new one gets created (which will properly fire up with your persisted settings)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants