I speak about the Mageia instance of MADB.
This application is build on top of Symphony 1.4 which no more supported by Symphony since 2012. Thus there is a big need to migrate it.
Migrating to Symphony 2 or above is not straight. What I have found about such a migration can resumed to: rewrite all from scratch!
Thus we have to rewrite the application from scratch. In this case, we have the choice of the technology:
PHP based like Laravel, Symphony...
JS based like NodeJS...
Python based like Django or Flask...
Actually, the system works with its database, which is synchronized with Sophie. In the event of a rewrite, I'd rather see a direct reading of the metadata. And in this case, it would seem wise to start with an application built in Python with Flask or Django. This would give direct access to the functions provided by the rpm bindings.
What are your thoughts about that?
I speak about the Mageia instance of MADB. This application is build on top of Symphony 1.4 which no more supported by Symphony since 2012. Thus there is a big need to migrate it. Migrating to Symphony 2 or above is not straight. What I have found about such a migration can resumed to: rewrite all from scratch! Thus we have to rewrite the application from scratch. In this case, we have the choice of the technology:
Actually, the system works with its database, which is synchronized with Sophie. In the event of a rewrite, I'd rather see a direct reading of the metadata. And in this case, it would seem wise to start with an application built in Python with Flask or Django. This would give direct access to the functions provided by the rpm bindings. What are your thoughts about that?