dmitri-carpov/rays

Liferay development and deployment management tool

rays's Issues

Synchronize different database types

rays sync won't work if environments use different database types.

Oracle support

Add oracle database support.

Add content synchronizers

Create advanced content synchronizers.
rays deploy content-sync
should create/update organizations
should push structures, templates, vocabularies, categories per organization or in global.

Enabling of developer properties in the environments.yml

It would be nice if rays could be configured to ask Liferay to load the portal-developer.properties file when starting the Liferay service. In the past I've prefixed the following JAVA_OPTS snippet in front of the tomcat startup script.

JAVA_OPTS="$JAVA_OPTS -Dexternal-properties=portal-developer.properties"

Remote liferay commands no longer work

> rays version
1.1.5
> rays --debug liferay --force stop
environment: test
stopping server
failed to stop the server
reason: undefined local variable or method `remote' for #<Rays::Service::ApplicationService:0x00000000cc0a38>
undefined local variable or method `remote' for #<Rays::Service::ApplicationService:0x00000000cc0a38>.: Backtrace:
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/raystool-1.1.5/lib/rays/services/application_service.rb:138:in `execute'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/raystool-1.1.5/lib/rays/services/application_service.rb:83:in `stop'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/raystool-1.1.5/lib/rays/interface/controller.rb:303:in `block in liferay_stop'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/raystool-1.1.5/lib/rays/utils/common_utils.rb:54:in `task'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/raystool-1.1.5/lib/rays/interface/controller.rb:295:in `liferay_stop'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/raystool-1.1.5/lib/rays/interface/commander.rb:330:in `execute'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/clamp-0.3.0/lib/clamp/command.rb:73:in `execute'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/raystool-1.1.5/lib/rays/interface/commander.rb:39:in `execute'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/clamp-0.3.0/lib/clamp/command.rb:64:in `run'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/clamp-0.3.0/lib/clamp/command.rb:126:in `run'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/gems/raystool-1.1.5/bin/__rays_exec.rb:29:in `<top (required)>'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/bin/__rays_exec.rb:19:in `load'
/home/fonseca/.rvm/gems/ruby-1.9.3-p125/bin/__rays_exec.rb:19:in `<main>'

Add possibility to kill liferay if stop doesn't work

Sometimes rays liferay stop doesn't work, for example when the JVM runs out of memory. It would be nice to either extend the liferay stop command to first try and use the Tomcat shutdown script and if it doens't work then force close the Tomcat process using kill. Else simply having a liferay kill command also works.

No message given when executed in non-rays directory

When I execute a rays command like rays liferay start in a directory which has not been configured to use rays I don't get any feedback. I suggest giving an error message.

Add --version flag

It would be nice to have the standard --version (and/or -v) flag to know which version of rays is installed.