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

Add base documentation #91

Merged
merged 20 commits into from
Mar 31, 2017
Merged

Add base documentation #91

merged 20 commits into from
Mar 31, 2017

Conversation

danlamanna
Copy link
Contributor

@danlamanna danlamanna commented Feb 9, 2017

Addresses #35 and #77

Nothing to review here yet @kotfic, but we can use this PR as a means of discussing a TOC and collaborating on docs.

I'm thinking a baseline TOC could look something like this:

* What is Geonotebook
** Goals
** Architecture
* Installation
** Basic Install
** Development Install
** Vagrant
** Docker
* User Documentation
** Walkthrough (example notebooks)
* Developer Documentation
** API Docs
** Adding an RPC call
*** Server Side
*** Client Side

@danlamanna
Copy link
Contributor Author

Part of this PR should be adding sphinx docs to each of the user facing commands on the M object so M.set_center? (for example) within the notebook will provide good docs.

@danlamanna danlamanna force-pushed the formal-documentation branch 2 times, most recently from 464121c to b9ff0b3 Compare March 8, 2017 20:13
@danlamanna danlamanna force-pushed the formal-documentation branch from b9ff0b3 to eaeadd4 Compare March 30, 2017 15:15
@danlamanna danlamanna changed the title [WIP] Add base documentation Add base documentation Mar 30, 2017
@danlamanna
Copy link
Contributor Author

@jbeezley PTAL

Note once this is merged, @dorukozturk can delete the S3 bucket we were previously relying on for geotiffs.

When you execute python in a Jupyter Notebook cell the python code was transmitted (as a string) over a web socket to the webserver, then proxied through ZeroMQ to the IPykernel where it was evaluated as a Python expression. The results of that execution are then sent back over the ZeroMQ/Websocket connection and displayed in your browser. This is the standard way in which Jupyter notebook takes code from a web browser, and executes it in an interactive shell (kernel) and returns the output.


*TODO introduce comm channels*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@danlamanna are we planning to keep TODO's?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can, or we can put them inside an issue with a checklist. It's up to us.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My slight preference to put them inside an issue with a checklist if it is not too much work but I am okay with this as it is (if you want to go ahead and merge it).

@danlamanna
Copy link
Contributor Author

related: #111

@danlamanna danlamanna merged commit d9a89de into master Mar 31, 2017
@danlamanna danlamanna deleted the formal-documentation branch March 31, 2017 18:46
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

Successfully merging this pull request may close these issues.

4 participants