![Martin Middleton Martin Middleton](/images/avatar-large.gif)
rd-setup does not set grails.serverURL property correctly
Reported by Martin Middleton | March 17th, 2011 @ 11:40 AM
When using rd-setup to configure RunDeck on a non-default port, the grails.serverURL property in the server/config/rundeck-config.properties file defaults to port 4440.
Comments and changes to this ticket
-
Greg Schueler March 17th, 2011 @ 02:30 PM
- Tag set to bug, config, setup
- Milestone set to Rundeck 1.3
- Milestone order changed from 17 to 0
-
Greg Schueler April 27th, 2011 @ 01:26 PM
- Milestone order changed from 9 to 0
Configuration of server files happens via the launcher codebase, so that is why rd-setup is not updating those files.
long term we have to figure out how we want reconfig to work. launcher installs server, configs server, then when server starts up it runs rd-setup. So perhaps we need a rd-config that does all the top level config, and in turn runs rd-setup.
It could be executed as part of the launcher, e.g.
java -jar launcher.jar --reconfigure -Dx=y
would do full top down reconfigure.IMO rd-setup should be be replaced with a full top-down reconfigure tool.
-
Alex-SF June 10th, 2011 @ 05:12 PM
- Milestone cleared.
- Milestone order changed from 8 to 0
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
People watching this ticket
Referenced by
-
280 Rename preferences.properties to something pertaining setup or install rd-setup needs revamp see #234