You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess the GENIE example might change in the future (as we might have a single instance), but it would still be useful that the news route would go to the configured news page for other local installations
There might be a configuration property already as the current News button on genie.cbioportal.org does go to the correct page
The text was updated successfully, but these errors were encountered:
@inodb in the application.properties file, to the skin.documentation.news property, the .md file assigned based on the instance [ex. News.md for cbioportal.org/news and News-Genie.md for genie.cbioportal.org/news], is likely the configuration property currently used.
A proof of which can be found in here.
And this PR 4342 does the rest of frontend task.
For any local instance as long as the documentation is followed, I believe this logic would work, do you still suggest setting up of a new configuration for /news route?
e.g.
cbioportal.org/news -> https://docs.cbioportal.org/news/
genie.cbioportal.org/news -> https://docs.cbioportal.org/news-genie/
I guess the GENIE example might change in the future (as we might have a single instance), but it would still be useful that the news route would go to the configured news page for other local installations
There might be a configuration property already as the current News button on genie.cbioportal.org does go to the correct page
The text was updated successfully, but these errors were encountered: