Question/Request: Directory for data that should persist over updates.

Lefteris Karapetsas lefteris at slock.it
Sat Jan 30 12:00:59 UTC 2016


Hello  Mark,


> Can you go into more detail about why that won't work in your
> case? Is it a question of the size of the data?


Yes exactly. It's a question of data size. Big databases, or blockchains in
my case, can't afford to be copied, especially when we are dealing with
embedded devices that already have very limited storage, say a 32GB SDcard
on a Raspberry PI.

But from what I understand from the discussion of Jamie and John above,
there is a plan in place for such a directory for 'shared' data in the
upcoming releases, so I am looking forward to it.

Best Regards,

---
Lefteris Karapetsas
Technical Lead at slock.it <http://www.slock.it>
Twitter <https://twitter.com/LefterisJP>, Github
<https://github.com/LefterisJP>, Blog <http://blog.refu.co>

On Sat, Jan 30, 2016 at 12:19 PM, Mark Shuttleworth <mark at ubuntu.com> wrote:

> On 28/01/16 05:44, Lefteris Karapetsas wrote:
> > Some snaps, including mine need to store some data, a database let's say,
> > or in my case a whole blockchain. So far I was instructed to do that at
> > $SNAP_APP_DATA_PATH. This works fine for now but whenever the user
> updates
> > the snap from what I understand this whole directory will be copied into
> > the next version's directory, to enable the transaction updating and
> > rollback nature of Snappy Ubuntu.
> >
> > This is not going to work for my snap and I need to ask if there is any
> > directory where I can store data for the application that will persist
> over
> > any update.
>
> Hi Lefteris
>
> The intention is that the data copy is invisible to the snap (the apps /
> services are shut down, the data copied, and then the new version
> started). Can you go into more detail about why that won't work in your
> case? Is it a question of the size of the data?
>
> Mark
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20160130/0cebcd6d/attachment.html>


More information about the snappy-devel mailing list