description
django-sync-server (formerly ‘django-weave’) is a reusable application which implements a Firefox sync server for Django.
The Server works up to FxSync v1.16.x (Firefox v14) Well tested also with SeaMonkey v2.3
How to create a django-sync-server test virtualenv: CreateTestEnvironment Wiki page
What is Firefox Sync?
Firefox Sync (formerly Mozilla Labs Weave Browser Sync) is a free browser add-on from Mozilla Labs that keeps your bookmarks, saved passwords, browsing history and open tabs backed up and synchronized, with end-to-end encryption for your privacy and security.
sourcecode
Our code hosted on github.com/jedie/django-sync-server
Clone our git repo:
git clone git://github.com/jedie/django-sync-server.git
A git clone also exist on google code.
download
Python packages available on: http://pypi.python.org/pypi/django-sync-server/
Unofficial debian packages: http://debian.fladi.at/pool/main/d/django-sync-server/
migrate
v0.3.0 to v0.4.0
We used django-south to change the existing models. Do this:
~$ cd django_sync_server_env ~/django_sync_server_env$ source bin/activate (django_sync_server_env)~/django_sync_server_env$ pip install South (django_sync_server_env)~/django_sync_server_env$ cd src/django-sync-server/testproject (django_sync_server_env)~/django_sync_server_env/src/django-sync-server/testproject$ ./manage.py syncdb (django_sync_server_env)~/django_sync_server_env/src/django-sync-server/testproject$ ./manage.py migrate weave 0001 --fake (django_sync_server_env)~/django_sync_server_env/src/django-sync-server/testproject$ ./manage.py migrate weave
Note: After South install, you must insert “south” in INSTALLED_APPS list in our own settings.py see also: https://github.com/jedie/django-sync-server/commit/452668fb671662a15da2faf1e1c1f642d744b5dc#diff-1
history
v0.4.2 - 27.07.2012
Bugfix in info_page() page: Use RequestContext(), so that inherit template can use variables from context processors
remove git timestamp from version string
v0.4.1
Bugfix to support sync with Firefox v3.6 - v5 (see: https://github.com/jedie/django-sync-server/issues/11 )
v0.4.0
Updates to FxSync API 1.1 (see: https://github.com/jedie/django-sync-server/issues/11 )
Create a info page on root url
v0.3.0
Add work-a-round for username longer than 30 characters (see: https://github.com/jedie/django-sync-server/issues/8 )
Add DONT_USE_CAPTCHA and DEBUG_REQUEST to app settings.
v0.2.1
Some updates for django v1.2 API changes
Change version string and add last commit date
v0.2.0
django-sync-server own basic auth function can be disabled via app settings.
v0.1.7
‘django-weave’ was renamed to ‘django-sync-server’
v0.1.6
Bugfix checking weave api version from url.
Add a tiny info root page to testproject.
v0.1.5
Changes to establish compatibility with Weave client v1.2b3
v0.1.4
split weave app and testproject
v0.1.3
Remove dependency on django-reversion
change Collection sites ManyToManyField to a normal ForeignKey
v0.1.2
many code cleanup and bugfixes
remove django-tools and django-reversion decencies
v0.1.0pre-alpha
sync works
v0.0.1
initial checkin
donation
links
Project page |
|
GitHub |
|
PyPi |
|
Firefox Sync homepage |
|
IRC |
more links: SyncLinks Wiki page
Metadata
Release files for django-sync-server 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-sync-server-0.4.2.tar.gz | 32.4 kB | Without provenance | Details for django-sync-server-0.4.2.tar.gz |
Release files / django-sync-server-0.4.2.tar.gz
| Download URL | django-sync-server-0.4.2.tar.gz |
|---|---|
| Size | 32.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2fc23208c8db4d4166c3a9529f9466236a997509cfd334c6f7ca826f9cc880c
|
|
BLAKE2b-256 checksum How to use checksums |
15865d1dc01dd3d521f05eabbc0008b82e518c046e7b63b927bd80be941603d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-sync-server 0.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.