Re: [galaxy-dev] Clarification on galaxy update process

2012-03-22 Thread Greg Von Kuster
Hi Raj,

The files associated with each .sample file (universe_wsgi.ini is associated 
with universe_wsgi.ini.sample, datatypes_conf.xml is associated with 
datatypes_conf.xml.sample, etc) are your local versions of each of these files, 
allowing you to set configuration values according to your own environment.  
When you notice certain changes to a .sample file in an incoming change set, 
you should determine if it is a change that should be made in your local 
version of the file.  If so, you need to make the change manually.  This 
process is not automatic, but using this approach enables you to have complete 
control over your own environment.  Some changes in the .sample file may not 
make sense to change in your own environment.

Greg Von Kuster

On Mar 22, 2012, at 6:39 AM, Praveen Raj Somarajan wrote:

 Hello Dev team,
  
 I normally use hg incoming to check for any updates and hg pull -u to 
 install new updates if available. I noticed that there are files created with 
 .sample extension after the update (for all config files) - eg 
 universe_wsgi.ini.sample is modified with new updates, but 
 universe_wsgi.ini remain unchanged. The recent update has 
 sanitize_all_html option integrated, but it added in the ini.sample file, 
 not in the original .ini file.
  
 I'm quite confused, how does Galaxy pick up this option from .sample? Do I 
 rename .sample to orginal .ini file name to reflect the updates? This is 
 quite difficult as I have made serveral mysql/port/user_dir settings in .ini.
  
 Any suggestions would be helpful
  
 Thanks,
  
 Raj.
  
  
 
 This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
 for the use of the addressee(s). If you are not the intended recipient, 
 please notify the sender by e-mail and delete the original message. Further, 
 you are not to copy, disclose, or distribute this e-mail or its contents to 
 any other person and any such actions that are unlawful. This e-mail may 
 contain viruses. Ocimum Biosolutions has taken every reasonable precaution to 
 minimize this risk, but is not liable for any damage you may sustain as a 
 result of any virus in this e-mail. You should carry out your own virus 
 checks before opening the e-mail or attachment.
 The information contained in this email and any attachments is confidential 
 and may be subject to copyright or other intellectual property protection. If 
 you are not the intended recipient, you are not authorized to use or disclose 
 this information, and we request that you notify us by reply mail or 
 telephone and delete the original message from your mail system.
 
 OCIMUMBIO SOLUTIONS (P) LTD
 ___
 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:
 
  http://lists.bx.psu.edu/

___
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:

  http://lists.bx.psu.edu/

Re: [galaxy-dev] Clarification on galaxy update process

2012-03-22 Thread Praveen Raj Somarajan

thanks for the clear update. But, how does the end user know which are the 
files got updated by the incoming changeset, as I see many files get modified 
by the update proces? I know sanitize_all_html is a new addition which I can 
incorporate manually, but I don't know which are other additions/modifications 
in such files which might me useful for me.

Raj.

From: Greg Von Kuster [mailto:g...@bx.psu.edu]
Sent: Thursday, March 22, 2012 4:18 PM
To: Praveen Raj Somarajan
Cc: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] Clarification on galaxy update process

Hi Raj,

The files associated with each .sample file (universe_wsgi.ini is associated 
with universe_wsgi.ini.sample, datatypes_conf.xml is associated with 
datatypes_conf.xml.sample, etc) are your local versions of each of these files, 
allowing you to set configuration values according to your own environment..  
When you notice certain changes to a .sample file in an incoming change set, 
you should determine if it is a change that should be made in your local 
version of the file.  If so, you need to make the change manually.  This 
process is not automatic, but using this approach enables you to have complete 
control over your own environment.  Some changes in the .sample file may not 
make sense to change in your own environment.

Greg Von Kuster

On Mar 22, 2012, at 6:39 AM, Praveen Raj Somarajan wrote:


Hello Dev team,

I normally use hg incoming to check for any updates and hg pull -u to 
install new updates if available. I noticed that there are files created with 
.sample extension after the update (for all config files) - eg 
universe_wsgi.ini.sample is modified with new updates, but 
universe_wsgi.ini remain unchanged. The recent update has sanitize_all_html 
option integrated, but it added in the ini.sample file, not in the original 
.ini file.

I'm quite confused, how does Galaxy pick up this option from .sample? Do I 
rename .sample to orginal .ini file name to reflect the updates? This is quite 
difficult as I have made serveral mysql/port/user_dir settings in .ini.

Any suggestions would be helpful

Thanks,

Raj.




This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not to copy, disclose, or distribute this e-mail or its contents to any other 
person and any such actions that are unlawful. This e-mail may contain viruses. 
Ocimum Biosolutions has taken every reasonable precaution to minimize this 
risk, but is not liable for any damage you may sustain as a result of any virus 
in this e-mail. You should carry out your own virus checks before opening the 
e-mail or attachment.
The information contained in this email and any attachments is confidential and 
may be subject to copyright or other intellectual property protection. If you 
are not the intended recipient, you are not authorized to use or disclose this 
information, and we request that you notify us by reply mail or telephone and 
delete the original message from your mail system.

OCIMUMBIO SOLUTIONS (P) LTD

___
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:

 http://lists.bx.psu.edu/



This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not to copy, disclose, or distribute this e-mail or its contents to any other 
person and any such actions that are unlawful. This e-mail may contain viruses. 
Ocimum Biosolutions has taken every reasonable precaution to minimize this 
risk, but is not liable for any damage you may sustain as a result of any virus 
in this e-mail. You should carry out your own virus checks before opening the 
e-mail or attachment.


The information contained in this email and any attachments is confidential and 
may be subject to copyright or other intellectual property protection. If you 
are not the intended recipient, you are not authorized to use or disclose this 
information, and we request that you notify us by reply mail or telephone and 
delete the original message from your mail system.

OCIMUMBIO SOLUTIONS (P) LTD___
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:

  http://lists.bx.psu.edu/