YunoHost bundle of Firefox Sync Server with an interface.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Rigel Kent b54ead99d5
Merge pull request #4 from Josue-T/patch-2
1 year ago
conf Improve security in Nginx config 2 years ago
patch/sources added patch directory + patch on tmp_swap_file 2 years ago
scripts Fix some importants bug 2 years ago
sources @ 0b784329b2 sources modified as a submodule. 2 years ago
.gitignore Fix 'secret' variable - see issue : https://github.com/abeudin/ffsync_ynh/issues/17 3 years ago
.gitmodules modified .gitmodule 2 years ago
LICENSE added README and LICENSE 2 years ago
README.md fixed sed error at install and updated README.md 2 years ago
manifest.json set "yunohost": ">> 2.5.4 as dependency on the manifest 2 years ago

README.md

Mozilla’s Sync Server for Yunohost

yunohost status

The Sync Server (ex Weaver) provides a replacement for Firefox’s default server (hosted at Mozilla). Its code is available on the Sync-1.5 Server documentation (no official documentation yet for the 1.6.x as it is really the bleeding edge version).

By default, a server set up will defer authentication to the Mozilla-hosted accounts server at https://accounts.firefox.com. So you will still have to authenticate at Mozilla, but the storage of your information will be done on your host.

Shipped Sync Server version: 1.6.2 (still 1.5 API)

Getting Started

Install it with the current url via the admin interface, or for a verbose install using sudo yunohost app install https://github.com/YunoHost-Apps/ffsync_ynh --verbose.

Once installed, reaching http://domain.tld/path/ should show a page explaining how to configure it. Otherwise please refer to the Yunohost page.

welcoming page

Contributing

From the sources directory, do as follows:

make build

make test

./local/bin/gunicorn --reload --paste syncserver.ini instead of the classical make serve to take into account changes you will surely do by developping the app.

Debug

Apart from the typical service ffsync status, you might want to see what requests cause errors by coloring them:

tail -f /var/log/ffsync.log | perl -pe 's/.*404.*/\e[1;31m$&\e[0m/g'