Customization Needed for Wildduck Email Server
Budget: $30 – $250 USD
I already have a wildduck email server with docker containers. The repo is at https://github.com/johnqh/wildduck-dockerized
I need some modifications done so I can modify the code. Which includes
1. Instead of using standard containers, Build and deploy containers from my forked Wildduck and Haraka repos:
https://github.com/johnqh/wildduck-dockerized
https://github.com/johnqh/haraka-plugin-wildduck
https://github.com/johnqh/wildduck-webmail
Goal: if I modify code in the forked repo, they get deployed when I run setup scripts.
2. Instead of have both backend (wildduck + Haraka etc) and frontend (wildduck-webmail) on the same server, I want to deploy them separately:
A setup_be.sh to deploy all backend services, basically everything except wildduck_webmail.
A setup_fe.sh to deploy on the wildduck_webmail, with configuration to use previously deployed backend server IP address for backend services.
3. Make any necessary source code or configuration changes to ensure the frontend and backend services work well together. This emails I can use a native email client to connect to the email server with standard IMAP and SMTP, and I can use the webmail frontend.
Notice, please post your bid with real price. Do not use placeholder prices. This is a small project, and the scope is well defined. I am not going to chat with teams before I select the winner. Instead, I will only look at your price, your portfolio, and your message.
I need some modifications done so I can modify the code. Which includes
1. Instead of using standard containers, Build and deploy containers from my forked Wildduck and Haraka repos:
https://github.com/johnqh/wildduck-dockerized
https://github.com/johnqh/haraka-plugin-wildduck
https://github.com/johnqh/wildduck-webmail
Goal: if I modify code in the forked repo, they get deployed when I run setup scripts.
2. Instead of have both backend (wildduck + Haraka etc) and frontend (wildduck-webmail) on the same server, I want to deploy them separately:
A setup_be.sh to deploy all backend services, basically everything except wildduck_webmail.
A setup_fe.sh to deploy on the wildduck_webmail, with configuration to use previously deployed backend server IP address for backend services.
3. Make any necessary source code or configuration changes to ensure the frontend and backend services work well together. This emails I can use a native email client to connect to the email server with standard IMAP and SMTP, and I can use the webmail frontend.
Notice, please post your bid with real price. Do not use placeholder prices. This is a small project, and the scope is well defined. I am not going to chat with teams before I select the winner. Instead, I will only look at your price, your portfolio, and your message.