Hacker News new | past | comments | ask | show | jobs | submit login

It's both! Most users are fine with hosted infrastructure, so they don't need to run+maintain it themselves. But you totally can if you want. The code for the sync engine and API is here on GitHub: https://github.com/nylas/sync-engine

We're working on putting together a better doc that outlines how to set up the entire stack locally. Ideally this could even be a Docker container.

And you should always read the source! ;)




And N1 has some easy way of integrating with a locally hosted sync engine, spawning it at N1 startup, and shutting it down at N1 tear down? Or is it the sort of thing were I'll need to host my own infra running this sync engine, and then hand tweak some config file to connect to my infra instead of yours?


Probably the latter-- though you can do it any way you want!




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: