-
Notifications
You must be signed in to change notification settings - Fork 53
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
Give clearer explanations for Jupyter tutorial #53
Conversation
@@ -3,7 +3,16 @@ | |||
Copy Jupyter App | |||
================ | |||
|
|||
We will begin by copying a pre-built Jupyter app to hit the ground running. | |||
We will hit the ground running by first copying over a pre-built example Jupyter app. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hit the ground running begin
to: | ||
|
||
- get a working Jupyter app running at your center | ||
- introduce you to app development and make you an Interactive App developer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the purpose of the tutorial is to "introduce you to app development and make you an interactive app developer" the first thing in the tutorial I would do is enable app development mode.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example, https://osc.github.io/ood-documentation/master/app-development/enabling-development-mode.html#b-enable-for-specific-users-using-custom-initializer provides a simple way to enable app development for one user (or one subset of users).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't recommend enabling app development to sys admins who just want to build apps for their center, until we hide the development dropdown from users.
If this is a sandbox Interactive App (Dashboard plugin), then it can be | ||
accessed by navigating to:: | ||
|
||
https://ondemand.my_center.edu/pun/sys/dashboard/batch_connect/dev/<app_directory>/session_contexts/new |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This note is perfect for the start of an Overview section.
We can Create a new section called "Overview" in App Development and add this block. Then soon we can add more stuff to "Overview".
Where you replace ``ondemand.my_center.edu`` with your domain. | ||
|
||
*Keep this link handy as you will want to access it everytime you make | ||
changes to the app code to test your changes.* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So if we require enabling app development first, will that remove the need to have this explanation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but see my comment on this above.
Also, if we do enable app development mode, we can remove this, but we'd have to add more documentation on how to use the app developer tools.
I'm going to merge this now, opened a separate issue to add changes later: #57 |
Fixes #52
Be sure to merge in master, release-1.1, and develop.