Skip to content
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

[deepnote] Share notebooks with 'execute' permissions #152

Closed
RussTedrake opened this issue Sep 5, 2021 · 2 comments
Closed

[deepnote] Share notebooks with 'execute' permissions #152

RussTedrake opened this issue Sep 5, 2021 · 2 comments
Assignees

Comments

@RussTedrake
Copy link
Owner

RussTedrake commented Sep 5, 2021

Posted as a suggestion here:
https://community.deepnote.com/c/suggestions/output-cells-for-anyone-with-the-link-can-execute-this-project?

I'm also quite happy to hear that this is not a good idea!

@danzvara
Copy link
Collaborator

danzvara commented Sep 7, 2021

🙏 I replied in the community, but TLDR is that shared outputs are quite central to many collaboration workflows - there should be a simpler solution to get around the tunnel link sharing issue.

@RussTedrake
Copy link
Owner Author

Thanks! Your answer also made me realize that execute sharing is a potentially awesome, but different feature -- if all users executing the notebook are running on the same provisioned machine, then things get complicated. Each time the cell with StartMeshcat is run, it will try to start a server on the 8080 port. If that fails, it will go to another ngrok port, etc.

Even if all users point their browser to the deepnote project id url, then the render will get whichever server was successfully launched at the 8080 port, and all of the sliders across different users will interact.

Long story short -- this is good to know. I'll stick with the "Duplicate" workflow!

RussTedrake added a commit that referenced this issue Sep 8, 2021
Now that #148 and #152 are resolved.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants