Repository navigation
Conversation
The DandiHub JupyterHub has been taken down. Redirect its hostname to notebooks.dandiarchive.org so visitors land somewhere useful instead of hitting a TLS error. All hub URLs were JupyterHub session paths with no equivalent on the notebooks site, so this drops :splat and sends every request to the root. A 302 is used rather than a 301 while the decision to retire the hostname permanently is still open. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Thanks @asmacdo.
It would be ideal to get this released soon. Please discuss with @waxlamp regarding the best approach.
It would be best to submit this change to |
Co-authored-by: Kabilar Gunalan <kabilar.gunalan@gmail.com>
yarikoptic
left a comment
There was a problem hiding this comment.
redirect is a nice idea but I think it should be redirected to some page describing why/where instead of dumping into a new cold bucket....
I think anyways we need to add to https://docs.dandiarchive.org/developer-guide/creating-dandi-instance/dandi-hub/ the announcement that as of Aug 1 Hub is being deprecated and users are invited to use google collab and visit our notebooks.d.o -- that is where it should be, not here!
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
|
Back to draft until dandi/dandi-docs#243 merges |
|
@asmacdo, @kabilar: there might be a simpler option here: revive the infrastructure for hosting a web application at hub.dandiarchive.org, but replace it with a simple, static page that explains that the hub has been deprecated, and either redirects the user (after a delay) to wherever they should go next (the notebooks site, or the docs), or else just presents them with both links (and they can choose). That resolves the issue of where to send the user (that Yarik raised), it provides a more graceful experience for the user, and it avoids adding redirect logic to this repository (which won't work right away; we would need to add back the DNS entry and have it point to the Netlify app, etc. etc.). Let me know what you think. |
|
I have added the redirect in an infrastructure PR, and can add the netlify when we are ready. I lean that way so we don't have another thing we have to host (even a small static page) but I don't have a strong opinion. Whatever we do I'd like to get to consensus and be done with it. |
|
I am ok either way (redirect or a page), only that with page we would gain one more page to maintain etc. IMHO pointing to docs page should be enough and would remove the need for one more thing to maintain |
|
Closing in favor of #2888. Long story and it's late on a Friday afternoon 😩 |
Do not apply until dandi/dandi-archive#2877 is deployed, or the redirector will answer for hub without a matching redirect rule. Ref: dandi/dandi-hub#296 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Add DNS records for notebooks and stats subdomains Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Point hub.dandiarchive.org at the Netlify redirector Do not apply until dandi/dandi-archive#2877 is deployed, or the redirector will answer for hub without a matching redirect rule. Ref: dandi/dandi-hub#296 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Fix the Route53 record and move it to its own file * Set webdav server quantity to 0 Scale down the webdav server quantity to 0. * Map all redirected subdomains to the redirector app directly * Add `.DS_Store` to `.gitignore` * comment out unused redirect * more commenting out unused code * trigger terraform plan --------- Co-authored-by: Kabilar Gunalan <kabi@mit.edu> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Jacob Nesbitt <jjnesbitt2@gmail.com> Co-authored-by: Austin Macdonald <austin@dartmouth.edu> Co-authored-by: Roni Choudhury <roni.choudhury@kitware.com> Co-authored-by: Mike VanDenburgh <37340715+mvandenburgh@users.noreply.github.com>
CAUTION: ORDER MATTERS
release?hub.dandiarchive.orgas a domain alias on the redirect project in Netlify.hub->redirect-dandiarchive-org.netlify.comgithub.com/Point hub.dandiarchive.org at the Netlify redirector dandi-infrastructure#282
Redirects
hub.dandiarchive.orgto the DANDI Hub retirement notice in the docs, per @yarikoptic's suggestion.302 rather than 301 in case we need to use the subdomain again.
Two questions:
release, which is ~120 commits behindmaster, so merging here doesn't activate anything until the next release. Should I open this againstreleaseinstead?Once this merges, I'll add the DNS record back, and then add(infra PR instead)hub.dandiarchive.orgas a domain alias on the redirect project in Netlify.