Create a "file-based" discovery backend about commuter HOT 4 OPEN

@rgbkrk Is there any documentation on information on what and how the discovery api works ?

from commuter.

Right now there's only GET for the discovery API, with a particular elasticsearch setup for it. It's largely intended to be a way to promote the content in the "browse" section.

What you posted within the nteract repo I'm pretty well on board with. I've even started mocking up the idea of a true publishing endpoint with versions, etc. I'm heading off to bed now, I'll post some of my sketches tomorrow. Super interested in this.

I would like to see auth on the server before tackling this though. ¯\_(ツ)_/¯

from commuter.

On a side note, we should make the UI not show discovery if its not enabled.

from commuter.

Ok now I understand the purpose of the Discovery feature.
I can certainly see the need for authentication. Especially in my current situation where the notebooks will need to be scoped to only people with access. However this raises another potential thought. What if we provided a way to have a notebook be public or private . Should the notebook be private maybe provide authentication requirements to access the notebook. I mainly work with the nuxtjs framework, nearly parallel to nextjs.

They have authentication solutions in their examples, but not too sure about nextjs.

from commuter.