Closed russss closed 7 years ago
If I remember correctly, the sticking point I hit with this is that the Flourish framework errors out if there are tables in the database it doesn't know about. This isn't great so we need a way of working around this.
(As a nasty hack, could we have the django tables in a different postgres schema to the flourish ones?)
Separate schema sounds good to me.
I've given up on the separate schema plan as neither Flourish nor Django copes well with schemas. Instead, I've patched Flourish to only look at a chosen subset of tables with c6a01ab
I think this is complete. The first thing I'm going to migrate is storage-requests-cron.php from #147.
We'd like to start the python migration by having a django app running, in parallel with the PHP app. I've made a start on this in the
python
branch. Let's just get the minimum possible working first and running on live, authentication is in #143.