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

Define custom domain for GitHub Pages deployment #109

Closed
kabilar opened this issue Jan 17, 2025 · 3 comments · Fixed by #110
Closed

Define custom domain for GitHub Pages deployment #109

kabilar opened this issue Jan 17, 2025 · 3 comments · Fixed by #110

Comments

@kabilar
Copy link
Member

kabilar commented Jan 17, 2025

https://dandi.github.io/example-notebooks/

See discussion here.

cc @bendichter

@bendichter
Copy link
Member

bendichter commented Jan 24, 2025

@kabilar this URL was set simply by activating Pages in the Settings of this repository. The default behavior (if the repo name is not [org].github.io) is to use the url http://[org].github.io/[repo]

Image

The advantage of this for anyone who knows this convention they can clearly see from the url where the repo is. However, I would be fine with moving this either by assigning a custom domain, or by moving this entirely into the Hugo site generation, if that is possible.

@kabilar
Copy link
Member Author

kabilar commented Jan 24, 2025

Hi @bendichter, this was previously using: https://www.dandiarchive.org/example-notebooks. See #93 (comment). That's why I was trying to figure this out.

I am fine with using https://dandi.github.io/example-notebooks/, Hugo, or notebooks.dandiarchive.org.

@kabilar kabilar reopened this Jan 24, 2025
@kabilar
Copy link
Member Author

kabilar commented Jan 24, 2025

For now, let's proceed with https://dandi.github.io/example-notebooks. Filed dandi/dandi-docs#171

@kabilar kabilar closed this as completed Jan 26, 2025
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 a pull request may close this issue.

2 participants