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.
632 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 'ec9d8d3329'
${ noResults }
Go to file
Tom Hacohen ec9d8d3329 Revert "Tasks: adds filter by tag feature" 
Reverting because I'm not the author. The next commit will have the
right author set.

This reverts commit b14697474c.
 		5 years ago
public Fix type in page title. 6 years ago
src Revert "Tasks: adds filter by tag feature" 5 years ago
.env lint: replace tslint with eslint and fix new warnings and errors. 5 years ago
.eslintrc.js eslint: changed unused-args to always warn. 5 years ago
.gitignore lint: replace tslint with eslint and fix new warnings and errors. 5 years ago
AUTHORS AUTHORS: remove duplicate entry. 5 years ago
LICENSE Add license and update README. 7 years ago
README.md README: fix typo 6 years ago
deploy.sh Deploy script: change rsync invocation. 5 years ago
package.json AddressBook: use a virtualized list for the contacts. 5 years ago
setenv Adjust a few of the defaults. 7 years ago
tsconfig.json Change journals to also not be a complex fetch type. 5 years ago
yarn.lock Bump acorn from 5.7.3 to 5.7.4 5 years ago

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.