-
Notifications
You must be signed in to change notification settings - Fork 785
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
Comments
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: |
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 ;-) |
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) |
Generalization cleanup #1
Clarify that JupyterHub on OpenShift is a different project
# 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
Fix azure cli VMSSPreview feature register command
Fix syntax errors and avoided a potential bug.
Add initial structure and deployment to RTD.
The text was updated successfully, but these errors were encountered: