You’ll find a quick start guide, sample docker-compose.yml, and instructions for setting up.
It is also possible to use this setup to sync Everdo remotely either using a VPN into your home network (e.g. using Wireguard and Tailscale) or a reverse proxy.
This project is still an very early-stage. You are welcome to try it out. If you run into issues or have ideas for improvements please open an issue or PR on GitHub or message me here! Contributions are very welcome.
Warning: Exposing your Everdo instance to the public internet even via or a reverse proxy using TLS encryption is risky! Both design and implementation errors can lead to data leaks or compromise. If you require remote access to the dockerized Everdo instance, prefer methods like a VPN into your home network (Wireguard, Tailscale).
Andrei knows of this project and allowed me to inform the community about it. He wants to underline that exposing any service to the web is inherentliy dangerous and you have to be very aware of the possible risks. When in doubt, use the ESS for remote synchronization.
I had two problems actually … build wasn’t working at first so when I posted, I was looking for the container in GitHub registry. But actually, my container manager is stuck on a very old version of build, so surgically upgrading buildx got my image built successfully.
Next I will try to figure out sync ports … I suspect I want a similar thing to you, a machine headless to manage local sync that also serves as the VPN gateway for remote syncing.
Thanks again