infra
/
etesync
2
0
Fork 0
Code Issues Pull Requests Packages Activity
E2E encrypted contacts, calendars and tasks: https://www.etesync.com/ - upstream sources are at https://github.com/etesync
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
190 Commits
1 Branch
0 Tags
3.5 MiB
TypeScript 66.5%
Python 31.9%
HTML 0.5%
Shell 0.4%
CSS 0.4%
Other 0.3%
 
 
 
 
 
 
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '97eaa756fe'
${ noResults }
Go to file
Tom Hacohen 97eaa756fe Add FIXMEs for the withRouter workaround 
Because of: https://github.com/ReactTraining/react-router/issues/5795
We have to use withRouter which triggers a lot of extra renderings.
This means that until the bug is fixed we have to use withRouter and
some memoization to make sure we don't recalc everything all the time.
 		7 years ago
public Update app name, title, and icon. 7 years ago
src Add FIXMEs for the withRouter workaround 7 years ago
.gitignore Adjust a few of the defaults. 7 years ago
LICENSE Add license and update README. 7 years ago
README.md Update README 7 years ago
package.json Explicitly include react-router as a dep. 7 years ago
setenv Adjust a few of the defaults. 7 years ago
tsconfig.json Adjust code to work with es5 as a target. 7 years ago
tsconfig.test.json Initial commit. 7 years ago
tslint.json Adjust a few of the defaults. 7 years ago
yarn.lock Add immutable.js. 7 years ago

README.md

An EteSync web client. Use EteSync from the browser

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. To do that, run yarn start.