[
https://issues.apache.org/jira/browse/OPENMEETINGS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251445#comment-13251445
]
SebastianWagner commented on OPENMEETINGS-111:
----------------------------------------------
10) Should we add guard against multiple installations?
=> I think you might open a new Issue for that, I think such a check should
cover a wider area:
The check should also be performed if the installation was not done yet, so if
you goto:
localhost:5080/openmeetings in your browser and there db is empty, then the
application should not load (but maybe redirect to webinstaller).
Also if the installer detects that you run it allready, then you it should not
run twice. The installer produced a file called "install.xml" in the conf
directory to keep track on installation progress. You could re-use that file in
the CLI installer. So if a user wants to re-install he needs to delete that
file.
> Command line admin need to be created
> -------------------------------------
>
> Key: OPENMEETINGS-111
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-111
> Project: Openmeetings
> Issue Type: New Feature
> Components: Converters
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: Maxim Solodovnik
> Assignee: Maxim Solodovnik
>
> It should be able to install/backup/restore OM
> java -jar ...openmeeting.jar CommanLineAdmin -c install -smtp.server
> localhost -smtp.port 25 -language english
> java -jar ...openmeeting.jar CommanLineAdmin -c backup -file mybackup.zip
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
