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.
56 lines
2.7 KiB
Markdown
56 lines
2.7 KiB
Markdown
6 years ago
|
<p align="center">
|
||
|
|
<img width="120" src="src/images/logo.svg" />
|
||
|
4 years ago
|
<h1 align="center">EteSync - Encrypt Everything</h1>
|
||
|
6 years ago
|
</p>
|
||
|
7 years ago
|
|
||
|
6 years ago
|
The EteSync Web App - Use EteSync from the browser!
|
||
|
7 years ago
|
|
||
|
|
|
||
|
|
|
||
|
2 years ago
|
[](https://www.etebase.com/community-chat/)
|
||
|
7 years ago
|
|
||
|
4 years ago
|
For notes, please refer to [the EteSync Notes](https://github.com/etesync/etesync-notes/) repository.
|
||
|
|
|
||
|
7 years ago
|
# Usage
|
||
|
7 years ago
|
|
||
|
4 years ago
|
A live instance is available on: https://pim.etesync.com
|
||
|
7 years ago
|
|
||
|
7 years ago
|
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](https://www.etesync.com/faq/#web-client).
|
||
|
|
|
||
|
|
## 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.
|
||
|
|
|
||
|
4 years ago
|
You can get the latest version of the web client from https://pim.etesync.com/etesync-web.tgz. This
|
||
|
5 years ago
|
file is automatically generated on each deploy and is exactly the same as the delpoyed version.
|
||
|
3 years ago
|
After fetching this file you need to extract it by e.g. running `tar -xzf etesync-web.tgz`, and then
|
||
|
5 years ago
|
you can serve the files using your favourite web server. Please keep in mind that opening the HTML files
|
||
|
|
directly in the browser is not supported.
|
||
|
|
|
||
|
|
If you are just serving the app locally, you could, for example, use the python built-in web server by
|
||
|
|
running `python3 -m http.server` from inside the extracted `etesync-web` directory. If you plan on
|
||
|
|
serving it from a server, please use a proper web server such as nginx.
|
||
|
|
|
||
|
|
## Building it yourself
|
||
|
|
|
||
|
|
Before you can build the web app from source, you need to make sure you have `yarn` install.
|
||
|
7 years ago
|
|
||
|
|
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.
|
||
|
6 years ago
|
|
||
|
4 years ago
|
The URL of the EteSync API the web app connects to defaults to `api.etebase.com`, but can be changed on
|
||
|
5 years ago
|
the login page. You can change this default by setting the environment variable `REACT_APP_DEFAULT_API_PATH`
|
||
|
|
during the build. This can be useful for self-hosting. You can set the default URL to the address
|
||
|
|
of your self-hosted EteSync server so you don't have to change the address for every login.
|
||
|
|
|
||
|
6 years ago
|
### Serving from a subdirectory
|
||
|
6 years ago
|
|
||
|
|
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.
|