-
Notifications
You must be signed in to change notification settings - Fork 6
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
The name of this repository doesn't make sense #1
Comments
we could add an alias, similar to: http://dashboard.obofoundry.org/ http://nor-dashboard.obofoundry.org/ or What would you prefer? |
|
Ok! Sounds good to me. @jamesaoverton where is the right place to add such a redirect? |
@matentzn Hmm. I think this would have to be handled in the obo-dash.github.io repo. We're using GitHub pages, which does not give us access to HTTP server configuration that I would usually use for a redirect. But it should somehow be possible to return an HTML page with a |
Oh ok, yeah I can see now in the settings of the main obo dashboard that its deployed to dashboard.obofoundry.org.. Its low prior, but maybe we can find a way to deploy the nor dashboard in the same way? What are the steps I would need to take to deploy this dashboard at dashboard-nor.obofoundry.org (sorry @cthoyt I cant think of another way to phrase it that is concise and can be descried as a subdomain). |
We would need to update the DNS configuration. That's easy enough. What is the advantage of having a subdomain for this? |
It just stands a bit outside the usual obofoundry.org infrastructure - I think it would be nice while trying to operationalise the review discussion process to have the NOR board be part of the normal architecture rather than standing on the side of it. obfoundry.org is also less prone to changes in URLs, so a link to the NOR dashboard would be more stable if we were to include it in various other docs. |
Since this is inside the obofoundry organization, it means you have to access it via https://obofoundry.github.io/obo-nor.github.io. It would make sense if this were in a different organization called
obo-nor
so you could actually access it as https://obo-nor.github.io. Maybe it would be better to give this a more descriptive nameThe text was updated successfully, but these errors were encountered: