On 11/02/2016 12:41 AM, Didier Roche wrote:
> Le 28/10/2016 à 21:00, Aaron Ogle a écrit :
>> Point definitely well made. I'm with you now. :)
>>
>> Now this being the case. I can't just swap the location. This is
>> where I would need a rock solid upgrade hook. But I would only need
>> to run
Le 28/10/2016 à 21:00, Aaron Ogle a écrit :
> Point definitely well made. I'm with you now. :)
>
> Now this being the case. I can't just swap the location. This is
> where I would need a rock solid upgrade hook. But I would only need
> to run it the once. Any suggestions? Or any good examples
Point definitely well made. I'm with you now. :)
Now this being the case. I can't just swap the location. This is where I
would need a rock solid upgrade hook. But I would only need to run it the
once. Any suggestions? Or any good examples?
On Fri, Oct 28, 2016 at 1:54 PM Kyle Fazzari
wrot
On 10/27/2016 11:27 PM, Didier Roche wrote:
> Le 27/10/2016 à 19:00, Aaron Ogle a écrit :
>> On Thu, Oct 27, 2016 at 11:56 AM Kyle Fazzari
>> mailto:kyle.fazz...@canonical.com>> wrote:
>>
>>
>> So are you storing this database in $SNAP_COMMON? Because
>> $SNAP_DATA would do this for you,
Le 27/10/2016 à 19:00, Aaron Ogle a écrit :
> On Thu, Oct 27, 2016 at 11:56 AM Kyle Fazzari
> mailto:kyle.fazz...@canonical.com>> wrote:
>
>
> So are you storing this database in $SNAP_COMMON? Because
> $SNAP_DATA would do this for you, no?
>
>
> Correct we are doing in $SNAP_COMMON. Is $S
On Thu, Oct 27, 2016 at 11:56 AM Kyle Fazzari
wrote:
>
> So are you storing this database in $SNAP_COMMON? Because $SNAP_DATA would
> do this for you, no?
>
Correct we are doing in $SNAP_COMMON. Is $SNAP_DATA using CoW? Or is it
going to be a full copy. From what I could see it was a full cop
On 10/27/2016 08:59 AM, Aaron Ogle wrote:
> Didier:
>
> With each upgrade we perform a database migration. So when reverting
> back the data structure in the database might have changed. This is
> potentially something we could handle inside of our platform
> specifically. But figured I would a
On 10/27/2016 08:52 AM, Didier Roche wrote:
> Le 27/10/2016 à 17:33, Aaron Ogle a écrit :
>> Didier:
>>
>> This sounds like exactly what I wanted! So once this lands I will be
>> able to just use: snapctl get value to get user set information?
> Exactly!
>
>>
>> Will the snapctl command be avail
Didier:
With each upgrade we perform a database migration. So when reverting back
the data structure in the database might have changed. This is potentially
something we could handle inside of our platform specifically. But figured
I would ask :)
On Thu, Oct 27, 2016 at 10:53 AM Didier Roche
Le 27/10/2016 à 17:33, Aaron Ogle a écrit :
> Didier:
>
> This sounds like exactly what I wanted! So once this lands I will be
> able to just use: snapctl get value to get user set information?
Exactly!
>
> Will the snapctl command be available anywhere in the snap or only in
> the hooks?
I gues
Didier:
This sounds like exactly what I wanted! So once this lands I will be able
to just use: snapctl get value to get user set information?
Will the snapctl command be available anywhere in the snap or only in the
hooks?
Also the upgrade hook looks like it could be a thing of beauty. Any plan
Le 27/10/2016 à 16:50, Aaron Ogle a écrit :
> Greetings,
>
> With our Rocket.Chat snap, we're looking to be able to allow someone
> to run an external mongodb instead of the built in one. As well as
> we'd like to add something like caddy / traefik etc to do ssl
> termination. But its not a daemo
Greetings,
With our Rocket.Chat snap, we're looking to be able to allow someone to run
an external mongodb instead of the built in one. As well as we'd like to
add something like caddy / traefik etc to do ssl termination. But its not
a daemon we would want enabled out of the box because of the e
13 matches
Mail list logo
