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

[docs] self-hosting + Docker guide #111

Open
rdlmda opened this issue Mar 18, 2019 · 14 comments
Open

[docs] self-hosting + Docker guide #111

rdlmda opened this issue Mar 18, 2019 · 14 comments

Comments

@rdlmda
Copy link

rdlmda commented Mar 18, 2019

Is it possible to run this in one (or more) Docker containers? I'd really like to know.

I suppose I could try to write a docker-compose file but my knowledge of Docker, networking, email standards, etc are not up to the task. So I'd feel more comfortable if someone more knowledgeable could pick up this task.

@loiu92
Copy link

loiu92 commented Mar 27, 2019

For my own usage, to try forward-email, i'm writing Dockerfile and docker-compose to have all requirements in container. I can share it when it's done

@rdlmda
Copy link
Author

rdlmda commented Mar 27, 2019

@loiu92 that would be amazing! Please do.

@nysky1
Copy link

nysky1 commented Apr 24, 2019

How's this file coming?

@UnoSD
Copy link

UnoSD commented Aug 24, 2019

This would be awesome for self-hosting in the cloud. Is there any update? I will try and do it myself, but I have a really poor Docker experience.

@UnoSD
Copy link

UnoSD commented Aug 24, 2019

It took me a while as Docker debugging is not exactly straightforward... but:

https://github.com/UnoSD/forward-email-docker/blob/master/Dockerfile

Some commands are a massive hack (like getting the README.md file and extracting the start script), but at least it should be working and it should be easy to fix and update.

EDIT: Well, ehm.. working... it runs and starts the service, I don't know if it actually works, but I will test it possibly tomorrow.

EDIT: I give up, I can get it to communicate over auto assigned ports, but not 25. It it frustrating and I cannot waste so much time on this, if anyone with a good Docker knowledge fancy helping, I can resume.

@UnoSD
Copy link

UnoSD commented Aug 25, 2019

This is annoying. I figured out why... Azure blocks port 25 so that cannot be hosted on Azure. @niftylettuce can your app work with a encryption? 25 seems to be blocked to avoid unencrypted traffic that is, by convention, on that port. I can obviously use a different port, but then I presume the traffic will have a different format being encrypted so it won't work.

@niftylettuce
Copy link
Collaborator

@UnoSD port 25 is required, so Azure is out.

@niftylettuce
Copy link
Collaborator

@UnoSD can you submit a PR to this repo with your beautiful docker file? 👍 🙏

@niftylettuce
Copy link
Collaborator

Actually, if you submit a PR, I will update and fix it all for you. There are a lot of issues with your current file right now. I just took a quick glance

@UnoSD
Copy link

UnoSD commented Aug 26, 2019

@niftylettuce without Azure support is pretty useless for me, so I can't spend much more time trying to make it work, but I am happy to fork your repo and put it somewhere for you to update it for others, any preference on the folder?

Update: Contacted Microsoft and they opened it for me, back in the game :)

I've create the PR, I have created a git submodule to carry on creating the infrastructure stuff independently, if you prefer just a file PR, let me know.

@tracker1
Copy link

UnoSD since it's really small, you could probably use a smaller provider like DigitalOcean or Linode to host the app... Thinking to myself, may put this on my dokku server on DO.

@X1Aaron
Copy link
Contributor

X1Aaron commented Sep 5, 2019

@UnoSD @niftylettuce Thanks! :)

@UnoSD
Copy link

UnoSD commented Sep 13, 2019

@tracker1 thanks for the suggestion, I will look at those providers, too, but I get free Azure credits with my MSDN subscription, so I don't have to pay for the container there.

@dapetcu21 dapetcu21 mentioned this issue Sep 19, 2019
2 tasks
@davidkaufman
Copy link

FYI: Amazon AWS also blocks SMTP connections to new EC2 instances by default. Well, they say they just "throttle" inbound traffic on port 25, but in my experience traffic is slowed to zero bytes per second :-) But, like Azure, they will unblock the port if you just ask. You can ask by submitting this form: https://aws.amazon.com/premiumsupport/knowledge-center/ec2-port-25-throttle/

@niftylettuce niftylettuce changed the title Docker support Self-Hosting + Docker Guide Apr 27, 2020
@niftylettuce niftylettuce changed the title Self-Hosting + Docker Guide [docs] self-hosting + Docker guide Aug 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants