What timing for this email - we have just made significant changes to the
default config layout, and this includes no longer copying sample configs
to their non-sample locations. The changes are in our default branch right
now and will be part of the stable release scheduled for October. Have a
look, I'd be interested to hear your feedback since you've already put some
thought into this.
On Fri, Sep 19, 2014 at 3:10 PM, Julien Seiler <julien.sei...@gmail.com>
> Hi all,
> I have notice that the run.sh script is creating automatically all missing
> configuration and location files to make sure Galaxy can work properly at
> first launch. However, the script is not taking care of the actual settings
> of an existing universe_wsgi.ini file. As a result, if the
> universe_wsgi.ini file says that job_conf.xml is located at foo/bar
> location, the run.sh will create a job_conf.xml file at the root of the
> galaxy source code anyway.
> I'm thinking of improving the run.sh behavior to respect file path
> declared in an existing universe_wsgi.ini file in order not to create
> unused config or location files. I have currently started to implement this
> behavior in a small Python script (more handy than pure sh).
> What do you think about this concern ? Should I go for a pull request at
> any point ?
> @julozi <https://twitter.com/julozi>
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> To search Galaxy mailing lists use the unified search at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: