Replies: 2 comments
-
|
@Ev2geny we are adding support in the next day or two that you can create a notebook that is backed/synced by a GitHub URL. This currently will just be the single URL for now, but later will expand to the full repo. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@mscolnick , excellent, than you! I am waiting for this! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear all,
my goal is to share a marimo notebook in the app mode in the molab.marimo.io
My questions is: what would be the correct workflow to maintain marimo notebook on molab in synch with github and to make sure, that the URL stays consistent?
My initial though was to follow instructions on https://molab.marimo.io/github and then the link to this github repository https://github.com/Ev2geny/marimotest1/blob/main/marimotest1.py becomes this one https://molab.marimo.io/github/Ev2geny/marimotest1/blob/main/marimotest1.py, which I could share with users.
The problem with this approach is that if a user wants to open a notebook in the app mode, than the user has to do the following:
1)Fork my notebook from github to his own separate instance in molab (before that create an account, if not done yet)
2) Run that notebook
3) Switch to the app mode
This is all doable, but just takes way too much steps. Plus the moment I publish a new version, the user has to do all these steps again (which will create a fork of my notebook on his molab account).
Then I found, that I can share already published by myself notebook in the app mode via the molab manu:
So, the link to the notebook, which I would share becomes like this: https://molab.marimo.io/notebooks/nb_pcXjRxXkmAF5CscfVV5niH/app
This works fine, but now the question is how to synch the notebook in molab with the notebook on github / my hard drive.
If I just follow initial procedure with the new version, this will create a new instance of the notebook on molab, with the different URL, which is not what I want.
So far I found the following workflow to update existing molab notebook:
To go https://molab.marimo.io/notebooks and shutdown the notebook in question, if it is running.
In molab go to edit mode and load a new version of the notebook via the file menu
Via the file menu delete the old notebook.py file
Via the file menu rename the newly uploaded file to notebook.py
So, that all seems to be working, but I am just wondering whether there is any better procedure?
Also, the next question would be how to keep things in synch, if there are more files, then just notebook.py, but this is another question.
Beta Was this translation helpful? Give feedback.
All reactions