[
https://jira.duraspace.org/browse/DS-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27645#comment-27645
]
Mark H. Wood commented on DS-1456:
----------------------------------
We already supply a <meta name="Generator" content="DSpace $VERSION">. We
could extend that with the UI's name.
If we can settle on a REST implementation, we could create space for things
like this. (Are there any standards for a service to describe itself,
extensibly, in a RESTful way?)
Tomcat Manager and the like must be installed as "privileged" contexts in order
to see other contexts. We'd have to provide a servlet to run in a privileged
context, and then ask it for DSpace instances, and then sort through them
looking for the one we're configured for. Much easier just to ask it for a
page that contains the information. And I can imagine many sites questioning
whether they should allow even a piece of DSpace to run in a privileged context.
Whatever we choose is going to be unsatisfactory, because we're asking a
process to tell us something about some other process' context. We have to
talk to the other process to know what it is.
Suppose, for the short term, we just spit out the value of dspace.url and let
people figure it out from there?
> "dspace version" command-line script
> ------------------------------------
>
> Key: DS-1456
> URL: https://jira.duraspace.org/browse/DS-1456
> Project: DSpace
> Issue Type: New Feature
> Reporter: Ivan Masár
> Assignee: Mark H. Wood
>
> We should provide a "[dspace]/bin/dspace version" script, which would gather
> the basic information about DSpace and its environment that is necessary to
> ask questions on dspace-tech.
> This information includes most prominently:
> * DSpace version
> * OS version
> * UI(s) used
> * is Discovery enabled?
> somewhat less often important:
> * JDK version
> * ant version
> * maven version
> * path to DSpace
> Optional flags could produce even more information, pulled from
> configuration, e.g. database configuration, hostname/URL configuration,
> authentication configuration (with passwords omited), etc.
> Most of this information is already available in the XMLUI admin Control
> panel, so some of those methods could be reused.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
