Bitweaver - Webtrees

Do I actually need access to the data in webtrees? On one hand probably not and keeping it as a stand alone package is probably the proper decision to make, and simply include the sqlite database file in the nightly backups. So simply mapping the webtrees data folder into the Bitweaver storage one may be all that needs to be done. However one element of this is the management of the media and providing different displays of galleries is poorly done in webtrees as it is in PhpGedView and it is this element that I would like to manage under Bitweaver. I have a large archive of images here which I need some way to display and ask for help from family members in identifying people in them which is another item on the longer road map that I am working towards.

Starting point code wise is on github but what is a bit of a problem is that this is now based off laravel having dropped ADOdb as the database abstraction layer. I'm getting too old to get involved with a new framework especially since it does not natively support Firebird. There is a laravel-firebird driver which is fairly up to date but I am a little lost on just how to merge that with the webtrees code. It may well be that plugging the remaining holes in the PhpGedView port is still the best way forward.

Webtrees itself is a nice package stand alone. There are some notes about migrating from older versions which includes a note about migrating from PhpGedView, but the comment that you don't need a working copy of PhpGedView to carry it out perhaps misses the point. My own 'migration' simply required tidying the raw GEDCOM file so that in was imported cleanly and correctly accessed the existing media folder. There is no need to access the PhpGedView database as the indexes are built clean. What I have even done is imported the new GEDCOM file back into the my live PhpGedView and this now includes the extra deaths that I have not been able to add directly. This gives me a breather in deciding what to do next ...