View Single Post
Old 05-14-2017, 01:11 PM   #189
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by kovidgoyal View Post
@eschwartz: There is currently no way to run the GUI against a server. That is do-able in principle, but requires a lot of work to get right, so it's something for the future. Currently if you want to run the server as a service and the GUI on the same machine, you need to do what I suggested earlier. Create a wrapper script that stops the server before running the GUI and restarts it after quitting. You can have the GUI autostart its embedded server so that the server is down for only a few seconds.
I somehow figured as such.

I'd very much appreciate such a feature before the beta graduates...
Though I suppose I can simply stop/start the service in the same wrapper script I already use for debug logging anyway, still, that is a bit of an ugly workaround which shouldn't be required in production releases.

Quote:
FYI: You should use http://127.0.0.1 not 0.0.0.0 as the server IP address.
Is this like a "calibre won't work" thing, or a best-practices-when-referencing-localhost thing? Because zeroes are easier to type really really fast.

...

It did highlight the fact that using `calibre-debug -g` doesn't seem to have a way to specify the library to start up with the way the main executable does, though whether that is urgent in the backdoor debug version is questionable.

Quote:
That error is caused by an outdated version of mechanize, you need version 3.3
Huh, so it is. I notice you have saved me the effort of flagging it out of date on https://www.archlinux.org/packages -- rebuilding it myself got it to work, despite my use of 0.0.0.0.
eschwartz is offline   Reply With Quote