-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API for JVS postgres database #172
Comments
In January I began looking into this specifically. The existing JVS architechture is fairly dated (written in Perl!) which is a pretty big impediment to getting new people to help develop it. On the other hand, Vlasisku is designed in a fairly modern way (using Flask written in Python). That said, the best route for JVS2 is to slowly give Vlasisku more and more features, until it can function in tandem with JVS. At that time, using JVS can be deprecated, and be decommissioned some time later. The first step to making Vlasisku replace JVS is to give it direct access to the database (at first in a readonly way, pe'i). It will thus always be up to date. Building an API for querying the database would be very easy with Flask. I had started work on having Vlasisku interact directly with the database, rather than use XML dumps, but got sidetracked with school and other projects. Hopefully over the summer I'll have more time to work on it! |
API is more important to me than any GUI. Just plugging it directly to the 2015-06-11 18:22 GMT+03:00 Jacob Thomas Errington [email protected]
|
The title of the issues might be misleading. It's not about JVS but about JVS postgres database. |
Develop an API for JVS that is able to read and writ to the db. This will also make almost all JVS 2.0 issues and proposals not relevant since they can be implemented in separate projects using this API.
The text was updated successfully, but these errors were encountered: