I’m having a little trouble following what you are saying in some parts, and this is probably because I only run your notebook from your launch binder
button. (In fact, I only ever run Voila online served by MyBinder.) I think I follow along most of your questions and so let me try to address them:
A: I’m not sure you got the idea you need this? Or where you got that such code belonged in your notebook.You don’t need it for Binder, at least, as the installation also enables Voila. You should look at other Voila deployments and model your code after them. Especially if they are close to what you are trying to do, such as this bear classifier that the fastai folks provide that runs on MyBinder via the launch badge. Ideally, get the originals working in your own repo so that you know the backing tech is handled and then adapt them to use your code. The Voila folks made an entire gallery of examples available that is backed by Binder launches. You can go to the source repositories of any of them by pressing the Source
button below the description that links to the launch.
And if you were working with a less fancy extension that did need enabling, a command like that to enable it would go in the postBuild
configuration files, (or possibly start
), see this example repo and more about config files here.
I’m unsure why you would need this? I think this works in MyBinder, but I haven’t checked. And from the commit where that flag was added it looks to me that it just allows some logging when you launch from the terminal using the voila command. That last part is a very important distinction. It is meant to be used when you launch from the command line, which you don’t use when running from MyBinder.
You see the errors by running it in the notebook mode as I tried to direct you last time. If you can Run all
on your notebook in notebook mode and test all the features and options then your code should run cleanly in app mode, too. In other words, you’ll be debugging in the notebook mode so there is not any real need for voila --debug
. I should add though that this is being said by someone who only runs Voila in sessions on MyBinder. Maybe running on the command line locally using voila --debug
adds some benefits of which I am unaware.
A: As for the URL needed to launch the app direct, it should work now. I think you had that !jupyter serverextension
line messing things up before. For others trying to form the URL to do this, I have several examples of launching direct in my own repo here.