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 initial build for RTD #1

Closed
willingc opened this issue Apr 10, 2017 · 3 comments
Closed

Add initial build for RTD #1

willingc opened this issue Apr 10, 2017 · 3 comments
Assignees

Comments

@willingc
Copy link
Collaborator

Add initial structure and deployment to RTD.

@willingc willingc self-assigned this Apr 10, 2017
@choldgraf
Copy link
Member

choldgraf commented Apr 10, 2017

hey - I sent a message about this a little bit ago on slack, is that not a good place to reach you? it's currently deployed to:

http://zero-to-jupyterhub.readthedocs.io/en/latest/

@willingc
Copy link
Collaborator Author

Hey @choldgraf, What channel did you send it to? I didn't get it though I will be the first to admit that I'm not tied to any social media. Gitter is usually better or better yet an issue with an @-mention.

Deployment looks fine. We do need to modify the title on readthedocs to be specific to k8s. There's a few other housekeeping items related to hosting on readthedocs and how we typically structure and build the Jupyter docs.

I'm going to close this and I'll leave some other issues tomorrow as I'm about done for my day ;-)

@choldgraf
Copy link
Member

sounds good! I sent it to you as a DM on the uc-jupyter slack channel, but I'll use gitter from now on.

Def other updates to make on these docs (also there's the dopey logo that I threw together just because I needed something to put there...that should probably be updated with something official)

yuvipanda referenced this issue in yuvipanda/zero-to-jupyterhub-k8s Sep 18, 2017
willingc pushed a commit that referenced this issue Feb 28, 2018
Explain auth.github.org_whitelist
willingc added a commit that referenced this issue Apr 6, 2018
Clarify that JupyterHub on OpenShift is a different project
manics referenced this issue in manics/zero-to-jupyterhub-k8s Dec 6, 2018
# This is the 1st commit message:

Move travis install/script into ci/ scripts

chartpress was failing with an error (exit 1) but travis did not detect the non-zero exit code and continued, leading to errors when z2jh was deployed trying to run the non-existent image `jupyterhub/k8s-hub:generated-by-chartpress`

# This is the commit message #1:

Source env vars in travis-script.sh
consideRatio pushed a commit that referenced this issue May 29, 2019
Fix azure cli VMSSPreview feature register command
consideRatio pushed a commit that referenced this issue Nov 25, 2019
minrk pushed a commit that referenced this issue Sep 8, 2020
Fix syntax errors and avoided a potential bug.
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