E2E encrypted contacts, calendars and tasks: https://www.etesync.com/ - upstream sources are at https://github.com/etesync
 
 
 
 
 
 
Go to file
Tom Hacohen f0ab21172a Types ical.js: fix fromJSDate. 2018-01-17 11:21:37 +00:00
public Add support for Signed Pages page signing. 2017-12-29 14:20:42 +00:00
src Types ical.js: fix fromJSDate. 2018-01-17 11:21:37 +00:00
.gitignore Adjust a few of the defaults. 2017-11-30 11:08:47 +00:00
LICENSE Add license and update README. 2017-12-01 12:08:52 +00:00
README.md Update README 2017-12-28 16:11:38 +00:00
deploy.sh Add a deployment script that supports signed pages. 2017-12-29 14:43:52 +00:00
package.json Remove stub package @types/reselect. 2018-01-09 15:24:11 +00:00
setenv Adjust a few of the defaults. 2017-11-30 11:08:47 +00:00
tsconfig.json Adjust code to work with es5 as a target. 2017-12-14 11:13:01 +00:00
tsconfig.test.json Initial commit. 2017-11-30 11:06:15 +00:00
tslint.json Adjust a few of the defaults. 2017-11-30 11:08:47 +00:00
yarn.lock Remove stub package @types/reselect. 2018-01-09 15:24:11 +00:00

README.md

The EteSync Web App

Use EteSync from the browser!

GitHub tag Chat on freenode

Usage

Note: This is still in an early stage, but it should be safe to use. It uses the battle tested sjcl javascript crypto library for encryption, so that should be fine too.

A live isntance is available on: https://client.etesync.com

Please be advised that while it's probably safe enough to use the hosted client in many cases, it's generally not preferable. It's recommended that you use signed releases which's signature you manually verify and are run locally!

More info is available on the FAQ.

Running your own

You can either self-host your own client to be served from your own server, or better yet, just run an instance locally.

First make sure you have yarn install.

Then clone this repository yarn, run yarn and wait until all of the deps are installed.

Then it's recommended you run yarn build to build a production ready client you should serve (even if run locally!) and then just serve the build directory from a web server. You could for exapmle use the python built-in web server by runnig python3 -m http.server from the build directory.

Alternatively, you can run the debug server just to verify everything works, though be aware that the app will probably be quite slow. To do that, run yarn start.