Quote:
Originally Posted by goge
Sooo... did some work last night. I'm going to have to scrap the plugin idea.
|
I agree
that's why I'm going to implement it in the content server.
My non-graphical/no ui plugin didn't seem to have access to the db, and didn't seem to start when only starting the content server.
Starting multiple web servers also seems like a waste when the content server already starts up a cherrypy server.
Is the content server extensible with plugins? At a glance it doesn't seem to be. It seems the easiest way to add new functionality would be to add endpoints to ajax.py or create a new class used with the LibraryServer.
At first I'm only going to be adding an endpoint that takes an isbn parameter and adds it to the db and schedules a metadata update similar to the ui. Once that is done I might also add an endpoint to edit existing metadata.
So should I add the functionality to ajax.py and create a new 'web app' similar to browse.py or add the functionality to browse as well?