-
Notifications
You must be signed in to change notification settings - Fork 120
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
Dockerfile #49
Comments
You can connect directly but only locally as it's not HTTPS.
As of the latest release,
Yes. Launching 3 processes won't work well (at least if you run both IMAP and CardDAV, SMTP and another server might work better). I definitely want to add this feature: #21
Added some README instructions about this. |
I'd prefer if the Dockerfile was community-maintained, out-of-tree. |
@emersion cool, I've set up some example configurations here: https://github.com/harleylang/hydroxide-docker |
Thank you for this project ! I really don't think to use the proprietary bridge from protonmail.
Since hydroxide is meant to run headless, I think it makes sense to have a small dockerfile for
it and run it in a separate container. Below, there is a simple example to build and create such container.
To make it usable I need a few more information.
?
Otherwise to containerize hydroxide I need to add a process manager that defeats a bit the philosophy of one process per container ...
Once you have docker installed on your machine and saved the snipped below as
Dockerfile
, it's just as simple asdocker build . -t hydroxide
anddocker run hydroxide
And one last question : this is me not understanding... when I do
hydroxide auth <username>
which username is that ? protonmail ? Or a local username used to store all the protonmail data separate from others ?The text was updated successfully, but these errors were encountered: