Part 5: turn on the peering
Bug #1067298 reported by
Jason Gerard DeRose
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Dmedia |
Fix Released
|
Critical
|
Jason Gerard DeRose | ||
Bug Description
The last step is to actually have the peering functionality turned on in the live application.
dmedia-service will listen for peering offers when it has the user private key (because without that, it can't issue machine certificates for new devices).
dmedia-gtk has a trial implementation of the first-run dialog, and I'll shortly turn on the same in novacut-gtk. There are a few rough edges still, but that's why I want to get this through the daily builds and get people to help us test.
Related branches
lp:~jderose/dmedia/all-in
- Jason Gerard DeRose: Approve
-
Diff: 5039 lines (+2468/-1581)23 files modifieddmedia-cli (+2/-2)
dmedia-gtk (+4/-3)
dmedia-service (+111/-20)
dmedia/core.py (+13/-26)
dmedia/gtk/peering.py (+66/-9)
dmedia/gtk/ui/client.html (+10/-12)
dmedia/httpd.py (+1/-1)
dmedia/parallel.py (+42/-0)
dmedia/peering.py (+298/-439)
dmedia/server.py (+301/-205)
dmedia/service/__init__.py (+24/-5)
dmedia/service/avahi.py (+74/-81)
dmedia/service/peers.py (+324/-24)
dmedia/service/tests/test_avahi.py (+54/-20)
dmedia/startup.py (+45/-45)
dmedia/tests/couch.py (+3/-1)
dmedia/tests/test_core.py (+20/-59)
dmedia/tests/test_peering.py (+419/-324)
dmedia/tests/test_server.py (+559/-190)
dmedia/tests/test_startup.py (+92/-111)
run-browse.py (+2/-1)
run-publish.py (+3/-3)
setup.py (+1/-0)
| Changed in dmedia: | |
| status: | In Progress → Fix Committed |
| Changed in dmedia: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
