Give you seemingly have a custom deployment, a manual upgrade is probably
best. Instructions are available here:
https://wiki.galaxyproject.org/CloudMan/Services/Galaxy#Updating_Galaxy_source

We'll get the 16.07 release done too but juding by the way things look, it
won't be until the next month.

On Wed, Sep 14, 2016 at 11:23 AM, Lapointe, David <david.lapoi...@tufts.edu>
wrote:

> Hi Enis,
>
> Yes I figured what I was doing wrong. Using Cloudman to restart services
> overwrote my confs.   Using the CLI to manage services keeps everything in
> place, though I would like to figure out what is the optimal way to move to
> 16.07. Wait for the AMI or update?
> --
> David Lapointe Ph.D.
> Sr. Bioinformatics Specialist
> Research Technology (RT)
> Tufts Technology Services (TTS)
> 16 Dearborn Road
> Somerville MA 02144
>
> Phone:  617-627-5319
> Fax: 617-627-3667
> http://it.tufts.edu
>
> From: Enis Afgan <enis.af...@irb.hr>
> Date: Wednesday, September 14, 2016 at 11:01 AM
> To: David Lapointe <david.lapoi...@tufts.edu>
> Cc: "galaxy-dev@lists.galaxyproject.org" <galaxy-dev@lists.
> galaxyproject.org>
> Subject: Re: [galaxy-dev] Modifying a Cloud Cluster Instance
>
> Hi David,
> I totally missed this email from you - apologies! Are you still trying to
> do this or did you figure it out? Following the general guidelines on
> customizing the instance is a good place to start. There is an option in
> CloudMan to turn on non-signed SSL (from the Admin page) but the steps
> performed may be useful in trying to do the same manually. I believe it's
> necessary to just update and reload the Nginx configuration. A template can
> be found here https://github.com/galaxyproject/cloudman/blob/
> 8db478a8d777bcc48ed8c838f1f9de8519a11e60/cm/conftemplates/
> nginx_server_ssl.default
>
> Hope this helps and, again, sorry for not getting back to you earlier.
>
>
> On Thu, Aug 11, 2016 at 2:30 PM, Lapointe, David <david.lapoi...@tufts.edu
> > wrote:
>
>> This is on Amazon I should add.
>> --
>> David Lapointe Ph.D.
>> Sr. Bioinformatics Specialist
>> Research Technology (RT)
>> Tufts Technology Services (TTS)
>> 16 Dearborn Road
>> Somerville MA 02144
>>
>> Phone:  617-627-5319
>> Fax: 617-627-3667
>> http://it.tufts.edu
>>
>> From: galaxy-dev <galaxy-dev-boun...@lists.galaxyproject.org> on behalf
>> of David Lapointe <david.lapoi...@tufts.edu>
>> Date: Thursday, August 11, 2016 at 1:44 PM
>> To: "galaxy-dev@lists.galaxyproject.org" <galaxy-dev@lists.galaxyprojec
>> t.org>
>> Subject: [galaxy-dev] Modifying a Cloud Cluster Instance
>>
>> I have  a Cloudman instance up and running, but I would like to add SSL (
>> I have a signed cert and key ) and productionize it.  I see several methods
>> documented,but it's not clear which one is preferred: edit in place then
>> persist changes and restart  (wiki/Cloudman/CustomizeGalaxyCloud) seems
>> best to me. Any advice?
>>
>> Thanks
>>
>> David
>> --
>> David Lapointe Ph.D.
>> Sr. Bioinformatics Specialist
>> Research Technology (RT)
>> Tufts Technology Services (TTS)
>> 16 Dearborn Road
>> Somerville MA 02144
>>
>> Phone:  617-627-5319
>> Fax: 617-627-3667
>> http://it.tufts.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:
>>   https://lists.galaxyproject.org/
>>
>> To search Galaxy mailing lists use the unified search at:
>>   http://galaxyproject.org/search/mailinglists/
>>
>
>
___________________________________________________________
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:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to