EteSync - Secure Data Sync

A skeleton app for running your own EteSync server

Installation

Before installing the EteSync server make sure you install virtualenv (for Python 3):

Arch Linux: pacman -S python-virtualenv
Debian/Ubuntu: apt-get install python3-virtualenv

Then just clone the git repo and set up this app:

git clone https://github.com/etesync/server-skeleton.git

cd server-skeleton

# Set up the environment and deps
virtualenv -p python3 venv  # If doesn't work, try: virtualenv3 venv
source venv/bin/activate

pip install -r requirements.txt

Edit the settings file. Please refer to the Django deployment checklist for full instructions on how to configure a Django app for production. Some particular settings that should be edited are:

ALLOWED_HOSTS -- this is the list of host/domain names or addresses on which the app will be served
DEBUG -- handy for debugging, set to False for production
SECRET_KEY -- an ephemeral secret used for various cryptographic signing and token generation purposes. See below for how default configuration of SECRET_KEY works for this project.

Now you can initialise our django app

./manage.py migrate

And you are done! You can now run the debug server just to see everything works as expected by running:

./manage.py runserver 0.0.0.0:8000

Using the debug server in production is not recommended, so please read the following section for a proper deployment.

Production deployment

EteSync is based on Django so you should :

either follow the instructions of the Django project here.
either/or follow the instructions from uwsgi here.

The webserver should also be configured to serve EteSync using TLS.

There are more details about a proper production setup in the wiki.

Usage

Create yourself an admin user:

./manage.py createsuperuser

At this stage you can either just use the admin user, or better yet, go to: www.your-etesync-install.com/admin and create a non-privileged user that you can use.

That's it!

Now all that's left is to open the EteSync app, add an account, and set your custom server address under the "advance" section.

`SECRET_KEY` and `secret.txt`

The default configuration creates a file “secret.txt” in the project’s base directory, which is used as the value of the Django SECRET_KEY setting. You can revoke this key by deleting the secret.txt file and the next time the app is run, a new one will be generated. Make sure you keep the secret.txt file secret (don’t accidentally commit it to version control, exclude it from your backups, etc.). If you want to change to a more secure system for storing secrets, edit etesync_server/settings.py and implement your own method for setting SECRET_KEY (remove the line where it uses the get_secret_from_file function). Read the Django docs for more information about the SECRET_KEY and its uses.

Updating

First, run git pull --rebase to update this repository. Then, inside the virtualenv:

Run pip install -U -r requirements.txt to update the dependencies.
Run python manage.py migrate to perform database migrations.

You can now restart the server.

Supporting EteSync

Please consider registering an account even if you self-host in order to support the development of EteSync, or help by spreading the word.

3.9 KiB Raw Blame History Unescape Escape