novacut-0 => dmedia-0

Bug #1020491 reported by Jason Gerard DeRose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Novacut
Triaged
High
Unassigned

Bug Description

Been thinking on this for a while: I think we should move the docs we currently store in novacut-0 into the dmedia-0 database. There are few reasons for this:

1) Replication - novacut-0 doesn't contain much, but it does contain stuff that we want to *always* continuously replicate to your other local devices. It would be better to only have one such database (we definitely want to always continuously replicate dmedia-0).

2) Eliminate redundancy - the render server needs the dmedia/file doc for each source file, and currently we copy them into novacut-0, which is kinda silly

3) Consistency - when a render job finishes, we currently update both docs in novacut-0 and dmedia-0. Things will be a lot more sane if we stay in one database.

4) Jobs - we're going to start dispatching jobs through dmedia, and as jobs are basically what we use novacut-0 for, makes sense to put all this stuff in dmedia-0.

Note that your actual edit projects are *not* stored in novacut-0. Each Novacut project gets its own CouchDB database, novacut-0-<random_id>

Changed in novacut:
milestone: 12.07 → 12.08
Changed in novacut:
milestone: 12.08 → 12.09
Changed in novacut:
milestone: 12.09 → 12.10
Changed in novacut:
milestone: 12.10 → 12.11
Changed in novacut:
milestone: 12.11 → 12.12
Changed in novacut:
milestone: 12.12 → 13.01
Changed in novacut:
milestone: 13.01 → 13.02
Changed in novacut:
milestone: 13.02 → 13.03
Changed in novacut:
milestone: 13.03 → 13.04
Changed in novacut:
milestone: 13.04 → 13.05
Changed in novacut:
milestone: 13.05 → 13.06
Changed in novacut:
milestone: 13.06 → 13.07
Changed in novacut:
milestone: 13.07 → 13.08
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.