E2E encrypted contacts, calendars and tasks: https://www.etesync.com/ - upstream sources are at https://github.com/etesync
 
 
 
 
 
 
Go to file
Tom Hacohen 8e790ed666 Fix bug with web client not remembering a user is logged in.
Was introduced in 118d26ce83
2020-02-25 15:51:15 +02:00
public Fix type in page title. 2019-03-27 12:10:29 +00:00
src Fix bug with web client not remembering a user is logged in. 2020-02-25 15:51:15 +02:00
.env lint: replace tslint with eslint and fix new warnings and errors. 2019-11-06 00:18:17 +02:00
.eslintrc.js eslint: changed unused-args to always warn. 2019-11-07 12:02:51 +02:00
.gitignore lint: replace tslint with eslint and fix new warnings and errors. 2019-11-06 00:18:17 +02:00
LICENSE Add license and update README. 2017-12-01 12:08:52 +00:00
README.md README: fix typo 2019-02-08 13:20:46 +00:00
deploy.sh Deploy script: change rsync invocation. 2020-02-05 13:02:07 +02:00
package.json DateTimePicker: change to a more usable date and time picker 2020-02-14 13:22:33 +02:00
setenv Adjust a few of the defaults. 2017-11-30 11:08:47 +00:00
tsconfig.json Change journals to also not be a complex fetch type. 2020-02-21 16:43:42 +02:00
yarn.lock DateTimePicker: change to a more usable date and time picker 2020-02-14 13:22:33 +02:00

README.md

EteSync - Secure Data Sync

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 instance 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 example, use the python built-in web server by running 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.

Serving from a subdirectory

In order to run your own version and serve it from a subdirectory rather than the top level of the domain, add "homepage": "/subdir-name" to the package.json file.