Charm needed: Firefox Sync

Bug #911919 reported by Jorge Castro
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Juju Charms Collection
Fix Released
Undecided
Unassigned

Bug Description

A nice charm for your own hosted Ubuntu Firefox Sync server is a nice companion for our default browser:

https://wiki.mozilla.org/Services/Sync/Server
http://docs.services.mozilla.com/howtos/run-sync.html

Jorge Castro (jorge)
description: updated
Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

Claiming this. I have this nearly working.

Changed in charms:
assignee: nobody → Ben Howard (utlemming)
status: New → In Progress
Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

Linked new branch for review.

Changed in charms:
status: In Progress → New
assignee: Ben Howard (utlemming) → nobody
Changed in charms:
assignee: nobody → Ben Howard (utlemming)
Revision history for this message
Mark Mims (mark-mims) wrote :

note to rename fsync to firefox-sync before pushing any official branches

Revision history for this message
Robert Ayres (robert-ayres) wrote :

Thanks for submitting the charm, worked well on EC2.

Please see bugs/comments below.

Bugs
*hooks/common.sh, looks like a typo within build_source when removing old build directory '${buildd}' instead of '${build_d}'.

*hooks/website-relation-joined, doesn't set 'hostname' or 'port'.

*/usr/local/sync_server/sync.db and /usr/local/sync_server/server-full/etc/sync.conf are world readable but may contain sensitive information.

Comments
*It'd be nice if the daemon ran as a different user than root.

*cache relation has hooks but no definition in metadata.yaml.

*Be quite nice if you could toggle 'allow_new_users' in sync.conf to enable/restrict new user creation via a config option.

Please fix the bugs and consider the comments then resubmit for a second review.

Changed in charms:
status: New → Incomplete
Changed in charms:
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

*hooks/common.sh, looks like a typo within build_source when removing old build directory '${buildd}' instead of '${build_d}'.
--- Fixed

*hooks/website-relation-joined, doesn't set 'hostname' or 'port'
--- Fixed.

*world readable files:
--- Fixed.

*It'd be nice if the daemon ran as a different user than root.
--- Introduced code to create and run as firefox-sync user

*cache relation has hooks but no definition in metadata.yaml
--- Removed as artfact

*Be quite nice if you could toggle 'allow_new_users' in sync.conf to
enable/restrict new user creation via a config option.
-- Implemented

Changed in charms:
status: Incomplete → New
Revision history for this message
Marco Ceppi (marcoceppi) wrote :

Hi Ben!

Thanks for making those changes, the charm is really coming together!

The only issue I have at the moment is I can't seem to get Firefox to actually accept the server when I attempted to test the sync[1]. It's possible I did something wrong which leads to my next point, the README is a tad out of date, the charm name needs to be updated as it uses the fsync name. I'd also like to see a section on how to actually use the service within firefox as I can't seem to get it working.

A few knitpicks:

There's a configuration option for db_sqlite which is redundant. It should just use sqlite unless there's a MySQL relation (which is pretty much what happens currently).

Baring actually verifying it works with Firefox and an updated readme this charm looks good to me. Great job!

Changed in charms:
status: New → Incomplete
Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

Fixed the read me. Removed nit-pick on sqlite.

Confirmed that it works. I suspect that the issue is with using the wrong port.

Changed in charms:
status: Incomplete → New
Marco Ceppi (marcoceppi)
Changed in charms:
status: New → Fix Released
Revision history for this message
Marco Ceppi (marcoceppi) wrote :

Commenting to drop from the review queue

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.