Skip to content

Redirect hub.dandiarchive.org to docs.dandiarchive.org/user-guide-using/dandi-hub - #2877

Closed
asmacdo wants to merge 3 commits into
dandi:masterfrom
asmacdo:redirect-hub-to-notebooks
Closed

asmacdo wants to merge 3 commits into
dandi:masterfrom
asmacdo:redirect-hub-to-notebooks

Conversation

@asmacdo

@asmacdo asmacdo commented Aug 4, 2026 •

Copy link
Copy Markdown
Member

CAUTION: ORDER MATTERS

  1. Merge the graveyard page Hub graveyard page dandi-docs#243
  2. This PR merges and deploys. Open question for @waxlamp: retarget this at release?
  3. Add hub.dandiarchive.org as a domain alias on the redirect project in Netlify.
  4. Add the Route53 record in dandi-infrastructure: CNAME hub -> redirect-dandiarchive-org.netlify.com
    github.com/Point hub.dandiarchive.org at the Netlify redirector dandi-infrastructure#282

Redirects hub.dandiarchive.org to 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:

  1. The gui netlify project (the one that does the redirect) deploys release, which is ~120 commits behind master, so merging here doesn't activate anything until the next release. Should I open this against release instead?
  2. I've deleted the R53 route for now. Once this merges, I'll add the DNS record back, and then add hub.dandiarchive.org as a domain alias on the redirect project in Netlify. (infra PR instead)

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>
@kabilar

kabilar commented Aug 5, 2026

Copy link
Copy Markdown
Member

Thanks @asmacdo.

  1. The gui netlify project (the one that does the redirect) deploys release, which is ~120 commits behind master, so merging here doesn't activate anything until the next release. Should I open this against release instead?

It would be ideal to get this released soon. Please discuss with @waxlamp regarding the best approach.

2. I've deleted the R53 route for now. Once this merges, I'll add the DNS record back, and then add hub.dandiarchive.org as a domain alias on the redirect project in Netlify.

It would be best to submit this change to dandi-infrastructure.

@kabilar
kabilar marked this pull request as ready for review August 5, 2026 15:03
Comment thread redirector/netlify.toml Resolved
@kabilar
kabilar requested review from jjnesbitt and waxlamp August 5, 2026 15:21
Co-authored-by: Kabilar Gunalan <kabilar.gunalan@gmail.com>

@yarikoptic yarikoptic left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

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!

Comment thread redirector/netlify.toml Resolved
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
@asmacdo asmacdo changed the title Redirect hub.dandiarchive.org to notebooks.dandiarchive.org Redirect hub.dandiarchive.org to docs.dandiarchive.org/user-guide-using/dandi-hub Aug 12, 2026
@asmacdo
asmacdo marked this pull request as draft August 12, 2026 21:41
@asmacdo

asmacdo commented Aug 12, 2026 •

Copy link
Copy Markdown
Member Author

Back to draft until dandi/dandi-docs#243 merges

@waxlamp

waxlamp commented Aug 13, 2026

Copy link
Copy Markdown
Member

@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.

@asmacdo

asmacdo commented Aug 13, 2026

Copy link
Copy Markdown
Member Author

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.

@yarikoptic

Copy link
Copy Markdown
Member

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

@waxlamp

waxlamp commented Aug 14, 2026

Copy link
Copy Markdown
Member

Closing in favor of #2888. Long story and it's late on a Friday afternoon 😩

NEStock pushed a commit to aplbrain/dandi-infrastructure that referenced this pull request Oct 26, 2026
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>
NEStock added a commit to aplbrain/dandi-infrastructure that referenced this pull request Oct 27, 2026
* 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>
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